KB955020 Update for Windows Vista and Server 2008 May Occupy 1GB Disk Space – Remove to Recover
December 1, 2009Logons Hang at "Applying Internet Explorer Branding Policy" When Connecting to XenApp Servers with Internet Explorer 7
November 26, 2009http://support.citrix.com/article/CTX120579
Symptoms
When you log on to a Citrix XenApp server, running Windows 2003 with Internet Explorer 7, and there are Active Directory Internet Explorer Maintenance Group Policy settings configured, you experience a 20 second delay at logon.
You experience the delay when the stuisrv.exe gui is displaying "Applying Internet Explorer Branding policy…"

Cause
Internet Explorer 7 introduced an error that causes this problem to occur; the error occurs as a result of command line parameters that are parsed by Internet Explorer 7.
Solution:
Enter the following in the open field: rundll32 iedkcs32.dll;Clear.
Smart auditor agent error: Exception caught while sending message queue message.
November 26, 2009Try restart the Citrix SmartAuditor Agent service.
XenServer loses its all NIC and settings.
November 20, 2009http://support.citrix.com/article/CTX119240
The following are the commands you can try.
host-is-in-emergency-mode
host-is-in-emergency-mode
Returns true if the host the CLI is talking to is currently in emergency mode, false otherwise. This CLI command works directly on slave hosts even with no master host present.
pool-emergency-transition-to-master
pool-emergency-transition-to-master
Instruct a member XenServer host to become the pool master. This command is only accepted by the XenServer host if it has transitioned to emergency mode, meaning it is a member of a pool whose master has disappeared from the network and could not be contacted for some number of retries.XenServer Administrator’s Guide Command line interface 162
Note that this command may cause the password of the host to reset if it has been modified since joining the pool (see the section called “User commands”).
pool-recover-slaves
pool-recover-slaves
Instruct the pool master to try and reset the master address of all members currently running in emergency mode. This is typically used after pool-emergency-transition-to-master has been used to set one of the members as the new master.
User Profile Manager Deployment Best Practices &
November 12, 2009http://support.citrix.com/article/ctx119036
XenServer Pool, Master host failures
November 12, 2009Master failures Every member of a resource pool contains all the information necessary to take over the role of master if required. When a master node fails, the following sequence of events occurs:
1. The members realize that communication has been lost and each tries to reconnect for sixty seconds.
2. Each member then puts itself into emergency mode, whereby the member XenServer hosts will now accept only the pool-emergency commands (xe pool-emergency-reset-master and xe pool-emergen- cy-transition-to-master). If the master comes back up at this point, it re-establishes communication with its members, the members leave emergency mode, and operation returns to normal. If the master is really dead, choose one of the members and run the command xe pool-emergency-tran- sition-to-master on it. Once it has become the master, run the command xe pool-recover-slaves and the members will now point to the new master. If you repair or replace the server that was the original master, you can simply bring it up, install the XenServ- er host software, and add it to the pool. Since the XenServer hosts in the pool are enforced to be homoge- neous, there is no real need to make the replaced server the master.
Posted by Nicolas Lin
Posted by Nicolas Lin
Posted by Nicolas Lin