Moving from single label to dotted domain name..

[johnny]

Hi,

 

We have a w2003 dc / dhcp / dns with around 50 users with a single label domain name.

 

I want to change the domain name to a dotted one to avoid caring about the special requirements for non-dotted domains.

 

Also we need to move this server (and users) to new hardware.

 

How do I do this with the least hassle? In which order..?

 

Thanks a lot for urls, hints and comments...

 

/johanny

[Geoff]

You need to use the domain rename tools to change the dns domain name.

 

http://www.microsoft.com/technet/downloads/winsrvr/domainrename.mspx

 

Once you've done this, then bring up your new server and move the services across.

[johnny]

You need to use the domain rename tools to change the dns domain name.

 

http://www.microsoft.com/technet/downloads/winsrvr/domainrename.mspx

 

Once you've done this, then bring up your new server and move the services across.

 

Thanks Geoff, I have skimmed through the accompanying documents and it covers about all conceivable combination of forests, trust relationships and complex dns zone scenarios.

 

We have just one server and one domain and it wasn't easy to figure out what in those 82 pages that was applicable to my situation.

 

Does it exist any good '3rd party' how-to or white paper for a simple single-server single-domain rename..?

 

I'd also ask for the same concerning moving services and files from w2003 server to new hardware. Does any of you know about good 'practical' how-tos for this too..?

 

Thanks anyway ;-)

 

/johnny

[Geoff]

Does it exist any good '3rd party' how-to or white paper for a simple single-server single-domain rename..?

 

http://thelazyadmin.com/index.php?/archives/446-Domain-Rename-Part-1-Setup.html

 

 

I'd also ask for the same concerning moving services and files from w2003 server to new hardware. Does any of you know about good 'practical' how-tos for this too..?

 

Which services do you wish to move? Everything? Or only some services?

 

As for data, you can either transfer them across the network directly (for example with robocopy), or use whatever disaster/backup recovery system you have to restore your data (we use NTBackup here for such things).

[DMcCoy]

Don't you have to perform the rename with a non DC member server? Its been a while since I did mine so I can't remember

[johnny]

Which services do you wish to move? Everything? Or only some services?

 

This particular w2003 50 users dc box does dhcp, dns, some printing and home folders.

 

On the new hardware we have installed w2003r2 std server. I want to move most of the old user stuff over with as least hassle as possible.

 

If possible I want the new hardware to take over the old server's IP address. Is this practically possible, and if yes, when in the process should I make the change on the old server's IP?

 

To transfer AD, do we set up the new hardware to be a secondary DC? Will all computer and user accounts, OUs etc be correctly replicated then?

 

For the home folders, is robocopy the best solution..?

 

What about the user profiles? Does it exist an automated way to push these over..?

 

If we succeed in most of the above, will the users only need to select the new domain name from the drop-down list when logging in, do will there be more work to do locally at their machines..?

 

Anyhow, thanks for urls or hints on these operation too ;-)

 

/johnny

[Geoff]

If possible I want the new hardware to take over the old server's IP address. Is this practically possible, and if yes, when in the process should I make the change on the old server's IP?

 

I'd do this last. Once everything is moved you can simply change the servers IP address and reboot.

 

To transfer AD, do we set up the new hardware to be a secondary DC? Will all computer and user accounts, OUs etc be correctly replicated then?

 

Promote the new server to being a DC. Run them concurrently for a while and see if any problems crop up. If nothing goes wrong demote the old server.

 

For the home folders, is robocopy the best solution..?

 

The key is to use a method of copying that understands and preserves your ACL structure.

 

What about the user profiles? Does it exist an automated way to push these over..?

 

Depends, where do they live at the moment?

 

If we succeed in most of the above, will the users only need to select the new domain name from the drop-down list when logging in, do will there be more work to do locally at their machines..?

 

The process will be transparent to the users.

[johnny]

The key is to use a method of copying the home folders that understands and preserves your ACL structure.

 

Would that be robocopy from \\servername\home$ to \\newservername\home$..? Or does it exist a more elegant and bulletproof solution?

 

... where do the profiles live at the moment?

 

They are on a separate share named \\servername\profile$

I plan to create a similar share on the new server, but which options do I have to push them over so that they will be accessable by the users..?

 

Thanks for your comments, highly appreciated ;-)

 

/johnny

[Geoff]

Would that be robocopy from \\servername\home$ to \\newservername\home$..? Or does it exist a more elegant and bulletproof solution?

 

Robocopy will work fine, care must be taken with the command line options though otherwise it will not copy everything you want.

 

They are on a separate share named \\servername\profile$

I plan to create a similar share on the new server, but which options do I have to push them over so that they will be accessable by the users..?

 

Well, assuming you copy the contents of the share correctly, all you have to do is alter the GPO's/User accounts to point to the new profile location.