Thanks - that was my plan - bad semantics.
I meant I was going to create 15 new accounts on the new server and then re-configure the workstations to connect to the new domain / server.
If anyone can point me to any step-by-steps, that would be great.
I don't want to start this and realize I screwed something up that requires a re-installation!
Main Topics
Browse All Topics





by: dooleydogPosted on 2008-03-31 at 11:24:57ID: 21247804
internal DNS name space has nothing to do with external DNS namespace.
It is generally considered a good idea to keep the names different simply to avoid confusion. Quite often company.com will use ad.company.com internally.
Internally, you will need to make the DC a DNS server, and the dcpromo wizard will take care of that for you if you let it.
Now it gets complicated...
install the apps and test, then instead of trying to migrate 15 users, I would suggest just creating new accounts in the AD domain. It may be seem like more work, but may be simpler in the long run.
This is in no way a complete list... you need to do a lot of research still.
Good Luck,