Product Version: N/A
Expires on: 365 days from publish date
Updated: March 17, 2014
The persistent data disk stores status files which may trick ProfileUnity into thinking that there are no settings that need to be replayed into the user's session, even though the operating system has recomposed since the user's last session.
User settings are lost or reset to default, especially after a recompose. Setting loss may be intermittent or for each logon.
You can set ProfileUnity to disregard the timestamp that is cached in the persistent data disk. This is a setting in the ADM template portion of the ProfileUnity GPO.
To use this setting:
1. Open Group Policy Management Editor and go the the ProfileUnity GPO that is applied to your users (if you are using loop-back processing this setting may be applied at the machine level but passed through loop-back processing to the users).
2. Edit the ProfileUnity GPO.
3. Go to the ADM Template portion of the GPO. This can be in one of two places depending on your version of Active Directory.
On Windows 2003 and older: User Configuration\Policies\Administrative Templates\Liquidware Labs\ProfileUnity
On Windows 2008: User Configuration\Policies\Administrative Templates\Classic Administrative Templates\Liquidware Labs\ProfileUnity
4. Double Click the "Disable Time Stamp Check" setting, and set it to enabled.
5. If you have more than one domain controller you may need to allow time for replication between domain controllers. You may also need to perform a group policy update or reboot your machines in order for them to pick up this setting.
Note: This KB is only for this specific scenario. If this change does not fixes your problem than the issue may lay somewhere else. Than please change back the setting to default state (unconfigured) and look for another KB or contact email@example.com