This post is more than 5 years old
19 Posts
0
149884
March 12th, 2013 13:00
Script assigned to user not execute
Hello,
I've a problem with the execution of scripts assigned from Quest Console (7.6). In Resources/Scripts I've 2 scripts (one VBS and other CMD). Scripts are located at an UNC resource accessible by all users. Script run manually works perfect. But not runs automatically in desktops running VDI with Windows 7 SP1.
Any ideas?
No Events found!
DELL-David Y
228 Posts
1
March 12th, 2013 13:00
Hi Carlos,
I have seen a similar problem before, in my case the script ran perfectly when I executed it manually but did not produce a result when executed through a GPO.
I did some investigation and learnt that it could be caused by the UAC settings on the system you are testing the policy. With UAC enabled any scripts that are run from a policy will execute, but under a different security context to the user. When UAC is enabled the logon/logoff scripts are executed by an Administrative user, the desktop then loads afterward as the user.
One suggestion to resolve the problem was to firstly apply this registry setting:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
EnableLinkedConnections =(dword)1
Google UAC and logon scripts and you will find further information and suggested workarounds.
I hope this helps
David
carlos.nova-iny
19 Posts
0
March 12th, 2013 13:00
Ok, with your info. I'll try with GPO directly (my script only creates internet shortcuts in user desktop). Perhaps, the folllowing link is useful for other people:
http://blogs.technet.com/b/elevationpowertoys/archive/2010/05/25/uac-logon-scripts-and-the-launchapp-wsf-workaround.aspx
It's a "launcher" that detects UAC and in this case, set a task for execute in user environment.
Regards