WinBatch Studio Mapped Drives Issue

 Keywords: UAC WBSTUDIO STUDIO NETWORK DRIVES MAPPED MAP Vista Win7

ISSUE: When running as an Administrator, the user has two contexts: the limited user context, and the administrator context. When you map drives in Windows Explorer, they are added only for the limited user context. Thus when the WinBatch Studio runs in the administrative context, no mapped drives are 'seen' by WinBatch Studio. WinBatch Studio runs with user elevation 'HighestAvilable', which means when running under an Administrator account the script is running in the context of the administrator NOT the user. OPTIONS:

Turn off UAC.
Perhaps map the drives under the administrator context in the first place.
Run the WBStudio_IT.exe instead which uses the AsInvoker manifest (this tells WBStudio_IT.exe to run within the user level context ).
You can set this Registry value and you will get access to those drives from both 'integrity' levels. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLinkedConnections =(dword)1
Administrative users should map network drives under the limited user token. This mapping is accomplished by scheduling the script to run using the task scheduler. The task scheduler launches the script under the administrative full token, thereby allowing Windows Explorer, other limited token processes, and the elevated token process to view the mapped network drives. Reference: See "Group Policy Scripts can fail due to User Account Control" section of this doc: http://technet2.microsoft.com/WindowsVista/en/library/5ae8da2a-878e-48db-a3c1-4be6ac7cf7631033.mspx?mfr=true

Article ID:   W17495

File Created: 2010:04:07:07:44:18

Last Updated: 2010:04:07:07:44:18

Database Search

TechHome

WinBatch Studio Mapped Drives Issue