C
ChrisInRIC
Guest
Has anyone else seen where a terminal server is not updating the
following key appropriately:
\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal
Services\WFProfilePath
We were migrating the file server to a new platform. The Profiles
share was moved to a new server. Each users TS Profile path was
updated in AD. The two controllers (both local) were synch'd. But
the three Terminal Servers would not look to the new server. Found
that key was still pointing at the old server. We manually edited the
key, but does anyone have an idea as to how it should have worked?
And why it might have failed?
Thanks,
Chris
following key appropriately:
\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal
Services\WFProfilePath
We were migrating the file server to a new platform. The Profiles
share was moved to a new server. Each users TS Profile path was
updated in AD. The two controllers (both local) were synch'd. But
the three Terminal Servers would not look to the new server. Found
that key was still pointing at the old server. We manually edited the
key, but does anyone have an idea as to how it should have worked?
And why it might have failed?
Thanks,
Chris