Discussion Locked

Raoming profiles on laptops

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 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.

This discussion is closed to new replies.