I'm a domain admin on a Win2012 domain with a Win10 workstation, and I'm finding that my drive mappings appear to be split and not entirely persistent.
Mappings through Windows Explorer or a normal command prompt work for accessing file shares, and browsing the network, persist between sessions, and show up under net use in a normal command session. But they do not work for any applications that require administrative access to mapped drives. Especially if the program uses the "Browse for Folder" dialog to locate resource files, or if you wish to pin recently used files to an application such as Excel in the Start menu.
To enable those mappings I have to open an elevated command session and run the mappings with the net use command. But these mappings don't remain persistent between sessions. And if I map these under an elevated command prompt without the normal mode mappings having been done, the mappings don't show in Windows Explorer. However, applications that require the "Browse for folder" dialog will see their resources properly.
I hope I've explained this properly, and feel free to ask for clarifications, but I'm at a complete loss as to what is causing this. I have a feeling its some sort of policy conflict since I'm a domain admin and under a completely different OU than average users, both my user account and my workstation. We only have one other domain user on Win10 as yet, and his computer doesn't exhibit any of the behaviors mine does.
Incidentally, I recently wiped my workstation and reinstalled a clean version of Win10 thinking perhaps the upgrade from Win7 had created a fault, but even with the wipe the issue exists.
I would greatly appreciate any insights into why this is occurring, and where I may look to try and diagnose the issue.