Administrator Guide

and the response to this command would be:
&00
NOTE: The system does not use any basic authentication for the V99 command.
Running the HTTP Application Manually
To run the HTTP Application Manually:
1 Launch the command prompt on the system where you have installed WDM.
2 Type the following command:
Wyse-Http-server.exe –u < Username> –p <Password > –Po <Port number>
where — u is the user name for basic authentication, —p is the password for basic authentication, and —po is the port number on
which the HTTP Application is running.
Peer Device is unable to download an Image le
If the peer device is not able to download the bios.img or the cmos.img les, then you must check if the les are available on the PAD
master device under the following folder path: C:\Program Files\WDM.
Determining whether the WDM Agent and WDM Server Communication is related to the PAD Schedule
All communication between the WDM Agent and the WDM Server that is related to the PAD Schedule would have the PAD tag set to 1 as
part of the request or response.
Prole Manager Issues
This section describes the issues you could face with Prole Manager and the steps to troubleshoot them.
WCM Application does not launch during the creation of the Prole Manager Package
This could happen if the WCM application or its components are corrupt or are not available in the Installation folder.
Prole Manager Package does not get deployed
To troubleshoot this issue:
1 Check if Prole Manager is enabled in preferences. For more information.
2 Check if Prole Manager deployment is supported by the client system. For this:
a Select the Device Manager node on the tree pane of the WDM Console.
b On the right-hand pane, select the device to which you want to deploy the package.
c In the Device Properties pane click the Hardware Info tab.
d The WCM Support eld should be set to True. If it is set to False, then it indicates that the client does not support Prole
Manager package deployment and you need to update the WDM Agent on the Client.
3 Check if there are some scheduled packages that are yet to be deployed. Wait till the packages are deployed successfully.
4 Check if there are some scheduled packages in Error state. If there are such packages, then delete them.
5 Check if the client is already updated with the prole manager package prior to the deployment. To verify the same, congure Prole
Manager to deploy another package with a dierent conguration.
Tips to Troubleshoot the Repository
General Tips:
Troubleshooting
109