Following the great article Terminal Server & XenApp Tuning Tips published on this website by Pierre Marmignon, this article defined all tips that I’ve found, test and validate for tuning Windows 2008 R2 and XenApp6.
Please note that :
- These informations are provided "as is" and that using these tips is at your own risks.
- All this tuning tips have been tested and validated only on VMs running on Vmware Vsphere 4, let us know your feeback related to any other platform (either Hypervisor or physical server).
That's a fact, XenApp is ALSO mainly use to deploy Rich Web Applications and not only for rich client one.
When you deploy such applications, you may not want users to be able to use the published Internet Explorer to surf the web or be able to access other informations.
To do so, many policies exists, but there are also some "hidden" settings, not present in standard policies but only within specific KB.
Having to deal with such cases, I've created a little custom ADM that is managing ...
Another experience from the field ...
Deploying applications on XenApp, You may have faced this kind of issue : an application is working fine within a published Desktop, but is not launching when published seamless.
In many cases (although it can also be related to a seamless issue), this is because the Application needs "explorer.exe" running (which is the case in a published desktop but not within a published application).
To deal with this problem, you can ...
Working in SBC environments for some years now I've used some best practices documents like the well known Methodology In a Box (MIAB) from Rick Delingher.
These documents, although really pertinent, are now quite outdated and do not include the latest OS and XenApp releases.
The purpose of this article is an attempt to summarize all Tuning Tips I've found (and also that I'm using) and describe the target operating system / XenApp version(s) they're working for.
Do not hesitate to give us your comments for this Article to be updated with your experience and feedback.
Please note that these informations are provided "as is" and that using these tips is at your own risks.
I was recently working on a large migration project in which we had to clean the users profiles.
To ease Users experience, we had to develop a way to avoid the eternal first run Microsoft Office Popup asking for Username, Company and Initials.
As these settings relies on reg values, this could be easy to define them by logon script.
However, as they are hardcoded within reg binaries values, scripting these settings is not as simple as it could have been ...
This "Tech Tip" article is focused on a very useful Security Setting You might want to enable on your Terminal Servers Farms.
By default, Windows allows Users to store their Network and Messaging (Exchange, .Net Passport) Passwords.
The first problem is that these settings are not stored in the User Profile but locally on the Server in an encrypted base.
The Second problem is that you may want Users to be able to save such informations (When Defining Several Outlook Profiles for User convenience for example) ...
You may have encountered this issue while running a Terminal Server or Citrix XenApp Project.
The Symtoms are quite simple to illustrate : Users are facing (random) significant Logon Delays and the logon process is hanging on "Applying Registry Settings".
According to Microsoft, this can occur if most of the following conditions are met ...
When troubleshooting an EdgeSight 5.0 SP1 Issue on XenApp 4.5 HRP03, I got the Following workaround from Citrix (as originally this is a DotNet Framework Issue) to deal with the "Citrix End User Experiencing Monitoring Service" not starting correctly :
Create a SemsService.exe.config file within the %ProgramFiles%\Citrix\EUEM\Service\ folder with the following content
You would say what's the matter with the Article Title "CitrixTools.Net Tools are Slow to Launch" ?
Actually I've been trying to find for weeks why in some cases All the Tools published on this Site were so Slow to Launch in some cases (Not Always).
And Guess What ? ...
This Article is based on another nice article written initially in French by Laurent Falguiere.
Windows 2008 Terminal Services introduce a new functionnality called "Drain Mode".
This new functionnality allows Admins to connect to a Terminal Server while Users can not (Only disconnected sessions will be able to reconnect, while new sessions won't be allowed).
Actually, when a server is configured in this mode ...
Laurent Falguiere, a French Terminal Server MVP, has written an interesting article regarding the Terminal services Console Session and the "/Admin" Switch introduced in RDP Client 6.1 and Windows 2008 Server.
I decided to translate it and publish it in Our English part (as the French part is directly pointing the Laurent's French WebSite).
On Windows 2003, the console session points to the local session (the one accessible when being physically in front of the server, connected directly on it).
This session has a really specific role :