Unisys1
asked on
Server share to DFS Migration without End User intervention
Currently we have 2 AD sites and 1 Files server. The file server is located a site 1. The files server is named \\ServerA. All the users at both sites have mapped share of \\ServerA\Share
I want to decomission/replace the ServerA with ServerB at site 1, add Server C to Site 2, and then make a Domain DFS replication & Namespace between ServerB & ServerC. The question is...... Is there anyway I can make the Namespace shares look like \\ServerA\Share, so that end users will never notice the change?
I want to decomission/replace the ServerA with ServerB at site 1, add Server C to Site 2, and then make a Domain DFS replication & Namespace between ServerB & ServerC. The question is...... Is there anyway I can make the Namespace shares look like \\ServerA\Share, so that end users will never notice the change?
ASKER
Is there anyway, perhaps DNS, to make serverA = "domain.name" so the old users drive mappings would work?
Hmm...I'm not sure, but if you care to wait until Monday I'll happily give it a try on my DFS.
Do clients access the share via a UNC path, or do they all have drive letters mapped? If it's a drive letter mapping, then it shouldn't be too much trouble to use a login script to disconnect the old mapping & reconnect to the new path.
Do clients access the share via a UNC path, or do they all have drive letters mapped? If it's a drive letter mapping, then it shouldn't be too much trouble to use a login script to disconnect the old mapping & reconnect to the new path.
ASKER
Thanks tgerbert, I'd love any help you can give. I am not this Domain's Admin, I was just asked if I could set up a better solution for our 2 WAN linked sites to makeUsers' shares faster, redundant. Currently all of the shares were set up by someone without using a login script. I am just doing what I can to make this transition to a better system, seemless. But.... we will do what is necessary to get this done, and if that means users have to remap drives, then so be it. I am just trying to avoid this for the ~50+ users.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I looked at my problem more and I tried just making a CNAME of ServerA= domain.name and I got undesired results of "A duplicate name on the network exists". Weird. But taking your script into consideration, I think I'm going have to remap their shares, and a VBScript sounds good. I will even share it and have the users run the script them selves..... I believe....
So basically, I will be doing lots of file movements and new DFS folders do minimize our domain shares. I.E.
\\ServerA\Share
.....will become.....
\\domain.name\DFSShare\DFS folder
And I will use your script to make that happen. Thanks!
So basically, I will be doing lots of file movements and new DFS folders do minimize our domain shares. I.E.
\\ServerA\Share
.....will become.....
\\domain.name\DFSShare\DFS
And I will use your script to make that happen. Thanks!
Although, you can include \\ServerA\Share in your DFS topology, this way either path will work until you re-configure the clients.