I have a MetaFrameXP server farm and use mandatory profiles for most of my users. These mandatory profiles are located on a seperate server accessible by all MetaFrame servers. When logging in as a user with a mandatory profile, I have often started seeing an error message, "Windows cannot locate your roaming profile and is attempting to log you on with your local profile." Yet the mandatory profile is then loaded from the central server despite the message. (I demonstrated that by putting a marker directly in the desktop folder of the central mandatory profile, and it was copied down even though the message said otherwise.)
I recall that in NT4 TSE there were some timeout settings that could be adjusted in the registry that would keep the MetaFrame server from displaying that message unless there were really a problem with accessing the mandatory profile.
Are there any similar settings within Windows 2000 Terminal Services?
Or is there some other cause for this behavior?
Thank you very much for your help.
I recall that in NT4 TSE there were some timeout settings that could be adjusted in the registry that would keep the MetaFrame server from displaying that message unless there were really a problem with accessing the mandatory profile.
Are there any similar settings within Windows 2000 Terminal Services?
Or is there some other cause for this behavior?
Thank you very much for your help.