We're considering doing this at a few places and I was wondering what people had found when they did it? I've heard horror stories of users and SIDS coming over but computer accounts not and some issues with roles on the new 2003 servers.
The migration would have be done incredibly quickly, so if it came down to mucking about or starting a clean 2003 domain I'd probably have to opt for the latter if we weren't fairly confident!![]()

If i was you i would start again with a Server 2008 / 2008 R2 Domain

Yeah again if i was you i would scrap your current domain and re-build a new one using windows server 2008/R2. I would leave 2003 unless you really want to use that and if so i would still start from scratch![]()
James.
I was part of a team that did a NT4 to 2003, but that was about 6 or 7 years ago. I do remember one or two small teething problems (do not remember any specifics), but there was nothing major. At that point in time, the senior tech and the IT manager were very knowledgable and did a couple of trial runs before hand.
-Ken
I love server 2008 but not sure where we stand with some of our hosted apps, otherwise I'd go for it straight off. Cheers folks, the new domain plan is something I've always favoured, too much old cr@p on the old domain too..![]()

I did it here 5 years ago for two domains. One I had to upgrade across from NT4 - 2003, the other (smaller) one I just migrated files and accounts. Provided you've got a back-out plan and good backups, it shouldn't be a problem.
But if you can I'd start clean with 2008 - get your new domain running nicely (with no users), migrate the user accounts (but leave them live in the old domain), shares and homedirs (using either microsoft tools or robocopy).
Given that 95% of the share contents will only be modified every 3 months (if that), the only work you should need to do on changeover day is do a final robocopy to catch anything that's changed and shift the computer accounts.
There are currently 1 users browsing this thread. (0 members and 1 guests)