I'm testing a deployment of WinZip 14 to a group of about 70-80 users who currently use WinZip 12. The scenario we want to follow is the same as I used for an earlier deployment of WinZip 11, which was to set up a Task Sequence in SCCM so users had a window of time to perform the install themselves before it became mandatory. We did this because we're rebooting the PC after WinZip installs, and many users stay logged in when they're not in the office, so we want to avoid causing them to lose any of their work in progress.

As a side note, sending email or notifying the users in advance of us doing the SCCM deploy isn't a great option, as we don't necessarily know the names of all the users on these PCs (PCs at multiple sites, multiple users on some PCs).

So on to my issue: I built an EXE to uninstall WinZip 12 using Wise Packaging Studio. When I run the EXE locally on a PC, it works fine. But when I run it in the Task Sequence as part of the SCCM deployment, the uninstall throws up a dialog that says "msiexec.exe has encountered a problem and needs to close".

I tried writing to a verbose log during the uninstall, but don't see anything of note in there (although I'm not exactly sure what to look for).

Any suggestions for what I can do to help identify the cause of the error dialog?
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


I've been thinking about this one since I spotted it last night and, reading it again this morning, I don't think you have any option but to target one of your test VMs/VPCs/VirtualBoxes and fire up ProcMon and have it monitor MSIExec and wait for the task to begin. Tedious in extremis, I know, but I can't think of any other way you can diagnose the problem.
Answered 05/07/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity