so.. the smart design by Novell as of now is that the clients will
also have to do each step of the update...??
Maaan....I really hope and thought I wouldnt be like that.
Ok for that the sat-servers would maybe have that extra reboot, but
forcing all clients to go through that ???....that's not directly
ZeroEffortNetworking or whatever the idea was......
So,, btw,,thanks for your answer,
status right now then is;
My idea was to update from 10.2.2. to 10.3.0 and then to 10.3.1 during
the weekend so no clients would be affected...,,,
But,, that might not be possible then ?
Meaning I have to get the whole zone to 10.3.0 first,
and then apply 10.3.1 ??
thanks again for your feedback and sorry for the frustration..
On Fri, 06 Aug 2010 17:34:03 GMT, Allan B. Clausen
>I have that same issue.
>It seems that there is no way around it - it will boot 2 times.
>If you try to install the 10.3.1 agent on top of a 10.3.0 agent, it
>will say that it's already installed.
>But I'm pondering something like this:
>1. Use AdminStudio to record the differences of a 10.2.2 to 10.3.1
>2. Push out a script during ZENworks login and run it.
>3. Kill all agent services
>4. Kill all agent processes
>5. Deploy the MSI from step 1
>Maybe that would do the trick?