Server transition, question about aliasing server name for shares
Posted on 2011-09-17
Hello! I have a 24/7 location that has outgrown their existing 2003 Windows server (ServerA). It is part of a multiple site, single domain deployment, and is that site's DC, GC, DNS, DHCP server, and file server.
A new server with server 2008 (ServerB) was configured for this location, joined to the domain and promoted to DC. It has been onsite as we copy data, permissions and create identical shares for awhile, and its time to take ServerA out of production.
This location has no local support and is out in the sticks, and each of the users have individually mapped drives to file shares. Because of the inconsistency in the drive letters used, I can't simply write a login script to disconnect all existing and reconnect to new shares-- the users will be back in at 10:00 pm Sunday for start of shift with no support, so the new server cutover has to be transparent.
I would like to turn off the shares (native Windows, no Mac shares), demote ServerA. I want "ServerA" to remain online for admin access only (in case of emergency due to lack of local support). I can rename ServerA, and change the IP address. I need \\serverA\datafiles and all the other shares to now transparently connect to the identical shares on \\serverb\.
I'm thinking DNS entries and WINS entries for "ServerA" pointing to "ServerB", but if I recall, I had trouble with this theory in the past (shares would enumerate for \\serverb\datafiles, but not using aliased name).
Looking for input prior to digging myself into a hole. TIA!