By Martin Buckley
One of the most important new features of ZENworks 10 Configuration Management is the System Updates feature. This allows administrators to automatically download, approve and deploy ZENworks patches and updates across their servers and workstations.
First things first - make sure your primary servers have enough disk space. We recommend 5GB of free space in the location where you installed ZENworks Configuration Management.
You can find System Updates under the Configuration Tab. You can review available updates; and then select Download Update:
The download will start; depending on the size of the update (this one is 800MB in size!) it could take some time to download.
One completed the download will be bundled (or inserted into the ZCM content system) and then syncronised with the other Primary Servers:
The next step is to release this update into your ZENworks Configuration Management Zone.
It is recommended that you use System Update Staging Groups to carefully deploy to test servers and test workstations before deployment to live servers. You should always make sure you have good Change Management and Release Management in place before doing any update.
Here are some System Update Staging Groups:
To release the update it first needs to be Authorised. Click on Status Details under System Update Overview; then select the System Update and make it Authorised.
Next step - allow the update to be deployed. You can make this automatic, going through each Stage automatically; update all machines immediately or to manually step through.
You should see the Update Status change:
It's that simple.
There's a lot more you can do with System Updates - including building in notification of updates being available, notification of success or failure between stages and showing the status.
I hope this gives some insight into the new methods of update we are delivering with ZENworks Configuration Management. Our aim is to make your systems easy to manage - and use ZENworks to update and patch itself.
As always - comments welcome.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.