April 7th, 2012
Earlier this week Microsoft announced App-V 5.0 Beta. You can download it from Microsoft Connect, try and investigate what has changed. While reading some articles it seems to be rewritten from scratch, I guess the name Softgrid is now history.
A short summary:
- A new format with the extension .APPV
- The format SFT is gone.
- No Q drive anymore
- No more OSD files
Read the Release Notes carefully because there are known limitations.
App-V 5.0 Beta components (Client, Sequencer and Server) require both .Net 3.5 and .Net 4.0.
Sequencing Office 2010 is not supported in the Beta release.
The App-V Sequencer and Client require the latest windows updates as they contain updates critical to creating correctly formatted virtual application packages. (i.e KB2533623).
This information is found in the Microsoft Application Virtualization (App-V) 5.0 Beta Adminstrator’s Guide and the Release Notes.
Windows XP and Windows Vista not supported as the sequencer.
March 29th, 2012
Microsoft has released an update rollup for the printing core components that are included in Windows 7 and in Windows Server 2008 R2.
Issues that the update rollup resolves
This update rollup resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
- Picture Manager may stop responding when you open the “Printer Properties” dialog box in Picture Manager in a 64-bit version of Windows 7 or of Windows Vista
- Stability update for Windows Server 2008 R2 Failover Print Clusters
- No event is added to the System log or to an operational channel when a print job is canceled or deleted
- FIX: A legacy HP printer driver may crash when you run a 32-bit application on a computer that is running a 64-bit version of Windows 7 or of Windows Server 2008 R2
- You cannot print a Web page by using an IPP printer in Windows 7 or in Windows Server 2008 R2
- “Windows cannot connect to printer” error message when you try to create a Point and Print connection to a remote printer from a Windows 7 or Windows Server 2008 R2-based client computer
- Poor printing performance in Windows 7 or in Windows Server 2008 R2 compared to the performance in Windows Vista or in Windows Server 2008
- A computer that is running Windows 7 or Windows Server 2008 R2 intermittently cannot use a shared network printer to print
- Event 602 is logged after you log on to a Windows 7-based or Windows Server 2008 R2-based computer that has a network printer installed
- The Add Port Wizard dialog box is displayed incorrectly in an x64-based version of Windows 7 or of Windows Server 2008 R2 when you run an application that uses the AddPort function
- You cannot print results to files by using web applications in Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 after you install security update MS10-061
- Printing performance decreases in Windows 7 or in Windows Server 2008 R2
- Print queue does not work if the queue is not one of the first 100 queues installed in a Windows Server 2008 or Windows Server 2008 R2 Terminal Services session
- Print driver installation does not work in Windows 7 or in Windows Server 2008 R2 when you try to install the HP Universal Print Driver in a Novell network environment
- Invalid redirected printers may be available in a Remote Desktop Services session that connects to a RD Session Host server that is running Windows Server 2008 or Windows Server 2008 R2
March 27th, 2012
This article describes how to configure Application Pre-launch in XenApp version 6.5.
- Citrix Receiver 3.0 for Windows
- Online Plugin 13.0
To configure Application Pre-Launch in XenApp 6.5, complete the following procedure:
- Select an application for pre-launch from the AppCenter.
- Right-click the application and select Other tasks.
- Create a pre-launch application.
- After you complete it, a new pre-launch application is added to the application list with an icon followed by an application name, as shown in the following screen shot.
Note: Pre-launch is available only for the application’s configured users.
- On the client device, verify the setting of the following registry key(Default Installation Values):
32bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Prelaunch
64bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\Prelaunch
- Close the Receiver and then re-open it.
Note: Do not start any applications.
- In AppCenter that the application is set for prelaunch.
- The following screen shot displays a calculator that is a prelaunch application and ready to use. The application is now ready to start.
- It is a best practice to also set the folowing policies:
Pre-launch Terminate Timer Interval
Maximum amount of time before the pre-launch application exits (60 minutes by default)
Pre-launch Disconnect Timer Interval
Amount of time before the pre-launch application disconnects the session (60 minutes by default)
March 14th, 2012
A good whitepaper from Citrix regarding Administrator experiences concerning XenApp 6.5 Session Pre-Launch. Click here to view the whitepaper.
March 1st, 2012
Click here to view a great video serie of Citrix and RES Software products:
- Deploy Citrix XenDesktop from a Building Block
- Deploy Citrix XenApp from a Building block
- Citrix XenApp Publishing and RES Workspace Manager
- Citrix XenClient and RES Workspace Manager
More videos will show up later
February 28th, 2012
The Adobe Acrobat Reader application stops to respond. This issue is observed on a Server console, RDP, and ICA Connections versions 9.1, 9.5, and 10.1.0.
This issue exists only on a 64-bit server. The Adobe Acrobat Reader application that is installed on 32-bit server functions as expected.
Several Adobe Acrobat Reader .dll files have conflict with Citrix Memory Management feature.
1. To resolve the preceding issue, complete the following procedure:
- Exclude the following files from Memory Optimization that has stopped Adobe Acrobat Reader on the 64-bit Windows 2003 Servers:
Note: Ensure that you enable the Use farm settings option.
- C:\Program Files (x86)\adobe\reader 9.0\reader\AdobeXMP.dll
- C:\Program Files (x86)\adobe\reader 9.0\reader\BIBUtils.dll
- C:\Program Files (x86)\adobe\reader 9.0\reader\logsession.dll
- C:\Program Files (x86)\adobe\reader 9.0\reader\LogTransport2.dll
- C:\Program Files (x86)\adobe\reader 9.0\reader\sqlite.dll
NOTE: Try to include the C:\Program Files (x86)\adobe\reader 9.0\reader\AcroRd32.exe file, even though this file is not listed by ADSCleaner Tool.Reset the CPU/Memory Optimization of the affected XenApp servers to the farm default settings.
2. Reset the CPU/Memory Optimization of the affected XenApp servers to the farm default settings.
3. Clean the streams of the affected XenApp servers with ADSCleaner tool (CTX108542).
February 22nd, 2012
When I upgraded my Citrix Receiver 3.0 to 3.1, I ran into the fact that a https address instead of a http must be configured in the preferences.
There is a way to allow configuring http instead of https. This can be done by adding/changing the following registry keys:
HKLM\SOFTWARE\Citrix\AuthManager (on a 32-bit machine) or
HKLM\SOFTWARE\Wow6432Node\Citrix\AuthManager (on a 64-bit machine)
Under AuthManager create a new String Value (REG_SZ) with the name “ConnectionSecurityMode” and the Data “Any”
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Dazzle (on a 32-bit machine) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Dazzle (on a 64-bit machine)
Under “Dazzle” modify the existing data of “AllowAddStore” to be “A”.
February 13th, 2012
Last friday I was at the first DUCUG (Dutch Citrix User Group) event in Amsterdam, which was a great, well organized and interesting day. Jim Moyle had a great and presentation about Windows 7 and IOPS. A surprising outcome which makes you start thinking about designing environments (especially VDI).
Click here to get the full presentation
February 13th, 2012
A nice explanation at the Citrix Blog about Pre-Launching in XenApp 6.5.
Click here to view the article.
February 3rd, 2012
Today I have been reading a useful article in the Citrix Knowledge Center about troubleshooting installation or removal issues with Citrix XenApp, CTX132117.
I guess it can also be consulted for troubleshooting installation or removal issues with other software.
When trying to install or remove any XenApp Software (including hotfixes and rollup packs), a 1603 Windows error message is displayed.
The following are the possible error messages that are displayed when trying to install or remove any XenApp Software:
Error 1603: A fatal error occurred during installation
Check the article at: http://support.citrix.com/article/CTX132117