Explaining Shadow Key Time Stamp
Thursday, 21 December 2006 by Michel Roth
Wilco van Bragt has written a short article on the how, when and what of the Shadow Key Time Stamp utility: "If applications are installed on a Terminal this is normally done via Add/Remove programs or via change user /install command. This sets the Terminal Server in installation mode. When an application within this installation mode writes registry keys to the HKEY_CURRENT_USER Microsoft writes this key also in the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software. These values in this key, called Shadowkey, will be applied to a user when he logs on to the Terminal Server if no keys (or older keys) are found in his profile based on a time stamp.

Because the checking is done on time stamp you can experience strange behaviors if a new server is applied to your infrastructure. This behavior occurs because the values in the Shadow key got the time stamp when they are installed. Users can have different settings in their profile, but with an older timestamp. When these users logs on to new server, the Shadow keys settings are written in their profile because the date is newer than the setting in the user profile, which is logically unwanted."

Read the article here.

Related Items:

Review of Sepago Profile (29 August 2007)
Citrix / Terminal Server Registry Secrets (13 January 2006)
Dealing with Profiles and Policies In Vista and Server 2008 (26 June 2008)
Group Policies And Virtual Applications (7 November 2007)
Migrating User Settings With The Flex Profile Kit (21 March 2007)
Terminal Server Client Shortcut Key Combinations (27 October 2005)
Viewing Quest vWorkspace Managed User Profile Data (24 August 2009)
A First look at RTO Virtual Profiles (9 April 2008)
Using The FPK In VDI Deployments (28 March 2007)
User Profile Hive Cleanup Service 1.6d (2 November 2005)
Comments (0)