RunAsWait and O.S. > win7

[seagull62]

Good morning to the whole forum.
In the company where I work a script is used, invoked at the time of logon to the domain, which checks the installation status of the antivirus client and, if it does not meet the minimum requirements, the setup.exe is run for installation and / or update antivirus client.
Starting from the version of the Win8.1 operating system, the execution of the setup command ends in error due to security problems.

Below is an excerpt of the script in the section where setup.exe is executed.

"...

RunAsWait("<user>","<domain>","<pwd>",0,$server,@TempDir,@SW_HIDE)

..."

Please Note:

- the user is a domain user that is a member of the Domain Users group that is a member of the local Administrators group of the computer on which the script runs;

- the $server variable represents the network path where the setup executable is located.

I searched the net and carried out various tests but without yet finding the one that solved the problem of non-execution.
 

Thanks in advance.

 

[JLogan3o13]

Can you define "due to security problems"? Do you simply mean the UAC is popping up?

[Subz]

Try running it from a "Computer Startup" Script via GPO this should run the software as System account and means you no longer require username and password and shouldn't invoke UAC prompt if enabled.  You can also try having the script download the installer locally and remove the folder afterwards as I've found some AV can interrupt network communication stopping the install from finishing, having the software run locally should overcome that issue.

[seagull62]

UAC disabled

[seagull62]

"You can also try to download the installer locally and remove the folder afterwards."

Errata Corrige - All the antivirus client installation package is copied locally before attempting to run the setup. I was wrong to say that the program was run from a network resource.

[JLogan3o13]

7 minutes ago, seagull62 said:

UAC disabled

So would you please share the exact wording of the "security problem"? Not giving us a lot to work with.

[Subz]

Try and change the third parameter to 1, ideally if you can tell us what error you're getting will be most helpful otherwise just guessing.

[seagull62]

@Subz

Executing installation script C:\Users\006101~1\AppData\Local\Temp\sep_inst\setup.exe;
Errore RunAsWait: 1

[seagull62]

What is the difference between using RunAsWait or ShellExecuteWait?
I point out that the current windows user concui is executed the script is generally not computer administrator.

[seagull62]

What is the difference between using RunAsWait or ShellExecuteWait?
I note that the current windows user running the script is generally not a computer administrator.

[Subz]

Log on as 006101... run C:\Users\006101~1\AppData\Local\Temp\sep_inst\setup.exe manually whats the result, if it popups waiting for more info then you need to add switches to your command to make it run silent.  What AV are you installing?  What switches are you using?

[seagull62]

" What AV are you installing? " SEP (14)

"What switches are you using?"  If you are referring to the switches of the AV client installation executable, none: setup.exe is executed

Thanks for interesting....

 

[Subz]

Try and use the Msi version of the install https://support.symantec.com/en_US/article.HOWTO81177.html#v8527856 this might be one of those products that uses setup.exe as a wrapper which runs another process but not with the same elevation, I've had this issue occur in SCCM before.  Anyway try msi and let us know how that goes.

[seagull62]

@Subz - I'm working on the SEP client installation solution via msi. Then I will give you feedback.  :-)