Discussion Locked
0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I use roaming profiles on my NT4.0 network. All the workstations are Win 2000. I just purchased a few laptops with docking station. When the laptops are on the docking stations here at work there is no problem with profiles. When a user undocks and takes the laptop home and logs on to the laptop it uses the cached profile. When the user comes back to the office, docks the laptop and tries to log on his roaming profile is not loaded. Any ideas?
5 replies
by curlergirl
How do you know that the roaming profile is not loaded? According to MS documentation, in Win2K if the locally cached profile is newer than the server-based profile, the two are merged. Therefore, you wouldn't see a message like you do on NT that the locally stored profile is newer. Are they getting some sort of error message?
by dguillermo
The profile that loads does not have any of the icons or wallpaper that it should have.
by countupir
I think the reason is that since work has been done at home the local profile is newer then the one on the server. The profile won't load because the data from the work done at home is now updated regardless of the actuall work done. Roaming profiles are a bad idea for computers that are going to be removed from the network.
The ultimate solution is have them log on to the domain from home in order to utilize the profile at all times. Otherwise create two profiles. One for domain log on and the other for other times.
by dguillermo
Poster rated this answer
by dguillermo
This question was closed by the author
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending
0 helpful
11 replies
0 helpful
10 replies
Question Locked
Do You Save Useful Windows Tutorial Videos for Later
0 helpful
7 replies
0 helpful
1 reply
Question Unanswered
Is WSL still relevant in 2026?
0 helpful
0 replies