OpsiPaket: Installer Errorcode

[HiggsBoson]

Moin,

ich versuche gerade ein Paket für den vmware Horizon Agent zu bauen.
Leider schlägt die installation fehl.

"
[6] [2022-03-03 16:07:23.432] [] Changed current directory to O:\vmware-horizon-agent-ks\files1
[5] [2022-03-03 16:07:23.438] [] Execution of: Winbatch_install
[5] [2022-03-03 16:07:23.441] []
[6] [2022-03-03 16:07:23.447] [] Call ""O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=DOMAIN\userVDM_SERVER_PASSWORD=SECRET REBOOT=Force ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP" /passive /norestart /log "c:\opsi.org\log\vmware-horizon-agent-ks.install_log.txt""
[6] [2022-03-03 16:07:23.453] [] Waiting until the called process is finished
[6] [2022-03-03 16:07:23.458] [] Start process as invoker: Administrator
[7] [2022-03-03 16:07:23.465] [] Exception in StartProcess_cp: Failed to execute : 5
[4] [2022-03-03 16:07:23.469] [] Lasterror: 0 (Der Vorgang wurde erfolgreich beendet.)
[3] [2022-03-03 16:07:23.472] [] Error: Could not execute process ""O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=DOMAIN\user VDM_SERVER_PASSWORD=SECRET REBOOT=Force ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP" /passive /norestart /log "c:\opsi.org\log\vmware-horizon-agent-ks.install_log.txt""
[6] [2022-03-03 16:07:23.477] [] Set $ExitCode$ = getlastexitcode
[6] [2022-03-03 16:07:23.482] [] The value of the variable "$ExitCode$" is now: "-1"

"

Nicht wundern, das Laufwerk O kommt daher, weil ich das Skript im Skripteditor habe laufen lassen um zu debuggen.

Ich frage mich wo das problem ist.
Wenn ich von Hand auf der CMD ein "O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=DOMAIN\userVDM_SERVER_PASSWORD=SECRET REBOOT=Force ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP" mache ist alles super?

Es wird auch keine log datei nach opsi.org/logs erzeugt, was mich total wundert?
Ich bräuchte da mal einen kleinen Schlag auf den Hinterkopf

[Medard]

Hi,
bin auch nicht so bewand im Skripten aber vielleicht hilft es %scriptpath%, $LogDir$ und $ProductId$ zu benutzern bzw. erstmal testweise den opsi-setup-detector zum erstellen des Pakets verwenden?
Grüsse,
Robert

[ThomasT]

Hast du mal mit den " und ' herumexperimentiert? Gerade bei mehrfacher Verwendung von " innerhalb eines Commands kommt es da uU zu Problemen.

[HiggsBoson]

Achso, ich benutze natürlich variablen, sieht man nur nicht, weil die ausgabe oben aus dem Errorlog ist (da wurden die Variablen schon ersetz).

ich könnte das mal mit ' testen, meint ihr das Opsiscript fällt da über seine eigenen Füße?

[HiggsBoson]

"
"%scriptpath%\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v'/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=DOMAIN\user VDM_SERVER_PASSWORD=secret REBOOT=Force ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP'
"

das fällt auch auf die Nase.

Log:
"
[7] [2022-03-03 17:26:54.780] [] Exception in StartProcess_cp: Failed to execute : 5
[4] [2022-03-03 17:26:54.783] [] Lasterror: 0 (Der Vorgang wurde erfolgreich beendet.)
[3] [2022-03-03 17:26:54.786] [] Error: Could not execute process ""O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v'/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=DOMAIN\user VDM_SERVER_PASSWORD=SECRET REBOOT=Force ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP'"
[6] [2022-03-03 17:26:54.791] [] Set $ExitCode$ = getlastexitcode
[6] [2022-03-03 17:26:54.795] [] The value of the variable "$ExitCode$" is now: "-1"

"

[SisterOfMercy]

Ich frage mich wo das problem ist.
Wenn ich von Hand auf der CMD ein "O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=DOMAIN\userVDM_SERVER_PASSWORD=SECRET REBOOT=Force ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP" mache ist alles super?

This doesn't look allright:
VDM_SERVER_USERNAME=DOMAIN\userVDM_SERVER_PASSWORD=SECRET
And you might want to do this with a (confidential) product property anyway: https://download.uib.de/4.2/documentati ... ctProperty

Also, ADDLOCAL might not always work as you think. It may not install every needed part. With msi installations (which this essentially is) you do a ADDLOCAL=ALL REMOVE=useless_shit_component,crappyfeature,dumbthing
It works in this case, because the feature tree in the msi file is pretty flat. With Libreoffice this would not work.

You might also have not called this winbatch section with a /64Bit or /SysNative parameter.

You can run the installer to extract it: use the /x parameter. Then pull the needed files out of the temp directory. Rename it to horizon-agent.msi or something like that, saves you from having to edit the filename in the script every time there is a new version.
The vcredist files are just the bog standard 2015-2022 vc runtimes. I have them in another package that I use as a dependency.
Core.cab and the msi file is what you need.
Then run it like this:

Code: Alles auswählen

[Actions]
DefVar $LogDir$
DefVar $ProductId$  
Set $LogDir$ = "%opsiLogDir%"
Set $ProductId$ = "vmware-horizon-agent-ks"

Winbatch_install_64 /64Bit

[Winbatch_install_64]
"%SystemRoot%\system32\msiexec.exe" /qb-! /l*v "$LogDir$\$ProductId$-setup.log" /package "%ScriptPath%\files\VMware-Horizon-Agent-x86_64.msi" REBOOT=ReallySuppress VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=DOMAIN\user VDM_SERVER_PASSWORD=SECRET ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP

And I think the /v" " stuff goes on the end of the command, try to run it locally with /passive /norestart /log "c:\opsi.org\log\vmware-horizon-agent-ks.install_log.txt" on the end too.

You also don't want to set REBOOT to Force, because it will (may?) mean the script gets cut off. If you need to reboot after installation do this at the end of the script with the "ExitWindows /Reboot" command.

[SisterOfMercy]

And for the productproperties:

Code: Alles auswählen

[Actions]
DefVar $LogDir$
DefVar $ProductId$  
Set $LogDir$ = "%opsiLogDir%"
Set $ProductId$ = "vmware-horizon-agent-ks"

DefVar $vdm_server_name$
DefVar $vdm_server_username$
DefVar $vdm_server_password$
Set $vdm_server_name$ = GetProductProperty("vdm_server_name","hint01.konzern.intern")
Set $vdm_server_username$ = GetProductProperty("vdm_server_username","")
Set $vdm_server_password$ = GetConfidentialProductProperty("secret_vdm_server_password","")

Winbatch_install_64 /64Bit

[Winbatch_install_64]
"%SystemRoot%\system32\msiexec.exe" /qb-! /l*v "$LogDir$\$ProductId$-setup.log" /package "%ScriptPath%\files\VMware-Horizon-Agent-x86_64.msi" REBOOT=ReallySuppress VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=$vdm_server_name$ VDM_SERVER_USERNAME=$vdm_server_username$ VDM_SERVER_PASSWORD=$vdm_server_password$ ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP

And the control file would then look like this, with a dependency for the vc redist stuff.

Code: Alles auswählen

[Package]
version: 1
depends: 

[Product]
type: localboot
id: vmware-horizon-agent-ks
name: VMWare Horizon Agent
description: VMWare Horizon Agent is a piece of software blah.
advice: 
version: 7.13.1
priority: 0
licenseRequired: False
productClasses: 
setupScript: setup3264.opsiscript
uninstallScript: uninstall3264.opsiscript
updateScript: 
alwaysScript: 
onceScript: 
customScript: 
userLoginScript: 

[ProductDependency]
action: setup
requiredProduct: microsoft-vc-runtime-2015
requiredStatus: installed
requirementType: before

[ProductProperty]
type: unicode
name: vdm_server_name
multivalue: False
editable: True
description: Blah blah blah servername
values: [""]
default: [""]

[ProductProperty]
type: unicode
name: vdm_server_username
multivalue: False
editable: True
description: Blah blah blah username
values: [""]
default: [""]

[ProductProperty]
type: unicode
name: secret_vdm_server_password
multivalue: False
editable: True
description: Blah blah blah password
values: [""]
default: [""]

[Changelog]
vmware-horizon-agent-ks (7.13.3-1) testing; urgency=low

  * Initial package

 -- BOFH <bofh@bofh.co.uk>  Thu, 18 Dec 2014 18:36:41 +0000

[HiggsBoson]

Danke für die detailierte Anwort

Ich habe meine Config etwas angepasst.

[Winbatch_install_64]
"%scriptpath%\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=$vdm_server_name$ VDM_SERVER_USERNAME=$vdm_server_username$ VDM_SERVER_PASSWORD=$vdm_server_password$ REBOOT=ReallySuppress ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP"

Log:
[5] [2022-03-04 09:27:35.259] [] comment: Start setup program
[6] [2022-03-04 09:27:35.271] [] Changed current directory to U:\vmware-horizon-agent-ks\files1
[5] [2022-03-04 09:27:35.277] [] Execution of: Winbatch_install_64 /64Bit
[5] [2022-03-04 09:27:35.283] []
[6] [2022-03-04 09:27:35.291] [] Call ""U:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=KONZERN\rdsks VDM_SERVER_PASSWORD=***(confidential)*** REBOOT=ReallySuppress ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP""
[6] [2022-03-04 09:27:35.298] [] Waiting until the called process is finished
[6] [2022-03-04 09:27:35.303] [] Start process as invoker: Administrator
[7] [2022-03-04 09:27:35.358] [] Exception in StartProcess_cp: Failed to execute : 740
[4] [2022-03-04 09:27:35.363] [] Lasterror: 0 (Der Vorgang wurde erfolgreich beendet.)
[3] [2022-03-04 09:27:35.367] [] Error: Could not execute process ""U:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=KONZERN\rdsks VDM_SERVER_PASSWORD=***(confidential)*** REBOOT=ReallySuppress ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP""
[6] [2022-03-04 09:27:35.373] []
[6] [2022-03-04 09:27:35.377] [] ExitWindows set to Reboot


Nun bekomme ich ein StartProcess_cp: Failed to execute : 740

Dann habe ich einfach das winbatchinstall auf:
C:\Temp\VMware-Horizon-Agent.exe

geändert

Log:
[5] [2022-03-04 09:29:09.492] [] Execution of: Winbatch_install_64 /64Bit
[5] [2022-03-04 09:29:09.499] []
[6] [2022-03-04 09:29:09.503] [] Call "C:\Temp\VMware-Horizon-Agent.exe"
[6] [2022-03-04 09:29:09.508] [] Waiting until the called process is finished
[6] [2022-03-04 09:29:09.514] [] Start process as invoker: Administrator
[7] [2022-03-04 09:29:09.529] [] Exception in StartProcess_cp: Failed to execute : 740
[4] [2022-03-04 09:29:09.533] [] Lasterror: 0 (Der Vorgang wurde erfolgreich beendet.)
[3] [2022-03-04 09:29:09.538] [] Error: Could not execute process "C:\Temp\VMware-Horizon-Agent.exe"
[6] [2022-03-04 09:29:09.543] []
[6] [2022-03-04 09:29:09.548] [] ExitWindows set to Reboot
[6] [2022-03-04 09:29:09.554] [] Set $ExitCode$ = getlastexitcode
[6] [2022-03-04 09:29:09.561] [] The value of the variable "$ExitCode$" is now: "-1"

WTF?
Eigentlich dachte ich, das die exe gestartet wird, und ich nun einen interaktiven Installer sehe?
Denke ich da gerade falsch?

Wenn ich den Befehl über die CMD starte (natürlich mit dem richtigen Passwort), rennt alles ganz sauber durch.
"U:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=KONZERN\rdsks VDM_SERVER_PASSWORD=***(confidential)*** REBOOT=ReallySuppress ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP"

EDIT: ist evtl die Benutzerkontensteuerung das Problem? Die ist nämlich noch aktiv?

[HiggsBoson]

Ich hab jetzt spasseshalber mal den CitrixReceiver Installer nach c:\temp\ gelegt

[5] [2022-03-04 09:41:36.497] [] Execution of: Winbatch_install_64 /64Bit
[5] [2022-03-04 09:41:36.503] []
[6] [2022-03-04 09:41:36.510] [] Call "C:\Temp\CitrixReceiver.exe"
[6] [2022-03-04 09:41:36.513] [] Waiting until the called process is finished
[6] [2022-03-04 09:41:36.518] [] Start process as invoker: Administrator
[6] [2022-03-04 09:41:36.911] [] Started process "C:\Temp\CitrixReceiver.exe" with Opt:
[6] [2022-03-04 09:41:45.085] [] ExitCode 1603 Executed process "C:\Temp\CitrixReceiver.exe"
[6] [2022-03-04 09:41:45.092] []
[6] [2022-03-04 09:41:45.097] [] ExitWindows set to Reboot

funktioniert sofort....

[HiggsBoson]

Wenn ich das opsi-script als "Administrator ausführen" starte, sieht es etwas anders aus

[5] [2022-03-04 10:00:18.486] [] comment: Start setup program
[6] [2022-03-04 10:00:18.491] [] Changed current directory to O:\vmware-horizon-agent-ks\files1
[5] [2022-03-04 10:00:18.494] [] Execution of: Winbatch_install_64 /64Bit
[5] [2022-03-04 10:00:18.496] []
[6] [2022-03-04 10:00:18.501] [] Call ""O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=KONZERN\rdsks VDM_SERVER_PASSWORD=***(confidential)*** REBOOT=ReallySuppress ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP""
[6] [2022-03-04 10:00:18.503] [] Waiting until the called process is finished
[6] [2022-03-04 10:00:18.507] [] Start process as invoker: Administrator
[6] [2022-03-04 10:00:18.564] [] Started process "O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" with Opt: /s\r\n/v"/qn\r\nVDM_VC_MANAGED_AGENT=0\r\nVDM_SERVER_NAME=hint01.konzern.intern\r\nVDM_SERVER_USERNAME=KONZERN\rdsks\r\nVDM_SERVER_PASSWORD=***(confidential)***\r\nREBOOT=ReallySuppress\r\nADDLOCAL=Core,RTAV,HelpDesk,BlastUDP"
[6] [2022-03-04 10:00:18.740] [] ExitCode -1 Executed process ""O:\vmware-horizon-agent-ks\files1\VMware-Horizon-Agent-x86_64-7.13.1-18035779.exe" /s /v"/qn VDM_VC_MANAGED_AGENT=0 VDM_SERVER_NAME=hint01.konzern.intern VDM_SERVER_USERNAME=KONZERN\rdsks VDM_SERVER_PASSWORD=***(confidential)*** REBOOT=ReallySuppress ADDLOCAL=Core,RTAV,HelpDesk,BlastUDP""
[6] [2022-03-04 10:00:18.743] []
[6] [2022-03-04 10:00:18.746] [] ExitWindows set to Reboot
[6] [2022-03-04 10:00:18.748] [] Set $ExitCode$ = getlastexitcode
[6] [2022-03-04 10:00:18.751] [] The value of the variable "$ExitCode$" is now: "-1"


Es scheint so, als ob es startet, aber mit -1 aufhört.