Windows Deployment Service

Summary

This monitor tracks the status of the Windows Deployment Services Server service. When this service is stopped, and the network is not configured as a topology 5 network (All nodes only on an enterprise network), the deployment of compute nodes will encounter errors.

Causes

This error can be caused by any of the following:

• The network is not correctly configured.

• The network is configured as a topology 5 network. The Windows Deployment Services Server service does not start automatically under this network topology.

• The Windows Deployment Services Server service encountered an error and had to stop running.

• The Windows Deployment Services Server service is disabled.

• Group policy does not allow this service to start.

Resolutions

To troubleshoot and fix this problem:

• If the network topology needs to be topology 5, then this monitor can be disabled.

• Restart the Windows Deployment Services Server service on the target head node.

• If the service cannot be started, resolve the errors that are reported by the Service Control Manager. The Service Control Manager will produce an error event if the service is terminated unexpectedly. Start Server Manager and check the Windows Deployment Services role. Resolve any errors that are reported by these events in this role service.

• If the service still cannot be restarted, contact the domain administrator to make sure that this service is not disabled by the domain group policy.

• If the preceding steps do not resolve the problem, uninstall and reinstall the HPC Pack on the compute node and reconfigure the network topology.

Additional

Recovery task will be run automatically to restart the service, so you may find the service keeps restarting while you are trying to stop it. There are couple of options to avoid it happen:

• Disable the recovery task;

• Change the service to start manually.