Solved

Windows 2003 Migration

Posted on 2004-08-18
4
138 Views
Last Modified: 2010-04-19
All, I am about to migrate my domain from NT4 to W2K3...

Could someone please clarify this point for me..

We have 100 desktops, 17 servers and 50 remote workers with laptops

My question is about the remote users; I can migrate the desktops using the computer migration tool which is fine, however its going to take a while (about a month) to get all the remote users in so I can migrate the laptops. To this end, will I need to keep the 17 windows based servers on the *old* domain until I get all latops migrated? I assume I will also have to keep the remote users logging into the *old* domain until I have migrated the laptops; I also assume that I can get them to log onto the *new* domain when I have migrated the laptops (obv I wil be cutting across the SID History)

Your urgent thoughts would be most appreciated

Thanks  
0
Comment
Question by:credmood
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 6

Expert Comment

by:youre1m
ID: 11828370
Yes you need to run your 2 environments in parallel, but not necessarily all 17 servers depending on what they are doing and what the Remote workers use on each server. You can set up a trust between the old and new domain and have them log in with new domain accounts but I would recommend keeping it clean and migrating as you have planned already. That way as you mention you get to carry the SID history accross.

We just completed a similar exercise, we transferred DHCP, DNS to the new environment and worked our way through everyone in teams as shared data can cause an issue if you have some users of it on the old and some on the new, so we set up a trust to enable new domain users to acces shared data on the old domain. Then once everyone that used that data had been migrated we moved the data to the 2003 domain until we were eventually clear on the old. Then we shut down but didn;t remove any old servers for 1 month, so that we had a rollback plan in the event of failure. Obviously you will be relying on new servers though, if your hoping to use the old kit for the new domain then you might have to take more of a "big bang" approach.
0
 

Author Comment

by:credmood
ID: 11838742
thanks for this, I have decided to stick with a *clean* migration and get all the remore users to use their *old* accounts until we get them into the office to do the computer migration..waht ill do is disable all the target accounts for remote users (untill their laptops are done) and disable all internal peoples source accounts..this way everyone is defo using the correct accounts....until i get everyone done and close the old domain.

Also, the problem I have is that the two serves I have targeted as being the DC's (I do have a tempdc that im going to build the new domain on) are file servers as well. However these will need to be on the new domain in oredr for me use as DC's. This involves me having to A) leave all existing permissions and create new ones for the new domain or B) migrating the server (which will change the permissions) and redo the old domain permissions. (I am going to have a trust set up). I think I will choose B this seems to be the better option...

Any thoughts on this

Thanks for your help

0
 
LVL 6

Accepted Solution

by:
youre1m earned 500 total points
ID: 11839095
We had new servers so didn't have this problem. We also used new group names so used robocopy to move the data and applied the permissions manually. Depends on the size of your operation  but we used it as a housekeeping exercise rather than simply recreating what we had before, as it didn't seem to quite fit what we were trying to achieve.

I'm a big fan of doing stuff as important as this as clean as possible, and with only 150 users your data probably isn't that complex a structure that it will take too long.
0
 

Author Comment

by:credmood
ID: 11839187
so your saying that what Im suggesting should be fine?
Your rigjht about the groups, however i went through them and they seem to more or less match what we're trying to do so I thought for ease I would just migrate them as well as the users...keeps everything *clean* as you rightly point out.

Cheers youre1m, its always good to get some feedback, just last minute panics that ive thought of everything thats all...:o)
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The HP utility "HP Lights-Out Online Configuration Utility for Windows Server 2003/2008" could be of great use when it comes to remotely configure a HP servers ILO WITHOUT rebooting the server. We would only need to create and run scripts using thi…
Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
In this video, viewers are given an introduction to using the Windows 10 Snipping Tool, how to quickly locate it when it's needed and also how make it always available with a single click of a mouse button, by pinning it to the Desktop Task Bar. Int…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

695 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question