Installing Zenworks 6.5sp2 as an Unsecure System User renders an incomplete install on some registered workstations
Posted on 2006-04-03
This is a bit complicated because this problem falls between an *.msi file and Zenworks 3.2 delivery.
We are currently deploying Zenworks 6.5 sp2 to the environment via a NAL object as an Unsecure System User.
Workstations that are registered have been receiving the application object.
The application object is actually running a *.vbs script that points to the ZFDagent.msi with the following switches:
strPath = "\\cluster\volume\aotfiles\zenagent"
strCommand1 = "msiexec /qb! /liweu+ \\cluster\volume\logs\zenlog.txt /i " & strPath & "\ZfDAgent.msi ADDLOCAL=ALL NAL_SINGLE_TREE=1 ZENWORKS_TREE=Our Tree REINSTALL=ALL REINSTALLMODE=vamus REBOOT=ReallySuppress"
This is fine. The msiexec /qb! /liweu+ switches were added to point a log file because Zenworks recorded a successful install (which I know can read as a false-positive since its really recording that the *.vbs file was successfully run), but the workstations were not registering.
Upon further investigation we found the following 1705 errors for these users:
"User SYSTEM has previously initiated an installation for product ZENworks Desktop Management Agent. That user will need to run that installation again before using that product. Your current installation will now continue.
Error 1705.A previous installation for this product is in progress. You must undo the changes made by that installation to continue. Do you want to undo those changes?
MSI (s) (F8:10): Product: ZENworks Desktop Management Agent -- Error 1705.A previous installation for this product is in progress. You must undo the changes made by that installation to continue. Do you want to undo those changes?"
I believe some users may stop the install because it may take too long and they'd rather not install it at that time (they maybe going to their task manager and killing the msiexec.exe process)
Notice how it prompts the user at the end: "...do you want to undo those changes"?
Do we manually have to go to each workstation and uninstall this partial install?
Out of 3000 users, we have this issue with about 10%
Has anyone see this issue?
Any feedback would be helpful.