General discussion

Locked

Keep profiles after Server upgrade

By Sneeks ·
I have a flat network w/ 1 NT4 domain (one Server only), and about 15 workstations (NT4, Win2K, Win98, Mac).

I want to put Win2k on the server, but without upgrading - I intend to format the server and start fresh. I don't care so much about recreating all the user accounts, but I am concerned about what will happen to my users' profiles. Profiles aren't kept on the server, just local. I have a test Win2k server running AD and DNS. As a test, I joined this new (different name) domain from my workstation. What I'm experiencing is: Logins are painfully slow and a new profile was created. I have about a half gig on my old profile. I tried to copy the data to my new profile but some programs are blurting errors at launch.

I want to make the transition as transparent as possible to my users. I don't want to have to lose their profiles. Is there an easier way to do this, and is there a way to login faster.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Keep profiles after Server upgrade

by gbworld In reply to Keep profiles after Serve ...

One of the difficulties of switching to Windows 2000 is the difference in the way items like profiles are stored. In general, it should not be changing the user's profile, but rather, changing the method of storing the profile. In your case, you arejoining a new domain, so the new profile is unfortunate, even if you have the same name.

A couple of things to notice here. First off, if you are upgrading the servers first, you need to make sure they are in mixed mode to provide NT and 9x machines the ability to use the network. This is advised. The easiest way to ensure this is to install server and then run dcpromo to make the server a PDC. You can switch from mixed mode to native once the domain is all Win2k, but not the other direction.

Now, back to your problem. If you want to keep older profiles, it is best to upgrade the PDC, at least. You can demote PDCs very easily in 2k, so this is just to maintain the domain. You then can rebuild BDCs into the domain and have one take over PDC while you rebuild the original PDC (if you want a clean install). This should maintain the domain. Clients can then log on without losing their information, as this is still the same domain.

If you, instead, decide to build a new domain with the same name, user's will have to rebuild.

Plan your network carefully before migrating to Win 2k. Win 2k is very powerful, but can be a pain if you do not approach sensibly. I say this no matter how small your network is (although planning smaller networks is easier, a bad decision is still a bad decision).

Summary: To maintain profiles, migrate at least one of your domain controllers in mixed mode. If you want to rebuild it later, add other DCs and then rebuild. This will maintain thedomain and help user's avoid a whole new profile. Then switch to native mode when everyone is Win 2k.
Gregory A. Beamer
MCP: +I, SE, SD, DBA

Collapse -

Keep profiles after Server upgrade

by Sneeks In reply to Keep profiles after Serve ...

Poster rated this answer

Collapse -

Keep profiles after Server upgrade

by abubin In reply to Keep profiles after Serve ...

Upgrading from NT4 to 2000 is a very tedious task. If you want to make you job simplier, try a software that help profiles migration. A software that I can recommend is Desktop DNA. The link is http://www.miramar.com. This problem will even help with migrating certain popular software.

Collapse -

Keep profiles after Server upgrade

by Sneeks In reply to Keep profiles after Serve ...

Poster rated this answer

Collapse -

Keep profiles after Server upgrade

by Sneeks In reply to Keep profiles after Serve ...

This question was closed by the author

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums