Karen Rodgers
asked on
DFS CONSOLIDATION ROOT Help needed on using old UNC file shares
I have set up DFS on the new server (2016) and I have created the namespace (newserver\#Oldserver) with a folder called the (Share) linking back to the Net App Nas hidden share.
Then I changed the DNS entry for the (oldserver to point to the new server) example
OLDSERVER 192.168.1.1 changed to 192.168.1.2
Newserver 192.168.1.2
I also changed the SPN for the OLDSERVER as follows:
setspn -d HOST/OLDSERVER OLDSERVER
setspn -d HOST/OLDSERVER.TEST.NET OLDSERVER
setspn -a HOST/OLDSERVER NEWSERVER
setspn -a HOST/OLDERVER.TEST.NET NEWSERVER
This all worked fine.
The problem is now that the \\OLDSERVER\SHARE still does not work but I can see \\OLDSERVER\#OLDSERVER\FIL ES, and I need to somehow remove the #OLDSERVER so that the old UNC paths still work.
What have I done wrong?
Then I changed the DNS entry for the (oldserver to point to the new server) example
OLDSERVER 192.168.1.1 changed to 192.168.1.2
Newserver 192.168.1.2
I also changed the SPN for the OLDSERVER as follows:
setspn -d HOST/OLDSERVER OLDSERVER
setspn -d HOST/OLDSERVER.TEST.NET OLDSERVER
setspn -a HOST/OLDSERVER NEWSERVER
setspn -a HOST/OLDERVER.TEST.NET NEWSERVER
This all worked fine.
The problem is now that the \\OLDSERVER\SHARE still does not work but I can see \\OLDSERVER\#OLDSERVER\FIL
What have I done wrong?
I do not understand the ultimate objective of this exercise, can you explain, also let me know a brief overview of before /after and expected environment.
ASKER
I am trying to move some standard shares from an old 2008R2 Server to a Share on a Net App SAN (NAS) or a 2016 server. The problem is I need to maintain the original file UNC paths for critical programs and data that is run from the user's desktops.
After reading through posts on my previous question, it was suggested I should use DFS to do the job and replace the file share.
The overview is: I have an old 2008r2 server as a massive file server that needs to be replaced by 2016 server. The server is a very old physical server and it is also out of warranty. I need to keep all UNC paths \\2008r2\file share the same as they were originally as the server is used by 3 or more domains. I have created some hidden shares on a Net App SAN/NAS so I can transfer the files to. Problem is I am unable to keep the UNC paths so DFS was suggested.
Required Outcome: I need to be able to use the original UNC paths so users and programs are unaware that the files are now on a new server and using a DFS Share.
After reading through posts on my previous question, it was suggested I should use DFS to do the job and replace the file share.
The overview is: I have an old 2008r2 server as a massive file server that needs to be replaced by 2016 server. The server is a very old physical server and it is also out of warranty. I need to keep all UNC paths \\2008r2\file share the same as they were originally as the server is used by 3 or more domains. I have created some hidden shares on a Net App SAN/NAS so I can transfer the files to. Problem is I am unable to keep the UNC paths so DFS was suggested.
Required Outcome: I need to be able to use the original UNC paths so users and programs are unaware that the files are now on a new server and using a DFS Share.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.