We are using a a Powershell script that maps a drive. Running the script locally (non-elevated) works perfectly. Running the script using group policy does not work as expected.
I've put the script in User Configuration | Policies | Windows Settings | Scripts | Logon
When running the script from the GPO, the script completes but does not map drives in an accessible manner. No errors come up. Looking in Windows Explorer the mapped drive is not there. However, if I run "net use" from an elevated command prompt I see the drive. For some reason that I can't put my finger on, the script is running with an admin token when running from GPO. It maps the drive, but elevated, so I can't access it without elevating everything.
The script is just a batch file that runs this command:
powershell.exe -NoProfile -ExecutionPolicy bypass -command ScriptName.ps1
The Powershell script runs a net use command (among other things) to map the drive. Again, if it is run locally (without any elevation) the drive maps with no issue, accessible from Windows Explorer, etc.
The script is running on a Win8.1x64 machine on a Windows 2012 AD domain.