Re use old servername or not?

[R. Wilco]

He everyone,

I would like your opinion about the following issue:

Currently we are planning to replace our current file and print server for two new file and print servers.

Now we have disccusion about using the old name for one server and a new name for the second server.

What is the best option: two names wich have not been used or recycle the name which has the advantage you don't have any problems with documents which includes links to other document on the same file and print server.

So what do you think: Two new servernames or one server using the old name and the other one gets a new name.

I hope you can help,

Roger

[Gfuss]

Roger,
I've always went with new names. This makes it easier to tell which server is which and migrate your shares and files as needed. Once you have migrated all of the printers and documents, you should be able to create a DNS (A) record for the old server to point at the new one. For example, you would make a DNS entry for server01 to be the IP address of server02. Any requests for documents on server01 would be directed to server02. This will ensure you will not need to update anyone documents to reference the new server.

I'd also go with new names if these servers are in a directory of some sort (NDS, Active Directory, etc.). You will avoid any directory conflicts if you bring the new server in with a new name.

-Gfuss

[Peter Turek]

If you're using windows 2003 AD you should note there are issues where you cannot just alias a server name in DNS and it will allow hosts to connect via the alias.

You will be foiled by Kerberos authentication.

To get around the problem you need to enter registry keys called "disablestrictnamechecking" and "optionalnames" in LANMANSERVER, restart the server or just restart the server service and netlogon service.

http://support.microsoft.com/default.aspx?scid=kb;en-us;281308

You also cannot alias existing existing server names without problems with SPNs, also a kerberos issue. The old server really needs to be dead and removed from AD and then you won't have any problems. The reason is you cannot have duplicate SPNs.

[Pavel Bradut Boghita]

I second going with two new names.
I would guess that a way around the linking problems could be having a dns entry linking the old name to the ip address of the new server