Thanks for the info. In our case this issue is specific to the first reboot after the 11.3 agent upgrade. Works fine the rest of the time, and never had this problem with previous agent updates.
Novell are playing their "it's meant to work like this now" card, which basically means that they haven't a clue. It clearly isn't working as designed, unless it was designed badly. I'm a long-time Novell supporter, so I remember when Novell products were reliable. Sadly, in the case of ZENworks at least, those days are long gone.
I do appreciate you taking the time to reply though.