New server considerations

[itaviator]

We're replacing one of our servers in the next couple of weeks. I'd like to get some feedback on whether anyone sees problems with my approach. My boss wants to use the same server name on the new server (he's leary of change). The new server is currently named "Test2003" and the current one being replaced is named "Calvin". "Calvin" is currently our second DC (not the master catalog).

1. Copy data from old to new.
2. Remove "Calvin" from AD role. Reboot.
3. Shutdown "Calvin" and remove computer account from AD.
4. Rename "Test2003" to "Calvin". Reboot.
5. Add AD role to new "Calvin".
6. Install any apps and make sure of share/security permissions.

Any feedback will help. Thanks.

Systems Administrator

 

[pagy]

You've got a server called Calvin??

Your steps look good to me

Your server is really called Calvin??

Paul

MCSE 2003

"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[SteveRoadWarrior]

To start, shut down Calvin and run the following tests:
- dcdiag (of COURSE it will fail replication tests, you're very interested in what FSMO roles it holds), why not choose the comprehensive tests
- open Windows Address book and click search, choose Active Directory from the drop down menu. Enter an "A" and click search. This is a decent test to see if your Global Catalog is available.
- run a full backup of your AD servers, and also as a safety net, run a windows backup and choose "Active Directory" as well as the drive(s) that hold your AD information. I like drive image software personally.
- if convenient, segment the two servers on their own private LAN during the conversion so that no other machines have the opportunity to change their passwords (this will save time during a restore)

To be safe, you should do this as part of step #3:

- remove Calvin from (AD Users & Computers) Domain Controllers OU if still there
- open sites and services and delete Calvin
- open DNS and remove all entries that point to Calvin, unless they're the only entries there (in which case, point them to your current DC)
-- be sure to check the PDC and GC entries
- run ADSIEdit and verify Calivin is gone completely

You might ask your boss what technical reasons he has for keeping the name the same. If he has none, it's better in my opinion to use a new name. The reason for this is powerful: it's always better to work from a known value than take a chance on an unknown variable. Unknown variables include some of the items I mention in step 3. If your boss was unaware of these places holding information about Calvin, you might suggest the new server be called Hobbes.

 

[itaviator]

LOL, our main DC IS called "hobbes". In fact, our email server is called "snowman". Someone here liked "Calvin and Hobbes"!! (I've only been here a little more than 2 yrs)

My boss (IT Mgr) still thinks it's the days of NT. Has got no clue when it comes to 2000 and above! He thinks people are used to seeing their mapped drives as "test on (calvin)" , so he doesn't want to hear phone calls. What an idiot. Everyone refers to the mapped drives as their letter! And the logon script takes care of that, even if we change it! But he won't listen.

Thanks for the feedback

Systems Administrator

 

[SteveRoadWarrior]

I thought that mapped drive letters were the case, but wanted to be sure. Now might be a good time to switch to DFS. Then the users will see "L: share on (domain)". In the future, users will not notice any changes if you decide to move the sharepoint to another server.

The pitch to your boss would go like this: You like stability right? Here's the Microsoft suggested method of storing data - store it on the domain. This way it will never change again.

You'll have to set this up and demonstrate it, too many NT4 admins can't wrap their heads around the concept of file shares attached to the domain...lol!