Auto Login to ZENworks Adaptive Agent Using a Pre-Configured Response File or ZAC Command Interface

Auto Login to ZENworks Adaptive Agent Using a Pre-Configured Response File or ZAC Command Interface

The following methods will help users to auto login to ZENworks Adaptive Agent using a pre-configured response file or by using the command line interface on a managed device. These methods are useful in scenarios where users want to first perform Active Directory Login from their workstations and then perform an auto login to the configured user source (Example: eDir login) where the user's credentials are not in sync with Active Directory.

Method 1: Auto login using a response file on the managed device

    1. Create the response file with the following parameters:



                 2 .Save the response file to a particular location on the managed device.

                    Example:  D:\AutoLogin\auto.txt.

                  3.On the managed device, in the HKLM\\SOFTWARE\\Novell\\ZCM\\ZenLgn location, create

                      the following registry entries:

Registry Key Type Value
UseResponseFile DWORD 1
ResponseFileName REG_SZ {Path to the response file}

Method 2: Install the Novell ZENworks Automation hooks and login using the ZAC command line interface

  1. Stop the ZENworks Agent Service.
  2. Install the novell-zenworks-automation-hooks MSI:
    (a) Download the msi from the Primary Servers. For example, if you are using a ZENworks 17.3 server, open a web browser and navigate to https://{Server-IP}/zenworks-downloads/msi/novell-zenworks-automation-hooks-  

 b) Place the AutomationHooks.dll in the correct target directory. For example, if the zenagent is installed in the C:\Program Files(x86) directory, then running the following command will place the AutomationHooks.dll in the correct target directory:                                                                                   msiexec.exe /i ${Path_To_AutomationHooks.msi} /qn TARGETDIR="C:\Program Files(x86)" ALLUSERS=2 REBOOT=ReallySuppress

3.Start the ZENworks Agent Service.

4.In the command prompt, run the zac command to identify if the zen-login command is listed amongst the other zac commands.

5.Run the zac zen-login command to log into the ZENworks server. The details of this command are as follows:
Command: zen-login, login

Syntax: zac zen-login /user:<UserName> /pwd:<Password> /realm:<Realm>

Example: zac zen-login /user:admin /pwd:novell /realm:EDIR

Labels (1)


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Thx, that looks exactly like what we need descibed inour IDEA "Ability to login to the ZCMagent command line"
I only find a recent novell-zenworks-automation-hooks on a ZCM appliance, on any Windows Primary Server I look this zenworks-downloads/msi/novell-zenworks-automation-hooks file is ZCM 11 while the primary already is 2017.
Although the msi version doesn't match with ZCM version, the functionality of auto-login exists and it should work with ZCM 11 as well.
First of all thank you very much for that wonderful cool-solutions-articel!

I tested Method 1) and it worked like a charm, but please edit the part 1 of Method 1) to be more specific how the Response-File should look like.

What i found out during my try-and-error-session:
- don' use any empty spaces
- don't use the { }

Example Response-File:

Again, thank you very much for sharing this Hint!
Thank you very much for your feedback and comment.Method 1 will be edited as per your comments.

Where would I be able to find the automation hooks msi on my Zenworks2017 primary server?

I have tried method in a SCCM CB Task sequence and it doesnt seem to pick the associated bundles for the user specified in the response file?

Top Contributors
Version history
Revision #:
2 of 2
Last update:
‎2019-05-05 09:10
Updated by:
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.