Whilst modelling an 11.3 -> 11.3.1 system update in our test environment we received
>>
Unable to complete your request for the following reason: The ZENworks Server and the ZENworks Loader Services are running on one or more Primary Servers. Shut down the services before proceeding.
<<
Following info in https://www.novell.com/documentation...a/bvcumla.html
it suggests:
>>
Action: Do the following:
  • Stop the ZENworks Monitor, ZENworks Server, and the ZENworks Loader services on all other Primary Servers.
  • Start the ZENworks Monitor, ZENworks Server, and the ZENworks Loader services on the dedicated system update server.
  • Assign the update from the dedicated system update server.

<<

This turned out to be the only way to assign the update to the first primary...

Really?!? Are we supposed to effectively keep zcm unavailable for the duration?!? I've not seen this is any internally managed system updates before... we usually get Service Desk, etc. to use alternate Primaries as we roll the update through...
This will significantly increase our upgrade window as we move from 11.2.4-> 11.3a -> 11.3.1

Please let me know your experiences

Cheers
David