ENGL Support

Issue

ENGL Imaging Toolkit configures AutoAdminLogon to automate the build process. If pre-requisites have not been met or certain policies have been applied logins may fail and the build process cannot complete automatically.

This document provides some basic steps to help you troubleshoot AutoAdminLogon.

Solutions

"Tree or Server Not Found"

Make sure you are using a recent version of the client: for Windows 10 1607 ("Anniversary") edition or later, it is required that "Client for Open Enterprise Server 2 SP4 (IR5)" or later is used.

When using the Novell client it is vital that SLP is configured correctly in order for AutoAdminLogon to complete. If you can log in manually after waiting for 30 seconds then SLP is the issue.

1. If you can manually log in as the installer user, then:
   
   

• Configure Scoped SLP and deliver the DA and Scope using either the client configuration or DHCP options 78 and 79. (See Novell TID 10014467 and 7002120 for details on how to configure scoped/named SLP)
  
  
• It has also been reported that it may also be necessary to remove all Name Service options other than SLP and NCP
  
  
• If using environment variables in to determine login details, ensure that these variables have been defined in the previous phase. The ztoolkit.log file will show what information was set when the DebugLevel is set to 3.
  
  
• If you are unable to login check that you can ping the tree / server and that the network card drivers are installed.
• The following registry change may also work, as it allows the number of login retries to be increased thus allowing time for the Network stack to configure itself. This would be added to a phase1-after.reg file.
  

  REGEDIT4
  
  ;
  ; Wait Novell Client network stack to load
  ;
  [HKEY_LOCAL_MACHINE\Software\Novell\Login]
  "Max Retries Boot Threshold"=dword:00000078
  
  

   This registry change is supported with the Novell Client 2 SP1 for Windows (IR6) or newer. More information can be found in the following
  Novell TID: http://www.novell.com/support/kb/doc.php?id=7006626 

Return

"The user could not be located in the specified context"

1. Check that the user exists in the context specified
   
   
2. Check that LDAP contextless login has been disabled as per the pre-requisites. It can be re-enabled using a phase4-after.reg file containing the following:
   
   

   REGEDIT4
   
   ;
   ; Enable LDAP Contextless login
   ;
   [HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Graphical Login\NWLGE\LDAP Contextless]
   "Contextless Login Enabled"=dword:00000001

3. Check that you can log in manually using the user and password credentials you specified in the zmainrun.xml
   
   
4. Check that the context listed in the Novell Client is correct
   
   
5. If you are unable to log in or browse contexts from the client try using an IP address instead of the Tree Name. If this works you may have SLP problems.
   
   
6. If you wait 15 seconds and can then log in you may have client issues and need to apply the latest patches or SLP problems.
   
   

Return

"No domain controller could be found for the specified domain"

If you receive a message that no domain controller could be found check that the computer name matches that which you gave it during phase1. If it does not check that the machine does not have a different ZISD identity.

• Check that the Windows Computer Name matches the one you specified in phase one. If it doesn't, check ZISD.
   If you are renaming a workstation you must clear ZISD first or this information will be restored and the computer names will not match.

Return

Acceptable Use Policy requires OK

Delivering an Acceptable Use Policy via Group Policy causes AutoAdminLogon to fail as it still requires OK to be clicked.

 This can be overcome by either removing the Acceptable Use Policy and using a phase4-after.reg file to deliver it or by altering the device's group membership or location using a phase4-after.vbs file so that the Group Policy does not apply during the build process.

Return

ZENworks login dialog appears

A ZENworks login dialog generally suggests that the currently logged in user has not been found in the ZENworks user source and there may be several reasons for this.

• If using an eDirectory user source:
  
  
  • More than one user with the same name exists and the password is different
    
    Solution: Use a unique account name
    
    
  • The Novell Client has been configured with additional options than those listed in the pre-requisites and has failed to log in
    
    Solution: Check that Initial Novell Login is enabled and LDAP Contextless Login is disabled. Try the build using only the pre-requisite settings in the acu/ncpf.txt file.
    
    
• If using an Active Directory user source:
  
  
  • Attempting to use the Administrator account may confuse ZENworks as it has its own internal Administrator account
    
    Solution: Use an alternate account with rights to add machines to the domain
    
    
• If using multiple user sources:
  
  
  • ZENworks is unable to determine which user source to authenticate the user against.
    
    Solution: Ensure that the installer user contains the correct User Source name, e.g., installer@mytree
    
    

Novell/OES login appears, but no error

• Check that the password for the local Administrator, stored in the project, matches the password used when the base image was created
• Check that the setting "Prompt for Novell login during Windows AutoAdminLogon" in Advanced Login in nciman is set to off

Return