Deploy Winzip pro V20
Hi there,
I am having issue with deploy Winzip pro v20. I created a managed install
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
1 Comment
[ + ] Show comment
-
Thanks guys. I got around it by created a script install. But tested adding msiexec.exe /i in and it worked. - yzhang 7 years ago
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
anonymous_9363
7 years ago
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?!?
Posted by:
rockhead44
7 years ago
Top Answer
As VBScab says, you'll need to have msiexec run. Try this at the beginning of your command line:
msiexec.exe /i
Posted by:
anonymous_9363
7 years ago
...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.
