During the current client upgrade process, the user can not operate fully on. (There can be no call bundles and usually a reboot is required.) In addition, the update process for administrators is temporally not taxable.
Symantec enables with its current client installation routine, the parallel installation of the new client version. (The new client is installed in a directory other than the old client.) The existing client does not have to be removed beforehand. The existing client is until the next reboot fully functional! Only after the restart, the system works with the new client. A necessary restart can be postponed indefinitely.
Users can continue to work without restrictions during the upgrade process. The update process would be for administrators manageable and more flexible.

It would also be highly desirable if the administrators could control the destination of the client update time.

IN GERMAN:
Bequemes ZCM Client-Update: Tausch der Client-Version mit ununterbrochener Funktionalität

Während des gegenwärtigen Client-Aktualisierungsvorgangs kann der Benutzer nicht in vollem Umfang weiter arbeiten. (Es lassen sich keine Bundles aufrufen und in der Regel ist ein Neustart zwingend erforderlich.) Außerdem ist der Update-Prozess für Administratoren zeitlich nicht steuerbar.
Symantec ermöglicht mit seiner aktuellen Client-Installationsroutine die parallele Installation der neuen Client-Version. (Der neue Client wird in einem anderen Verzeichnis als der alte Client installiert.) Der vorhandenen Client muss nicht vorher entfernt werden. Der bestehende Client ist bis zum nächsten Neustart voll funktionsfähig! Erst nach dem Neustart arbeitet das System mit dem neuen Client. Ein notwendiger Neustart kann auf unbestimmte Zeit verschoben werden.
Die Benutzer können ohne Einschränkungen während des Aktualisierungsprozesses weiter arbeiten. Der Update-Prozess wäre für Administratoren überschaubarer und flexibler.

Sehr wünschenswert wäre es auch, wenn die Administratoren den Zielpunkt des Clientupdates zeitlich steuern könnten.

by: Testus N. | over a year ago | System Update

Comments

• I like your idea better. Someone posted a variation here: https://www1.v1ideas.com/MFI/novell-zcm/Idea/Detail/1211

  by: Jasen W. | over a year ago

• While I love the idea of having a fully operating client at upgrade time, this probably is a lot of work to implement. Sure the ZCM team has played with that idea but decided at the time not to do that. So, as a trade off to 'not having it all' my idea at https://www1.v1ideas.com/MFI/novell-zcm/Idea/Detail/1211 was to have a acceptable solution which is relatively easy to implement using the current code base.

  by: Sebastiaan V. | over a year ago

• Thanks for the comment and the effort

  by: Testus N. | over a year ago

• Zen for desktops 4 had an option to make an icon available offline. Would be nice to add that back into 11 and use while the agent upgrade is taking place. We prohibit our users from accessing the regular start menu and creating .lnk files on their desktop.
  
  We try to schedule our agent upgrades for after hours. Otherwise our users keep rebooting the computer during the upgrade. They just don't understand why they can't launch their icons. This is with us sending out notices ahead of time. So finding a way to make the upgrade process seamless for the end user would be ideal.

  by: Jasen W. | over a year ago

• Another proposed agent upgrade idea. https://ideas.microfocus.com/MFI/novell-zcm/Idea/Detail/1173

  by: Jasen W. | over a year ago