All Unit Monitors in Microsoft.Windows.Server.WDS.2012 Management Pack

	DisplayName	Description	ID	Target	Parent Monitor	Category	Enabled	Instance Name	Counter Name	Frequency	Alert Generate	Alert Severity	Alert Priority	Alert Auto Resolve	Monitor Type	Remotable	Accessibility	RunAs
	Configuration Settings Updates	The Pre-Boot Execution Environment (PXE) server is used by Windows Deployment Services to provide network boot programs to client computers. The PXE server obtains configuration settings from the registry at startup time.	Microsoft.Windows.Server.6.2.WDSRole.ConfigurationSettingsUpdates	Microsoft.Windows.Server.6.2.WDSRole	System.Health.ConfigurationState	ConfigurationHealth	True			0	True	Error	Normal	True	Microsoft.Windows.2SingleEventLog2StateMonitorType	True	Public
	Rogue Detection State	Windows Deployment Services requires interaction with Active Directory Domain Services for several critical functions. One of these functions is rogue detection, which determines whether the Pre-Boot Execution Environment (PXE) server is authorized to provide services in the domain. Rogue detection is also known as Dynamic Host Configuration Protocol (DHCP) authorization.	Microsoft.Windows.Server.6.2.WDSRole.RogueDetectionState	Microsoft.Windows.Server.6.2.WDSRole	System.Health.AvailabilityState	StateCollection	True			0	True	MatchMonitorHealth	Normal	True	Microsoft.Windows.3SingleEventLog3StateUnitMonitorType	True	Public
	Check the registry configuration or reinitialize the server		Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer.ADIntegration.Check_the_registry_configuration_or_reinitialize_the_server	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer	System.Health.AvailabilityState	AvailabilityHealth	True			0	True	Error	Normal	True	Microsoft.Windows.2SingleEventLog2StateMonitorType	True	Public
	Ensure that the PXE provider can contact Active Directory Domain Services		Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer.ADIntegration.Ensure_that_the_PXE_provider_can_contact_Active_Directory_Domain_Services	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer	System.Health.AvailabilityState	AvailabilityHealth	True			0	True	Error	Normal	True	Microsoft.Windows.2SingleEventLog2StateMonitorType	True	Public
	Ensure that the WDSServer service can read settings from Active Directory		Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer.ADIntegration.Ensure_that_the_WDSServer_service_can_read_settings_from_Active_Directory	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer	System.Health.AvailabilityState	AvailabilityHealth	True			0	True	Error	Normal	True	Microsoft.Windows.2SingleEventLog2StateMonitorType	True	Public
	Find a solution for event 513 or register Wdsmgmt.dll		Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer.ADIntegration.Find_A_Solution_For_event_513_or_register_Wdsmgmt_dll	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer	System.Health.AvailabilityState	AvailabilityHealth	True			0	True	Error	Normal	True	Microsoft.Windows.2SingleEventLog2StateMonitorType	True	Public
	Specify a different name or grant permissions		Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer.ADIntegration.Specify_a_different_name_or_grant_permissions	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer	System.Health.AvailabilityState	AvailabilityHealth	True			0	True	Error	Normal	True	Microsoft.Windows.2SingleEventLog2StateMonitorType	True	Public
	Auto-Add Devices Database State	The Auto-Add Devices database enables you to add computer accounts to Active Directory Domain Services automatically. You will find this database in the \RemoteInstall\Mgmt folder (by default, the RemoteInstall folder is located on drive C). The database is created by the Pre-Boot Execution Environment (PXE) provider the first time you enable the Auto-Add functionality (using either the MMC snap-in or the /AutoAddPolicy command-line option). All computers in the pending queue are represented as an entry in the database on the Windows Deployment Services server.	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer.AutoAddDevicesDatabaseState	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer	System.Health.AvailabilityState	AvailabilityHealth	True			0	True	MatchMonitorHealth	Normal	True	Microsoft.Windows.3SingleEventLog3StateUnitMonitorType	True	Public
	Image Server Configuration	For the boot and install images to be available, the Windows Deployment Services image server must be configured and initialized correctly. The image server stores configuration information in the registry and in Active Directory Domain Services.	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer.ImageServerConfiguration	Microsoft.Windows.Server.6.2.WDSRole.Service.DeploymentServer	System.Health.ConfigurationState	ConfigurationHealth	True			0	True	Error	Normal	True	Microsoft.Windows.2SingleEventLog2StateMonitorType	True	Public
	TFTP Initialization State	When the WDSServer service is started, the Trivial File Transfer Protocol (TFTP) server reads the configuration settings in the registry that apply to the TFTP server. Note that the TFTP server will not function correctly until it has initialized successfully.	Microsoft.Windows.Server.6.2.WDSRole.TFTPInitialization	Microsoft.Windows.Server.6.2.WDSRole	System.Health.ConfigurationState	AvailabilityHealth	True			0	True	MatchMonitorHealth	Normal	True	Microsoft.Windows.3SingleEventLog3StateUnitMonitorType	True	Public
	WDSServer State	The state of the WDSServer service determines whether the service is started and operating normally. WDSServer is the main server-side service of the Windows Deployment Services solution. It provides basic service functions such as memory management, thread pooling, and network interface binding.	Microsoft.Windows.Server.6.2.WDSRole.WDSServerServiceState	Microsoft.Windows.Server.6.2.WDSRole	System.Health.AvailabilityState	AvailabilityHealth	True			0	True	Error	High	True	Microsoft.Windows.CheckNTServiceStateMonitorType	True	Public