Cool Solutions

ZENworks 7 Support Pack 1



July 18, 2006 8:12 pm






If you are a ZENworks administrator – you have probably seen that we released ZENworks 7 Support Pack 1 in the last few days.

The whole ZENworks team are very proud of this release – it is of high quality, fixes problems reported via Novell Support – and adds some new features to ZENworks 7.

This post will describe how to get ZENworks 7 Support Pack 1 and how to install it. My next post will talk about what’s new in this release – including platform support and software distribution bandwidth management.
This will be a longer post than normal – but there is a lot of useful information that needs to be shared!

Written at: Draper, UT

1 – Where to find ZENworks 7 Support Pack 1

We have made some updates to where ZENworks 7 Support Pack 1 is downloaded – and also how it can be installed.

The Support Pack is available from – you will notice that this is a new set of integrated CD ISO images. The specific link is here:

Documentation for the Support Pack is online at Novell Documentation. The link is here:
There is also a comprehensive Support document – TID 10097368 – describing the Support Pack.

There are FIFTEEN ISO images available for the full ZENworks 7 download. You most likely do not need to download them all. Here is a great document describing what is needed for each components of the ZENworks 7 Suite. This document describes what is on each ISO.

2 – installing ZENworks 7 Support Pack 1

First a note on the Support Pack itself.

You have probably noticed that ZENworks 7 Support Pack 1 is delivered as a new set of product CD images. We have moved away from a non-integrated support pack. The main benefits of this approach are:

  • integrated installation of ZENworks 7 Support Pack 1. Upgrade customers do not need to upgrade to ZENworks 7 then install the Support Pack. You can get the latest and greatest with a single install.
  • interactive upgrade from ZENworks 7 to ZENworks 7 Support Pack 1. You can work through an interactive upgrade, server by server and upgrade components.
  • unattended upgrade using ZENworks Server Management CPKs. These support both the Standalone Package Processor and automated deployment with ZENworks Server Management

There are really three methods of installing the Support Pack – each method really depends on ‘what you have’ and the size of your organisation.

The CPK based upgrade is the most interesting option – it is new with this release. Take a look at the options for installing this with the Standalone Package Processor. For customers using ZENworks Server Management this is another reason to smile – you can now roll out this support pack after hours, with no interaction.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. 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 it thoroughly before using it in a production environment.


  1. By:Paul

    I am disappointed with SP1 for ZENworks Desktop Management when it comes to imaging run off a Windows or NetWare server. Specifically, when one boots into Imaging Maintenance Mode and takes a look at the detected hardware, a new piece of information is presented: “Computer Product Name”. This is a great piece of information.

    Unfortunately, Novell didn’t update the ZENworks Snap-In’s for ConsoleOne so that one could establish an Imaging Server Policy rule based on “Computer Product Name”. In fact, they seem to have made no changes at all to the imaging rules snap-in. In my environment, we have several different hardware platforms by different manufacturers. Being able to take advantage of this information would have been extremely helpful in our imaging environment.

    Here is the disappointment: This new information came about with ZDM 6.5 SP2 and ZDM 7.0. When I asked Novell about it, I was told it would be addressed in ZDM 7.0 SP1. Either I have not been talking to the right people or Novell hasn’t been listening.

  2. Paul,

    One thing we did about a year ago was bring our imaging technologies for ZENworks Linux Management and ZENworks Desktop Management to a common codebase. That’s a sensible thing to do.

    One field we expose only via ZENworks Linux Management today is “Computer Product Name”; we do not – as you have seen – show this for ZENworks Desktop Management.

    The plan is that in the Next Generation ZENworks we bring the management interfaces and architectures together for managing Windows and Linux – and that is where that component will be exposed.

    The enhancement request you mention was investigated for addition to Support Pack 1 – unfortunately the delivery still remains for the Next Generation of ZENworks.

  3. By:Paul


    Why wasn’t the enhancement request included?

    The “Computer Product Name” *is* exposed in ZENworks Desktop Management in the ZENworks Imaging Engine (has been since ZDM 6.5 SP2/ZDM 7.0 as I previously mentioned). It is not, however, exposed in ConsoleOne. I do not understand why this seemingly minor enhancement could not have been included.

    I have been a die-hard fan of Novell and ZENworks since Version 2.0. I have been a die-hard NetWare fan since 3.11. I view this latest incident as an example of where too much emphasis on Linux R&D and too much outsourcing of development engineering on the part of Novell is stalling its ability to maintain and enhance its core products.

    I do hope the next generation of ZENworks Desktop Management will build upon and improve the current product.

  4. Paul

    Some enhancements make the cut; others don’t.

    Generally we don’t add many enhancements to a Support Pack release – we fit those into point releases.

  5. By:Paul

    I just got done with a 10 hour migration from ZDM 7.0 HP3 to ZDM 7.0 SP1. In the end, we had to abandon the migration and revert back to ZDM 7.0 HP3.

    There are serious flaws with ZDM 7.0 SP1 when it comes to imaging services running on clustered systems. Please conduct off-line confidence testing on an isolated network before attempting to migrate a clustered system to ZDM 7.0 SP1.

    We are running a two node cluster on OES NetWare 6.5. We were running ZDM 7.0 HP3 with ONLY the PreBoot Services and Imaging Services. When we went to apply SP1, everything seemed to go smooth. As a part of the installation process, the install will update the local workstation, then the clustered volume, then each node. It was on the node updates that something unusual occured.

    A java-based login dialogue box appeared and wanted eDirectory credentials for the IP address of the node. The problem was that there was no was to enter the information. All of the fields were locked and none of the buttons (OKAY, CANCEL, DETAILS) were clickable. The only thing that would work was to click the X to close to dialogue box down. Then the installation would proceed and the dialogue box would once again appear for the other node.

    When the installation completed, the log files indicated complete success. No error messages at all. However, after rebooting the cluster, the following problems cropped up:

    – Server Policy Package – Imaging Server rules were being interpreted by PXE just fine, however, after booting the linux kernel and at the moment where our Scripted Image Object would be accessed for its bash script, a “no work to do” message would appear and the workstation would reboot.

    – The img “View Hardware Information” would show different information than what we had programmed in our rules. If we attempted to match the information displayed in the “img” application, our rules would no longer function. We learned that we should not attempt to match the information and leave our rules alone.

    We were dead in the water.

    Examing our ZIMGDBG.LOG revealed numerous RAD -603 and RMAD -649 error messages. Network packet traces revealed that the scripted image object was indeed being accessed, but its contents were not being transmitted. No matter what we did (create new server policy package, create new image object, reinstall, reinstall fresh, etc.) we could not get ZDM 7.0 SP1 Imaging to work with PXE and Imaging Rules.

    We worked with Novell engineers who in-turn engaged developers. It was apparent to me that there had not been a whole lot of testing performed of ZENworks Imaging on clustered systems running NetWare.

    My advice to anyone running Imaging on a clustered system should hold off on applying ZDM 7.0 SP1 until Novell fixes all of the defects (and there are many).

    UPDATE: The problem with the login dialogue box was related to DNS. We don’t have DNS running on our isolated network because it isn’t needed. Apparently the installer for ZDM 7.0 SP1 *MUST* have access to either a DNS entry or HOST FILES entry for all nodes on a cluster. If it can’t resolve the name, the bogus login dialogue box appears. Apparently the Novell developer in charge of testing on clusters failed to log a defect for this problem which is why none of the front-line engineers and technical support knew anything of the issue.

  6. I spoke with engineering and support – there seems to be a workaround for this.

    The problem is caused by the install looking for resolvable hostnames for the cluster resources. Make sure you have DNS configured – or use a local HOSTS file.

    I spoke to Paul – and the two node cluster is used as a ZENworks Imaging Vault – so was not part of the corporate DNS infrastructure.

    A defect has been raised, a new test case may be added to the database – also a TID is produced as well.

  7. By:Johnnie Odom

    I’m looking forward to the complete “What’s New” article. I’ve been waiting for the SP to upgrade from 6.5 SP2.


ZENworks 7 Support Pack 1


July 17, 2006 12:14 am





Spent an interesting (and exhausting) weekend starting the process of pulling together the list of fixes for ZENworks 7 Support Pack 1, so we can publish them. For example TID3484245 is the result of working from about 5am to 3pm both days (I know what you’re thinking, why can’t he be more efficient? ). (more…)

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. 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 it thoroughly before using it in a production environment.


  1. By:Grant

    Excellent post. It’s very real world.

    I like the latest and the greatest, but I don’t apply SPs just because. Frequently when I do, something breaks that was working before. If I don’t see a tangible benefit (added features or bugs fixed that affect me) then I will wait.

  2. By:Eric Young

    w00t to sp1!

    Has there been any thought about automating the generation of TID’s from bugzilla? It sounds like it takes a lot of work to manually write up the TID’s.

  3. By:Shaun Pond

    It could be automated, but the problem as I see it is that bug reports in bugzilla are written when we don’t know what the problem is – we know some of the symptoms, but we might not have the underlying issue – imagine we get a problem that says something like “NAL can’t distribute apps that start with the letter A”, and that’s what we report, because that’s what we see in testing, but after the engineers has looked at the code, it turns out that the problem is only if the app name is an even number of characters. We’d want to write the TID to be as specific as possible, which is why they sometimes only get written in arrears…

  4. By:Shaun Pond

    that’s why we need to let you know what the changes are 😉

  5. By:Andrew Miller

    Have you ever looked at Jira for bug tracking?

    I work with some companies that literally make their release notes a wiki page (using Confluence for the wiki….don’t have to though) that pulls info directly out of a Jira (i.e. a list of the fixed bugs between 2.2.5 and 2.2.6).

    Here’s an example.

    For what it’s worth, I’d recommend Confluence over MediaWiki as well. 😉

  6. By:Shaun Pond

    Personally, no 🙂 We’ve just started using Bugzilla, I don’t see that changing soon…