How to Troubleshoot WinPE hanging after selecting an OSD script from the Boot Menu.

Description

This issue is characterized by selecting an OSD script from within the PXE Boot Menu inside WinPE, the Boot Menu window disappearing, and then no further pop ups or display windows occurring.

There are several causes for this behavior, and therefore, several possible solutions. This troubleshooting guide is centered around the issue of the OSD script failing to be initiated on the core server, or the OSD logs indicating that the machine is "OFF". If the OSD script indicates that it is launching at least one EXEC line against the target, then this troubleshooting guide can be skipped.

Possible Causes:

• Duplicate devices names in the database. 
  (Suggestion is to create a query based on target mac address and delete all instances that already exist in inventory)
• Miniscans being turned off for Inventory.
  (Under Configure Services > Inventory -> Advanced Settings the value for Ignore Mini Scans should be set to 0).
  

  If "Ignore Mini Scans" is set to 1", NO miniscans from the OSD client will be processed!   This must be set to 0.

• Core Server missing files in the \Program Files (x86)\LANDesk\Shared Files folder.
• Missing LANDesk Management Agent.
• No Inventory Record for target client (MAC address or full inventory record should exist)
• Certificate in boot image does not match certificate on core or certificate is damaged or missing.

A visual representation of this process is attached as a flowchart below:

Step 1 - Identifying the Issue

To determine the troubleshooting path, it must first be determined how far the process is progressing. The fastest way to accomplish this is to determine if a CustJob log is being created. Follow the steps below to determine this:

1. On the core server, go to the log directory. This is located at the following path <Install Drive>:\Program Files (x86)\LANDESK\ManagementSuite\logs or can also be accessed via UNC share at <coreservername>\ldlog.

2. Once in the log directory, it is recommended to sort by Date Modified, with most recent at the top.

3. The log file will be named CJ-OSD-<scriptname>-<timestamp>.log

4. If there is a log file, open it with a text editor, such as Notepad or Word.

5. If the log file is similar to the one listed below, and indicates that the machine is OFF, then CBA is unable to contact the specified machine or CustJob has targeted an incorrect machine record.

"Machine","CbaStatus","ExitCode","Duration","Begin","End","Command"

"(OFF) XPSP2B","OFF","N/A","0:00:00","11/6/2008 12:19:28 PM","11/6/2008 12:19:28 PM","N/A"
; "Job Complete","0 Done","0 Failed","1 Off","0 Unknown"

 

If there is no log, then the process did not complete to the point of initiating CustJob to launch the OSD script. See below for actions.

First, verify that the following service are installed and running on the core server:

LANDESK Inventory Server

LANDESK Management Agent

If these services are running, it may be beneficial to restart these services. If the LANDESK Management Agent service is missing, go to the "No logging generated on the core" section below. Once restarted, reboot the machine into WinPE and select the script from the menu.  If the same behavior occurs, follow the indicated directions:

If there was no log file generated in the log directory on the core, go to the "No logging generated on the core" section below.

If there was a log and it indicated that the machine was OFF, go to the "Machine shows OFF" section below.

No logging generated on the core.

The process to request a script to run on the client machine involves a series of processes to request, resolve and schedule the task from the client to the core server. The below steps will attempt to identify and resolve the issue related to these processes.

Missing LANDESK Management Agent service

If the core does not have a LANDESK Management Agent service, you can install this service by following the steps listed below:

1. On the core, pull up the Start > Run window

2. In the field, type or paste the following command and then hit enter:

"C:\Program Files (x86)\LANDESK\Shared Files\residentagent.exe" /register

Once the service is installed, start the service and then try the OSD process again.

If there is not a C:\Program Files (x86)\LANDESK\Shared Files folder on the core server, please contact LANDESK Technical Support for further assistance.

If the LANDESK Management Agent service is installed and running and a service restart did not resolve the issue, please follow these additional troubleshooting steps:

Verifying the Inventory Record

OSD needs an inventory of the device being imaged in order to create the task and begin logging.  New machines that have not been inventoried before will be listed by its MAC address in the Device Name column in the console.

If there is no inventory record for that device, restart the inventory service and reboot the client and try imaging again.  If still no inventory record appears for the device please contact LANDESK Technical Support for further assistance.

Verifying the PXE.amsx Web Service functionality

• Open the CoreWebServices.dll.log located in the log directory on the core server. The log should contain lines that are similar to those listed below:

RunScript: started with client mac address 000C29461DD1, script GUID bc6a8a9c-3edc-4845-83fb-5e1cceb60b71
RunScript: completed successfully with client mac address 000C29461DD1, script GUID bc6a8a9c-3edc-4845-83fb-5e1cceb60b71

Note: Each script has an associated GUID.  The GUID is contained in the Script (Located in the ManagementSuite\Scripts directory).   This must match in the PXEMENU table in the database in order for the script to be associated properly.

Line in Script: GUID=71e307da-bb27-46ab-ac8d-ef9641f3139f

Entry in Database:

• Can the LANDESK PXE.asmx web page be accessed? (Note: This must be run locally on the Core Server

• Open a web browser on the core and type/paste the following address:

http://localhost/LANDESK/ManagementSuite/Core/core.webservices/PXE.asmx

This should display the web page shown below:

• Will the GetObjIDFromMacAddress function resolve a Mac address to a Computer_Idn from the PXE.asmx web page?
  (Note: This must be run locally from the Core Server)

1. Click on the GetObjIDFromMACAddress link in the web site.

2. On the MAC Address field, enter in the mac with no spaces or dashes.

3. Click on the "Invoke" button to process.

4. The following return should be displayed:

NOTE: The number encased by > < is the object ID and corresponds to the machine's ID assigned by Inventory.

If this process fails, then there is most likely a missing record. Ensure that the Inventory contains the MAC address associated with a machine record.

Will the RunScript function start the job by manually putting in the MAC Address and ScriptGUID?
(Note: This must be run locally from the Core Server)

1. Click on the RunScript link in the website.

2. On the indicated fields, input the MAC Address and the script GUID.

3. Hit the Invoke button.

A CustJob window should launch on the core and start processing the script. You can also look to see if this process generates a log file in the log directory. If this process succeeds, then it indicates that IIS may be hung or not correctly processing SOAP requests.
Try running an "IISreset" command from Start > Run. You may also need to re-register ASP.NET on the core with the following command:

"C:\Windows\Microsoft.NET\Framwork\v4.0.30319\aspnet_regiis.exe -i"

• Enable OSD Web Tracing by doing the following:

1. Edit the web.config file in C:\Program Files (x86)\LANDESK\LANDESK\ManagementSuite\LANDESK\ManagementSuite\Core\Core.WebServices so that the line "<trace enabled="false"" reads "<trace enabled="true"" and restart the World Wide Web Publishing Service service.  (iisreset -restart also works)

2. The following URL may be used to pull up the Web Trace to track what requests are made to the OSD Web service on the core: (Note: This must be run on the LANDESK Core Server)

http://localhost/LANDESK/ManagementSuite/Core/core.webservices/trace.axd

• An http caching appliance will respond to the http requests made by the client. Due to the caching appliance responding, the client will not receive the subsequent lines of the script. Configure the caching appliance to not cache the http traffic from the Core Server.

Verifying the LANDESK Management Agent Service functionality.

• Run script calls a local execute on the Core Server. The LANDESK Management Agent service must be running on the Core Server.

• To test the Management Agent service, run the following command line:

"C:\Program Files (x86)\LANDESK\Managementsuite\custjoblaunch.exe"

/objid=<object id of machine> /script="<script name without directory path>" /bootonly

For Example:

"C:\Program Files (x86)\LANDESK\Managementsuite\custjoblaunch.exe" 83 "DeployGhostImage.ini" /bootonly

If this does not launch the script, remove and re-install the LANDESK Management Agent service with the following commands:

Remove:

"C:\Program Files (x86)\LANDESK\Shared Files\residentagent.exe" /unregister

Install:

"C:\Program Files (x86)\LANDESK\Shared Files\residentagent.exe" /register

If these steps do not resolve the issue, please contact LANDESK Technical Support for further assistance.

Machine shows "OFF"

NOTE: When troubleshooting Inventory related issues, please ensure that you are logged in to the core console with a user that does not have any restricted scopes applied and that is allowed to view the Default All Machines scope.

Causes

1. Another machine in the database has the IP address assigned to the machine in WinPE.  Custjob.exe is targeting that device.

2. The inventory scan had not yet processed the ip address from the miniscan. This could be because the inventory service is stopped or hung.

3. Duplicate devices (two machines with the same MAC Address) in the database.

4. Core cannot contact the Agent on UDP port 9595 or port 38293. (Firewall, or other filtering device is blocking this port.)

5. Under Configure | Services | Custom Jobs, the Discovery setting may be set to TCP only.  WinPE only responds to UDP.

6. DNS can be in a state where the client can resolve the Core Server but the Core Server cannot resolve the agent workstation.

7. NIC driver may not be entirely functioning properly.

8. Name resolution problems may prevent the core from targeting the machine by DNS name.

Resolutions

1. Start or restart the Inventory Service.

2. Search for the IP address that WinPE has.  If another device has this IP address, delete that inventory record.

3. That device may show up twice in the database.  Delete all devices with that MAC Address.  See
   community article 1569 for assistance with this.

4. Open UDP ports 9595 39293 between the Core Server and the Agent workstation.

5. Go to Configure | Services | Custom Jobs and set the Discovery to try both UDP and TCP.

6. Go to Configure | Services | Custom Jobs and check the box to Disable DNS/WINS Lookup.

7. Make sure the Core Server can ping the Agent workstation by name and IP.

8. Update the NIC driver In the WinPE image.

9. Make sure the Core Server and PXE reps are running the same version of software.

10. Verify that the client miniscans are being received by the core server. Enable the Store Scans option in Configure | Service | Inventory | Advanced. Set the value to 1 and restart the Inventory service. Browse to the ldmain\ldscan\Storage directory and verify that .IMS files are being received when the client boots into WinPE.

11. Verify that the core is processing mini scans. Check Configure | Services | Inventory | Advanced | Ignore mini scans. This value needs to be set to 0.

In the event that the certificate files are not valid inside of the boot images

1. Navigate to \Program Files (x86)\LANDesk\ManagementSuite

2. Run "osd.upgrade.exe"

3. This will inject the proper core certificates into the boot images.