Citrix PVS - After Reverse Imaging Unable To Change Computer Name

Purpose:

Show the steps taken after reverse imaging a W2K8R2 Citrix PVS Target Device to fix the inability to rename the server and add back to the AD Domain

Symptom:

After the reverse imaging process is done, the machine removed from the domain, rebooted, name changed and rebooted again the name of the server doesn't change and the ability to add the machine back to the domain is grayed out.



Resolution:

In the registry navigate to the below location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName

There are 2 subkeys called ActiveComputerName and ComputerName and within each of there are valumes called ComputerName. Verify that both have the new computer name.

On my issue the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerName\ComputerName value had the old computer name. I renamed the key and then restarted the computer.

Cause:
Computer account not updating correctly

SageLike Post ID: SL0014

Applies to:

Citrix Provisioned Target Devices
Windows Server 2008 R2
Windows 7

Maybe others but these are the OS's that I've had issues with.

References:

http://discussions.citrix.com/topic/283685-after-reverse-image-unable-to-change-computer-name/

Windows Update Never Stops Checking

Purpose:
This post explains how to fix an issue with Windows Update on Windows 7 x64.

Symptom:
My master (aka gold) Windows 7 virtual machine has been woefully in need of some updates.  The master image has been shutdown for several months because the XenDesktop catalog that relies on it has also been shutdown for months.  Returning my focus to Windows 7, I turned on the master image and ran Windows Updates.  Not wanting to watch paint dry, my attention drifted elsewhere and it ended up being a few hours before I returned to Windows Update.  It was still checking for updates.  I rebooted the machine and it happened again.

Resolution:
I am fairly certain this has happened to me before so; of course, I Bing'd it.  After digging around awhile, I found a forum entry suggesting to try KB3172605 or for x64 KB3172605.  I downloaded the patch directly from Microsoft and put it on my C drive.  Running the patch brought the Windows Update dialog up again and it started checking for updates which is not what I wanted to see.  Reboot and try installing the patch--you may even want to run it as an administrator.  After rebooting again, the patch successfully installed and Windows Update quickly returned with 34 new important updates (1.6 GB).

Cause:
Let us be honest here, this is Windows Update and from time to time it has issues.  At this time, Windows 7 has hundred and hundreds of updates and that assuming you are starting from Service Pack 1.  I am not confident that this is reproducible but it seems worth sharing with others. I am confident that this is not the last time I will run Windows Update on Windows 7 or even build a new master image.

Drop me a line in the comments if this works for you or if you have any questions,


Brian Olsen @sagelikebrian




SageLike Post ID: SL0012

Applies to:
Windows 7 x64 (validated on a virtual machine and Dell laptop)
Windows 7 x86
Maybe others

References:

• https://www.microsoft.com/en-us/download/details.aspx?id=53332
• https://www.microsoft.com/en-us/download/details.aspx?id=53335
• http://www.sevenforums.com/windows-updates-activation/382249-windows-update-never-stops-checking-updates-10.html
  

Citrix XenDesktop 7.1 Slow Logon Black Screen

Purpose:
This article explains slow logon times for XenDesktop v7.1.  In addition to slow logons, the wallpaper may show as black during the initial logon process.

Symptom:
A slow logon is a relative thing and depends on a myriad of factors.  If your server or desktop logon does not show the progress wording on logon but instead has only black wallpaper then it is definitely worth testing out this registry key.  If you just think that your logon is slow, then it still may be worth the effort to test.

Resolution:
Add a new registry key to the master image (desktop or server).

Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Logon
Name: DisableStatus
Type: REG_DWORD
Value: 00000001 

Before you add the key, establish a logon time baseline.  I historically like to do this manually using a stopwatch (iPhone) but the built in Director logon time functionality is an exciting new feature and will give you additional insight.  Here is an example of a Windows 7 baseline from the SageLike lab:

After adding the key, time another logon to see if your logon duration has improved.  Here is an example of the after:

This is a big improvement but YMMV.  An interesting side effect for Windows 2008 R2 server deployments is the return of the status text while establishing a session.  A blank black screen leaves the user to wonder if anything is happening at all.  This fix replaces the black wallpaper with the rapidly changing logon status information.  This cues the user that many things are happening to build their session.

Cause:
I have not found the history of this registry key or why it is absent when using the v7.1 VDA.  I have observed this working quite well for both Windows 7 and Windows 2008 R2 in a lab environment.  At the time this was written, the reference CTX article below only indicates it is applicable to XenApp 6.5

SageLike Post ID: SL0006

Applies to:
Windows 7
Windows 2008 R2
XenApp 6.5
XenDesktop 7.1
Maybe others

References:
CTX135782 Black Screen Logging on to a Published Desktop