NOTE: The text in the following Microsoft Knowledge Base article is provided so that the site search can find this page. Please click the Knowledge Base link to insure that you are reading the most current information.
Microsoft Knowledge Base article Q825037 contains:
SYMPTOMSWhen you boot a device (a computer that is controlled by Automated Deployment Services \[ADS\]) into the Deployment Agent, the device stops responding, and you receive the following message:
After several minutes, the device restarts, and the ADS process begins again.
On Windows Server 2003-based computers that run ADS, you may see the following events in the application event log.
Note If ADS is not collocated (that is, if all the services are running on one server), these events appear in the application event log of the computer that is running the service that is mentioned in the Event Source field.
Event Type: Warning
Event Source: adsctlr
Event Category: None
Event ID: 535
Time: 10:44:39 AM
User: N/A Computer: computer name
Description: Failed to find a default job template for the device mycomputer.win2k3.com to respond to the PXE boot request.
Event Type: Warning
Event Source: ADSPXE
Event Category: PXE
Event ID: 517
Time: 10:40:52 AM
Description: The ADS deployment agent with MAC address 0000395FBB18 rebooted because boot-policy was not available.
CAUSEThis issue may occur if either of the following conditions is true:
- The default job template is not defined for the device (and a task is not currently running against the device).
- Network Boot Service (NBS) cannot contact the ADS Controller service.
Note NBS queries the ADS Controller service only one time for the boot policy. However, the Pre-Boot eXecution Environment (PXE) client queries NBS every 5 seconds for the boot policy until it has performed the query 50 times. After 50 queries, the device restarts, and then the process begins again. When a device enters this state, even resetting the default job template does not resolve the issue. The default job template will not be checked again after NBS successfully queries the ADS Controller service one time and receives a response, even if the response is null (that is, no default job template is defined).
The Default Job Template Is Not Defined for the DeviceTo resolve this issue, assign a default template to the device. If the device has an operating system installed, the default template must be "boot-hd." Microsoft also recommends that you specify a default job template at the end of your task sequence when you image a device that has an operating system installed. For additional information about default job templates, see the "Job Templates Overview" section in ADS online Help.
Note If no default job template is defined for the device, you will see events 517 and 535 in the application event log.
NBS Cannot Contact the ADS Controller ServiceTo resolve this issue, make sure that NBS and the Controller service are in a Connected state and that they can communicate. To verify this state, follow these steps:
- On the Controller, start ADS Management. To do this, click Start, point to All Programs, point to Microsoft ADS, and then click ADS Management.
- Expand Automated Deployment Services
(server name), click Services, and then verify that the Controller
service and NBS state is Connected under State in the right pane.
Note You may have to update the console view first. To do this, click Refresh on the Action menu.
- On the Controller, type adsservice /l at the command prompt,
and then press ENTER.
In the results, verify that both Controller and NBS show a status of Connected under State.
- Check the application event log on the Controller to see if there are any warnings or events for the ADS PXE service (adspxe) or the ADS Controller service (adsctlr).
- On the Controller, verify that Device Name and IP_address in the properties of
the NBS device are set correctly. To do so, follow these steps:
- Start ADS Management.
- Expand Automated Deployment Services (server name), click Services, and then click Network Boot Services in the right pane.
- In the
Device Name box, verify that the name that is listed is the computer that runs NBS.
If the name is incorrect, remove NBS, and then re-add it to correct the Device Name entry. To do so, follow these steps:
- Right-click Network Boot Services, and then click Delete.
- In the left pane of ADS Management, right-click Services, click Add NBS Server, click the computer that has NBS installed, and then click OK.
- In the right pane of ADS Management, click Network Boot Services.
- In the IP_address box, verify that the IP address is the address of the computer that runs NBS. If the IP address is incorrect, type the correct address in the IP_address box, and then click OK.