/build/static/layout/Breadcrumb_cap_w.png

Software Question


Deploy Winzip pro V20

06/26/2016 1507 views
Hi there,

I am having issue with deploy Winzip pro v20. I created a managed install
EMfNOd.png 

The msi file gets downloaded on machine c drive C:\ProgramData\Dell\KACE\downloads. But it doesn't install. Here is the log

[2016-06-27.10:46:58][runkbot:UploadUsingCurl         ] UploadFile:  Server gzip compression cleanup.
[2016-06-27.10:46:58][runkbot:CleanupLog              ] Cleaning up log file [C:\Windows\TEMP\dkl14E.tmp]

[2016-06-27.10:47:13][AMPAgent:ClientReadCB           ] Header: msgid (103514657); msgType (0)
[2016-06-27.10:47:13][AMPAgent:ClientReadCB           ] Payload: pluginId: RunProcess (6); payloadLen (37)
[2016-06-27.10:47:13][pluginRunProcess:GetIdOfActiveUs] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(18) There are no more files.


[2016-06-27.10:47:13][runkbot:GetKbot                 ] Kbot [6-1400808518] not found locally, downloading ...
[2016-06-27.10:47:13][runkbot:GetIdOfActiveUser       ] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(18) There are no more files.


[2016-06-27.10:47:13][KDeploy:GetIdOfActiveUser       ] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(18) There are no more files.


[2016-06-27.10:47:21][KDeploy:GetIdOfActiveUser       ] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 9(18) There are no more files.


[2016-06-27.10:47:22][KDeploy:KLaunchClientImpl::Launc] KLaunchClientImpl::LaunchInSession - Error: CreateProcessAsUser Failed: 
[2016-06-27.10:47:22][KDeploy:CMIPackageMgr::LaunchPro] KDeploy    LaunchProcess: ERROR returned by KLaunch (193).
[2016-06-27.10:47:22][KDeploy:CMIPackageMgr::InstallSw] KDeploy    Managed Install FAILED (WINZIP200-64.MSI)
[2016-06-27.11:20:07][AMPAgent:ClientReadCB           ] Header: msgid (103516996); msgType (0)
[2016-06-27.11:20:07][AMPAgent:ClientReadCB           ] Payload: pluginId: RunProcess (6); payloadLen (31)
[2016-06-27.11:20:07][pluginRunProcess:GetIdOfActiveUs] GetIdOfActiveUser: SECURITY_LOGON_TYPE: 2(18) There are no more files.

What did I do wrong?

Thanks for your help.

Yan
Answer Summary:
1 Comment   [ + ] Show comment

Comments

  • Thanks guys. I got around it by created a script install. But tested adding msiexec.exe /i in and it worked.

Answer Chosen by the Author

1
As VBScab says, you'll need to have msiexec run. Try this at the beginning of your command line:

msiexec.exe /i  
Answered 06/27/2016 by: rockhead44
Red Belt

All Answers

1

I know nothing about Kace but I imagine that the fault lies in the check-box "Don't prepend MSIEXEC.EXE".

How will the workstation execute an MSI without running it against MSIEXEC.EXE?!?

Answered 06/27/2016 by: VBScab
Red Belt

1
...and for pity's sake, add logging to your installation command lines. If anything goes wrong, you'll have no clue what failed without a log.
Answered 06/27/2016 by: VBScab
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ