I am looking at setting up DFS in our domain and hope to use an existing File server which hosts Homefolders as a DFS server.
I have set up 2 test File servers called Testserver1 and Testserver2. Both these servers are running Server 2012 R2. I have set up test accounts testuser1 and testuser2.
On the test servers and using the test accounts, I have set up test Homefolders on a share "\\ Testserver1\testhomefolder", so that the Homefolders are "\\ Testserver1\testhomefolder\testuser"1 and "\\ Testserver1\testhomefolder\testuser2".
On File servers Testserver1 and Testserver2 I have set up DFS and set up a Namespace "\\ domain\testhomefolder" and a Replication to replicate between the 2 servers. This Namespace seems to function fine and is tolerant to one of the servers being offline, where connecting to "\\ domain\testhomefolder" and any of its child items works as normal.
The issue happens when I change the AD accounts Homefolder field for either testuser1 or testuser2 from "\\ Testserver1\testhomefolder\testuser1" and "\\ Testserver1\testhomefolder\testuser2" to "\\ domain\testhomefolder\testuser1" and "\\ domain\testhomefolder\testuser2" respectively, and then log on as either testuser1 or testuser2.
At the point of logging on as either testuser1 or testuser2 after the Homefolder field has been changed, the old Homefolder is deleted. A log off and logon creates a new Homefolder, but it is empty and all contents of the original folder is lost.
Can anyone please advise as to what I need to do to ensure that the original Homefolders are not wiped when changing the Homefolders for each account from a Servername to a Namespace?
NB - the UNC paths don't actually have a space after the "\\". I added in a space so that IE did nothelpfully turn them into links which stopped me submitting this question.