3 posts in this topic
I've abandoned the FileSelectFolder() approach and rolled my own UDF to create a dialog containing the folder list in a ListView, which seems to work fine. It's also a better fit to our requirements: we don't really want the user wandering around in the folder-selection dialog, plus the UDF displays some associated info for each folder in a second column. Thanks again to the forum members who took a look at this.
I'm writing an installer script that needs to run as Administrator so it can, e.g., write files into protected directories. The problem is that when I call FileSelectFolder(), there is a 60-second delay before the dialog appears. If I run as an ordinary user (in the Administrators group), there's no delay, but I don't think that will work: for one thing, the installer needs to create a symbolic link, which a member of the Administrators group can't do unless the program is elevated. (This is Win 7 x64.)
(The installer will be run using an Admin account; the other user accounts are locked down and don't have access to the filesystem, the Start menu, Computer, etc. - it's a turnkey system.)
Any idea what causes the delay? And is there a way around it?
After a few weeks of researching and testing, I think I have a good understanding of #RequireAdmin and IsAdmin() for an individual script. They both work in conjunction with each other and ignore whether the current user has administrator rights, or not. In other words, IsAdmin() doesn't test the user, only the declared permission level of the script it is executed in. A separate check is needed to actually confirm the user's admin level. I've included a test script that demonstrates the difference.
Here is my question: When a compiled scripts runs with administrative rights, does a script that it runs inherit those rights? Or is every script on its own? For example,
Parent Script ... (doesn't need admin rights) ... that runs:
Child Script ... that does need admin rights, and obtains them via #RequireAdmin + user's response ... and then runs:
2nd Child Script ...<< does this script execute with admin rights, or not?
If a script does not automatically inherit rights, then is there a way for a parent script that has admin rights to run a child script "with rights", so that running the child script does not result in another prompt for user permission?
Thanks in advance for any help.
;#RequireAdmin ; enable or disable this line to see the difference $AdCheck = IsAdmin() MsgBox(0, "Admin Test", "Admin is " & $AdCheck) $AdCheck = _IsAdministrator() MsgBox(0, "Admin Test", "Admin is " & $AdCheck) Exit Func _IsAdministrator($sUser = @UserName, $sCompName = ".") Local $aCall = DllCall("netapi32.dll", "long", "NetUserGetInfo", "wstr", $sCompName, "wstr", $sUser, "dword", 1, "ptr*", 0) If @error Or $aCall Then Return SetError(1, 0, False) Local $fPrivAdmin = DllStructGetData(DllStructCreate("ptr;ptr;dword;dword;ptr;ptr;dword;ptr", $aCall), 4) = 2 DllCall("netapi32.dll", "long", "NetApiBufferFree", "ptr", $aCall) Return $fPrivAdmin EndFunc
I have a problem with a script when I run it as admin. I am trying to get all the mapped drives from the local pc. This is the script I am using
;~ #RequireAdmin ; This switch is going wrong #include <Array.au3> If isAdmin() then MsgBox(0,"ADMIN","ADMIN") Else MsgBox(0,"NOT ADMIN","NOT ADMIN") EndIf $x = getMappedDrives() _ArrayDisplay($x) Func getMappedDrives() Dim $aDrives $objWMIService = ObjGet("winmgmts:\\" & @LogonDomain & "\root\CIMV2") $sQuery = "Select * From Win32_LogicalDisk Where DriveType = 4" $colItems = $objWMIService.ExecQuery($sQuery, "WQL", 48) If IsObj($colItems) Then For $objItem In $colItems ReDim $aDrives[UBound($aDrives) + 1] $aDrives[UBound($aDrives) - 1] = $objItem.DeviceID $aDrives[UBound($aDrives) - 1] = $objItem.ProviderName Next Return $aDrives Else SetError(-1, -1, -1) EndIf EndFunc When I run it without the '#RequireAdmin' switch it works fine. When I turn on the '#RequireAdmin' switch is gives me an empty array.
This code is part of a bigger project and my project always runs as admin. I dont know why it is doing this, because I am not using #RequireAdmin in the project.
Is there an other better way to get the mapped drives that works for me? Or am I doing something wrong?
I hope someone can help me.
A specific executable compiled with Aut2Exe 126.96.36.199 running under Windows 7.1/64 requests UAC/UAE elevation if it is compiled with the RequireAdmin option. Which is the expected behaviour.
However, when the same code is compiled with 188.8.131.52 no UAC prompt occurs, and instead the exe (or possibly the calling program) reports 'CreateProcess failed; code 740' and fails to launch.
Just wondering if there are any known differences here. If the issue hasn't been seen before I'll do a few more tests to try and establish under what conditions it occurs.
I have a script that updates a program across on many computers company wide. Occasionally it needs to install updates of other programs but sometimes it definitely doesn't want to have administrator privileges itself - so I have called little scripts to install what is needed. This worked fine in 184.108.40.206. It seems to have changed in 220.127.116.11
As a test I wrote two very little scripts: TestRA
#RequireAdmin MsgBox(0,"TestRA","This is running") and Testnon
MsgBox(0,"Test","This is running") then I wrote a script to call them.
$a=Run(@ScriptDir & "\testnon.exe") $a1= "No" if @error Then $a1="Yes" $b= Run(@ScriptDir & "\testra.exe") MsgBox(0,"Testing","Test non =" & $a & $a1& @CRLF &"Test ra=" & $b & @error) $a=RunWait(@ScriptDir & "\testnon.exe") MsgBox(0,"Test","Testnon = " & $a & @error) $b= RunWait(@ScriptDir & "\testra.exe") MsgBox(0,"Test","TestRA = " & $b & @error) I have just installed the latest SCiTE.
Attached are the various output messages.
As you can tell Test RA didn't run either on Run or RunWait. Can anyone tell me what is wrong?
Any ideas gratefully received