UAC, Logon Scripts, and the Launchapp.wsf workaround

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Antony Iadarola — Wed, 05 Sep 2012 15:58:00 GMT

Changing your GPO Login script to Inject directly into registry seems to work without this messing about.

Example:

$sLetter = "K"

$sUNC = "\\Server1\MyServer"

New-Item -Path Registry::HKCU\Network\$sLetter

New-ItemProperty -Path Registry::HKCU\Network\$sLetter -Name "RemotePath" -PropertyType String -Value $sUNC

New-ItemProperty -Path Registry::HKCU\Network\$sLetter -Name "UserName" -PropertyType String -Value ""

New-ItemProperty -Path Registry::HKCU\Network\$sLetter -Name "ProviderName" -PropertyType String -Value "Microsoft Windows Network"

New-ItemProperty -Path Registry::HKCU\Network\$sLetter -Name "ProviderType" -PropertyType Dword -Value 0x00020000

New-ItemProperty -Path Registry::HKCU\Network\$sLetter -Name "ConnectionType" -PropertyType Dword -Value 0x00000002

New-ItemProperty -Path Registry::HKCU\Network\$sLetter -Name "DeferFlags" -PropertyType Dword -Value 0x00000004

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Michael Murgolo — Fri, 17 Dec 2010 15:55:22 GMT

Tim Bernhardson,

I was just looking at MSDN and you may also have to set the userid for the trigger as well. So you may need this additional change.

Change this:

Set trigger = triggers.Create(TriggerTypeRegistration)

To this:

Set trigger = triggers.Create(TriggerTypeRegistration)
trigger.UserId = strNTUserPath

Let me know how it goes.

Michael Murgolo

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Michael Murgolo — Fri, 17 Dec 2010 15:22:14 GMT

Tim Bernhardson,

Perhaps making the task name user-specific will help for the terminal services scenario. Try the following change and let me know if it works. If it does I'll change the download.

Change this:

strTaskName = "Launch App As Interactive User"

to this:

    Set objWshNetwork = CreateObject("Wscript.Network")
    strUser = objWshNetwork.UserName
    strDomain = objWshNetwork.UserDomain
    strNTUserPath = strDomain & "\" & strUser
    strTaskName = "Launch App As Interactive User - " & strNTUserPath

Thanks,

Michael Murgolo

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Tim Bernhardson — Fri, 03 Dec 2010 16:20:22 GMT

Works fine on single user computers, however on Servers ( I.E. Terminal Services ) it only works for the first session for Administrative users - the scheduled task always runs in the first session so if you have multiple sessions on the server only the first one gets the maps...

Any idea of a work around?

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

eli — Sun, 29 Aug 2010 10:33:02 GMT

when you want to run exe it doesnt run so i changed it like this:

If WScript.Arguments.Length <> 2 Then

WScript.Echo "Usage: cscript launchapp.wsf <AppPath> <Arguments>"

WScript.Echo "Usage: if there are no arguments use """""

WScript.Quit

End If

strAppPath = WScript.Arguments(0)

strAppArgs = WScript.Arguments(1)

If GetWmiPropertyValue("root\cimv2", "Win32_OperatingSystem", "BuildNumber") >= 6000 Then

' Running on Vista or higher. Check if running elevated.

If IsElevated Then

LaunchAsScheduledTask strAppPath,strAppArgs

Else

LaunchDirectly strAppPath,strAppArgs

End If

Else

' Running on legacy OS (XP/2003 or lower).

LaunchDirectly strAppPath,strAppArgs

End If

Sub LaunchAsScheduledTask(strAppPath,strAppArgs)

Dim Action

Set Action = taskDefinition.Actions.Create( ActionTypeExecutable )

Action.Path = strAppPath

Action.Arguments = strAppArgs

WScript.Echo "Task definition created. About to submit the task..."

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Michael Murgolo — Sun, 22 Aug 2010 00:26:41 GMT

Heath,

I updated the script to handle the case when running on a legacy OS (XP/2003). Give it a try.

Michael Murgolo

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Heath — Thu, 12 Aug 2010 20:10:34 GMT

I'm not a VB programmer so what could I add to get it to work in a XP, Vista, and Win 7 (both 32 and 64bit) environment. I know it's not working in Windows XP right now.

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Michael Murgolo — Wed, 28 Jul 2010 13:45:07 GMT

Brett,

I know of a few customers using this successfully, so this may be due to Sysvol permissions in your environment. Can your standard users launch the script directly from the Sysvol folder?

Michael Murgolo

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

Brett — Mon, 26 Jul 2010 19:57:39 GMT

Well, the script appears to half work. While trying to use the LaunchApp helper, things work good for administrators. However, for non-elevated users, the user does not have enough permissions to launch the logon script. Any workaround for this?

re: UAC, Logon Scripts, and the Launchapp.wsf workaround

John Hartsell — Sat, 10 Jul 2010 03:18:07 GMT

Thank you. Works great....