Windows Forum

Ask something
Discussion Locked

Desperate for Profile Help

0 helpful
3 replies

by xpertdragon 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Not too long ago, I posted a question about help with NT/2000 profiles. I am still having many frustrating problems with the conversion of users from an NT 4.0 roaming profile to a Win 2000 Pro roaming profile. I have attempted to let Windows 2000 setup a user profile on its own after manually deleting the profile and logging back in, but I still receive the messages about roaming profile not found, and local profile not found, being logged in with a temporary profile.

I have visited Microsofts web site, and their help with profiles is fairly basic, and not troubleshooting oriented.

Can someone post a profile configuation web page to my question? Should there be something else I need to do on the NT 4.0 PDC server?

I myself, have a roaming profile, and log into my NT 4.0 workstation machine everyday with no problems....I also log into any Windows 2000 pro workstation with no problems. HBOwever, certain users, can't make that same transition over to Windows 2000 professional. Please help. Thanks.

Paul M. Chavez

3 replies

by shmaltz

Even thoug it works for you Windows NT profiles and Windows 2000 Profiles are NOT interchangeable.
You have to create a new profile for everyone. I know it's a pain. One way to make sure that people don't get cofused while you deploy windows 2000:Disable the roaming profiles. Create on all local computers a default profile that requires minimal user interaction to setup for the first time. When you are done with the deployment re-enable the roaming profiles. The next time users log in the local profiles will be copied to the server.
The reason that you receive the message roaming profile is not found is because the machine you log into knows that a roaming profile should exist so it tries to download it but cannot find it. The way to get rid of the roamin profile not found problem is to log in localy with administrative priviliges. In the system properties goto the user profiles tab and delete the profile for that user.

This discussion is closed to new replies.