Hello everybody,
Faced with strange situation. I have DFS namespace based on Windows Server 2012R2 and same RDS server. Issue is very simple: if you map DFS share to network drive, no matter how, via logon script or via group policy, the first user which logs in get this drive ok, second logged in user gets red X on this drive but still able to access it.
If I map this drive via GPO, after second user log in I can see warning in Event Viewer
The user 'R:' preference item in the 'Test DFS mapped drive {7CDE4506-692E-422B-9299-D12CB15F7CC6}' Group Policy Object did not apply because it failed with error code '0x80070055 The local device name is already in use.' This error was suppressed.
No matter if checkbox "Run in logged-on user's security contest" were marked or not.
After some tests I recognised following:
1. If you map drive manually from Windows Explorer, second logged in user gets same red X on that drive
2. If you map drive manually and use "connect using different credentials" options and even enter credentials of logged on user, then the problem goes away.
3. So I created script which do it in following way:
net use Z: /delete
net user Z: \\dfsnamespace\root /user:domain\%username%
This works fine but I'm wonder that this bug a bit well known on Google and there is no any reaction from MS as well about this point. Could please hint me anything about this issue? I don't like this workaround and I think there has to be another way to solve this issue.