Cool Solutions

ZCM Imaging – Installing the ZEN Adaptive Agent in the image


January 21, 2008 2:39 am

Reads: 34872



Download imagescripts

Creating the Image

Instructions for preparing the PC for creating a ZEN Image.

  • Boot up PC.
  • Remove Zen Adaptive agent & reboot – tell it to remove machine from zone.
  • Download full Zen agent to local disk
  • Disconnect NIC
  • Run the Agent, but DON’T reboot at end.
  • Browse to HKLM\Software\Novell\Zenworks\PreAgent and delete the GUID entry
  • Browse to HKLM\Software\Novell\Zenworks\Remote Management\Agent and delete any subkeys with machine names on them.
  • Browse to HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\System and remove the entry pointing at ziswin.exe (Leave the System key in place)
  • Run C:\Program Files\Novell\Zenworks\Bin\Preboot\ziswin
  • Click Edit, clear imagesafe data, and save – Click No to the question about “just imaged” if asked
  • Run sysprep -mini -quiet -reseal – this will prep the machine and switch it off.
  • Cut image.


SYSPREP is set to auto login as the last used user-id (which should be the admin account you used to run SYSPREP) twice – The script files modify the registry to run certain commands in sequence.

The attached ZIP file contains some scripts which need modifying as follows:

Edit the sysprep.inf and enter the following details where relevant:



Under the Compaq Folder, edit the install2.cmd as follows:


SYSPREP – 1st Reboot.

On 1st reboot, the script C:\COMPAQ\install.cmd is executed. This runs a HP/Compaq utility to obtain the BIOS information to assist in renaming the machine based on the BIOS Asset Tag. Obviously if you use any machines other than HP/Compaq, you’ll need to replace this with an equivalent utility.

This then calls the script which sets the Windows Machine name to the BIOS Asset Tag.

The registry is then updated to call install2.cmd at next reboot, and the machine is then rebooted.

SYSPREP – 2nd Reboot.

The 2nd Reboot again updates the registry, this time to put the ZISWIN call back into the system so that its called each time the machine is booted.

The PC is then added to the domain, and a couple of Local Groups are updated (feel free to update as required for your own purposes), and then the PC is rebooted for the final time.

Hope this helps.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. 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:trepanga

    use sysprep -bmsd command BEFORE using sysprep -mini -quiet -reseal.

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  2. By:havoc64

    Why wasn’t the autoimport “register” feature put into ZCM? Is it something planned for a later date in ZCM?

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  3. By:thtran

    If you do it like that, please don’t forget to delete the file “install2.cmd”, as it contains the PASSWORD FOR DOMAIN ADMIN ACCOUNT in plain text!

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  4. By:ipst13

    For my part, I have an add-on image that I can modify to update the current agent so, when a new system-update is launched in production, I just update my add-on image and any new workstation beiing imaged gets the latest agent.

    Installation of the agent is automated within a script after the 2nd reboot.

    No need to rebuild the whole image and do all the testing and drinking to much coffee!

    my two cents!

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
    • By:jimdavis66

      Hi, this is how I have been trying to do mine except it won’t install properly unless I log in to Windows as a user.

      In my sysprep.inf file I have:


      Which is calling this script to install the Novell Client and the Zenagent:

      REM install novell client
      start "novell" /wait "%systemdrive%\temp\491sp5\acu.exe" /U /D:no

      REM install zenworks client
      start "zenworks" /wait "%systemdrive%\temp\PreAgentPkg_AgentComplete.exe" -q -x

      The script runs after the sysprep mini and the Novell client installs but the zenagent doesn’t complete. I even tried making the install.bat pause for 10 minutes just incase it was still waiting but that didn’t fix it. Have I got the wrong syntax? How are you doing it?

      Thanks :)

      VN:F [1.9.22_1171]
      Rating: 0.0/5 (0 votes cast)
  5. By:cougmanjvh

    These steps are right on, but i think we need to specify that you CAN NOT reboot whatsoever after you install the agent. What i do is make this my last step in my base image setup, not plugged into network at all, just manually install client, and do all of these steps then. Then i do mini-setup, reseal, shutdown and plug into network and make base image. OVERALL, EXCELLENT STEPS..THANK YOU

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  6. By:MIke_Berlin

    downloaded the, unpacked them with 7zip and tried opening the
    resulting file with an editor. Only ununderstandable code is shown. Is this done
    with a particular compiler that is not mentioned above.


    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
    • By:thtran

      I just downloaded and unpacked it with Total Commander. I got 2 folders (compaq and sysprep) with one perl file, some bat files and some exe files.
      Looks o.k. to me.

      VN:F [1.9.22_1171]
      Rating: 0.0/5 (0 votes cast)
  7. By:dschaldenovell

    Hello I was trying to use your steps to prepare an image for Windows 7 however came across the following issues:

    These two registry keys don’t exist:

    Browse to HKLM\Software\Novell\Zenworks\Remote Management\Agent and delete any subkeys with machine names on them.
    Browse to HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\System and remove the entry pointing at ziswin.exe (Leave the System key in place)

    I have just ignored them, but wanted to know what if anything in the registry needed changing?

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
  8. By:dschaldenovell

    I’m starting to use 64 bit as my image platform, are there any plans to update this cool solution to reflect the needs for the 64 bit platform?

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)