beaujona Absent Member.
Absent Member.

new images failing during 3rd auto-login

I have had a sysprep system in place to do 3 auto-logins, essentially eliminating the need to intervene during the imaging process. This had been working flawlessly until we moved on to 11.2.3a and still to 11.2.3a MU1

Here are the steps I have running:

1) base image does not contain the ZCM agent; addon image for specific machine types have the .EXE in a subfolder; if I need to update my agent in an image, I just update my addon image with the new .EXE

2) after imaging is done and system reboots, the computer will automatically log into Windows (autologin 1) and "runonce" the ZCM agent from the subdirectory

3) the computer will auto-reboot after approximately 10mins and then auto-login and do its ZENworks thing (i.e. the window that appears in the top left; looking for ISD or creating it, configuring it, etc). Once this is completed, the computer reboots

4) the computer then auto-login (3rd time) but sits at the ZCM agent splash screen. Before 11.2.3a, if you left it there, it would eventually time out and just log into the machine and run my Novell Client Install bundle for the workstation location. Since 11.2.3a, after about 2mins of sitting at the ZCM login prompt, Windows shows up a "force shutdown" popup which then reboots the computer and never installs the Novell client, which then forces me to log in workstation only with my admin account and ZCM runs the novell client bundle

If I happen to "cancel" the ZCM login prompt and avoid the shutdown command, during the novell client install I will see a message popup telling me that ZENworks made some adjustments and will need to reboot

How can I avoid the agent from rebooting the computer while sitting at the ZCM agent login prompt? This is crucial to our deployment method and previous to 11.2.3a it worked without a hitch. What is going on in the background and what can I do to avoid it?

I was looking at the system update configuration tab, but I'm unsure if this will help me since the agent is installed from scratch (not run through the system update)

Anyone else run into this issue, or similar?


p.s. we upgraded to 11.2.3a MU1 in the hopes that it would help, but it's still an issue
Labels (2)
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: new images failing during 3rd auto-login


It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team

gshaw0 Absent Member.
Absent Member.

Re: new images failing during 3rd auto-login

I do mine in a different order:

Image > sysprep > drivers (DPInst) > Novell Client > ZCM Agent so that's your easiest fix. We don't use the ISD feature as I do other things with the naming process and it would cause more harm than good if left enabled.

ZCM 2017 U2 on VMware| SQL 2016 database | 4 primary servers over 3 sites | 3000+ Windows 10 images to deploy via MDT :cool: Check out my blog - ZCM imaging and other tech stuff
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.