/build/static/layout/Breadcrumb_cap_w.png
06/27/2019 281 views

Seems that Powershell , Appdeploy Toolkit does not like the following command, nor does using the install in Autoit. I've believe they don't like the %USERDOMAIN%\%USERNAME%. Anyone run into this and have a fix or workaround other than using a batch file. Trying to get away from batch files for packages and applications in SCCM.

Execute-MSI -Action 'Install' -Path 'lsf10.1_win-x64.msi' -Transform 'lsf10.1_win-x64.mst' -Parameters 'ADDLOCAL=ALL ALLUSERS=2 ARPNOMODIFY=1 CLUSTERADMIN=%USERDOMAIN%\%USERNAME% CLUSTERNAME=sas_cluster SHAREDDIR="\\Server name\sas_admin_grp\Prod\SAS_Clients\lsf_conf_win\conf"'

0 Comments   [ + ] Show comments

Comments



Community Chosen Answer

1
Trying to get away from batch files for packages and applications in SCCM.

So maybe Google how to access environment variables in Powershell?

Answered 06/28/2019 by: VBScab
Red Belt

All Answers

0

https://www.itninja.com/question/running-package-as-a-specific-account

and leave switch out and it should then run as that account


CLUSTERADMIN     Optional. Specify the cluster administrator OS user account name in the format domain\user_name.

If you are using a local user, specify .\user_name and ensure that the user password is the same on all hosts.

The default is your installation account.


Answered 06/27/2019 by: SMal.tmcc
Red Belt