New Server

mmerry

Active Member
Reaction score
113
Location
Minnesota
Probably overthinking this but want to get some input.

Creating a new file server in a new location so we can decommission the old machine. Both machines are currently set up and I have DFS running to keep data synced between them. So far so good.

Once I turn off the old file server, I cannot rename the new file server to the old name. Basically going to a new naming convention. There are a lot of automations and scripts that point to the old file server name. Rather than having to edit everything, I want to use DNS to point to the new server. Basically, if the end users types \\oldserver they are redirected to \\newserver.

What record do I do, PTR or CNAME? For the life of me, I think I forgot how to do it in my old age. Is there a way to test this locally without doing a DNS record so I don't screw up the entire company for a 15 minute test? I tried the host file but no luck.
 
PTR is a reverse record, resolves IP address to the name.

What you need is a CNAME record, and a DNS resolver configured with the appropriate suffix so the short name resolves correctly.

Also, I'd be looking REALLY HARD at editing all of those scripts to use the DFS name instead, so you can move things around in the future easier, or migrating to SharePoint and abandoning the entire concept of a file server.
 
In my >30 years of doing SMB support....which means....lots and lots and lots ...and lots....of server migrations, I can't think of a single instance where I wanted to keep the old server name.

Yeah a PTR can keep the old server name around, but...like Rob said above...just for moving forward, I'd take the time to edit those automations/scripts. And I'm curious...what are some examples of those?
I mean, the old fashioned logon.bat files to map drives or do the old fashioned printui push or..other things...those are simple.
The more modern version of using group policy to push printers and drive mapping...easy.
Group policy in general to "push stuff"...simple.
 
The scripts and automations are not IT related. We push using GPO and Intune. They are for our CAD and development departments in the automations to produce the files that go to production machines. Luckily I don't do the editing on those scripts, but if I just made the change, production would shut down. Done this enough to know that I needed to verify stuff before making the change. Just getting old and second guessing everything I know lately.
 
Back
Top