First of all, we don’t have experiences with the new ZEUS introduced in 11.4 because, as we asked in the 11.4 update webinar, it first comes to place for the update from 11.4(.0) to 11.4.* .
But we although asked in webinar if ZEUS will check for MSI service before the msi installation of the different zcm agent parts is started. We understood that ZEUS wont do this, therefore the behavior is like in prior versions of zcm and if a third-party software like anti-virus or other third-party tools will start their own triggered updates on a msi basis, then this will lead to corrupt installation of the zcm agent.
Therefore we wish that ZEUS either asks msi service if its unused and if not, starts with zcm component installation after the service gets available (or it try several times until it installation is successful).
by: S. M. | over a year ago | Install
Comments
I would say the whole point of ZEUS was to provide a hardened upgrade process fixing -any- upgrade issues for the user without breaking itself.
Concurrent (e.g. Windows updates) msi installations still 'break' the agent installation, resulting
* in the best case - a partially upgraded system which can be repaired 'easily' by a manual reinstallation
* in the worst case - a 'dead' system that is a real support nightmare.
We need an 'atomic' msi installation/transaction setup procedure that is immune to concurrent msi installations.