replace windows 2000 server

[Guest]

I’m going to replace a “old†windows 2000 file server with a “newer†server
which also run windows 2000. What will be the steps to maintain all shares,
permissions & UNC path? Do the followings be OK?

1. Setup a new windows 2000 server named it “newer†& join AD.
2. Copy all files from “old†to “newerâ€.
3. Shut down “oldâ€.
4. Rename “newer†to “oldâ€.

I’ve search the Internet & found info only for win2000 migrate to win2003.
I also need to minimize the downtime as we are running 24hrs a day. Any
suggestions?

 

[Meinolf Weber]

Hello KK,

Your plan sounds ok. For copying to the new server you can make a backup,
that has the advantage, that also the configured user rights will be saved
and if you restore it to the new location, you don't have to reconfigure
them. Just share the folders again and it should work.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

 

[Pegasus \(MVP\)]

Instead of recreating the shares, the OP could export the key
below on the old machine, then import it on the new server.
hklm/system/currentcontrolset/services/lanmanserver/shares

 

[Guest]

Thanks Meinolf,

Is that be better to restore files from backup tape instead of copying?

Friend of mine questioning about the UID of the "old" server that I can't
simply rename the "newer" to "old" because the UIDs of these servers are
unique.

 

[Meinolf Weber]

Hello KK,

see inline

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

Thanks Meinolf,

Is that be better to restore files from backup tape instead of
copying?

Better, i don't know, but easier because you keep your security configuration.
And it can happen during the copy that really long filenames make problems.

Friend of mine questioning about the UID of the "old" server that I
can't simply rename the "newer" to "old" because the UIDs of these
servers are unique.

Every server has an unique Security Identifier (SID), except the machine
is cloned and you not run sysprep after the cloning. The SID depends NOT
on the computername. So if you change the name the SID will be the same.
So rename them so often you like, but give Domain controllers time fro replicating
the changes.

 

[Guest]

thanks for your help.

Hello KK,

see inline

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.


Better, i don't know, but easier because you keep your security configuration.
And it can happen during the copy that really long filenames make problems.


Every server has an unique Security Identifier (SID), except the machine
is cloned and you not run sysprep after the cloning. The SID depends NOT
on the computername. So if you change the name the SID will be the same.
So rename them so often you like, but give Domain controllers time fro replicating
the changes.