This script runs on all Windows servers and determines if the server is hosting the DHCP 2003 Server role. If it is, it collects all the required information and creates the required classes within OpsMgr 2007 necessary to monitor the service.
DHCP Server 2003 Server Discovery script discovers the DHCP 2003 Server object, related properties and relationship.
These are the parameters that we could override, if need it:
IntervalSeconds: Amount of Seconds for each execution
SyncTime: Time expressed with this format: "hh:mm" since you will like to start the execution.
TimeoutSeconds: Amount of seconds to wait until cancel execution for "timeout reasons."
DebugFlag: Use "true" or "false" to record different events in the Operation Manager Event Logs for tracking purposes.
| Target | Microsoft.Windows.Server.Computer |
| Enabled | True |
| Frequency | 43200 |
| Remotable | False |
| Discovered Classes and their attribuets: |
|---|
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| Microsoft.Windows.DHCPServer.2003.Discovery.Server | DataSource | Microsoft.Windows.DHCPServer.2003.DataSource.ServerDiscovery | Microsoft.Windows.DHCPServer.Library.ActionAccount |
Home<Discovery ID="Microsoft.Windows.DHCPServer.2003.ServerDiscovery" Enabled="true" Target="Windows!Microsoft.Windows.Server.Computer" ConfirmDelivery="true" Remotable="true" Priority="Normal">
<Category>Discovery</Category>
<DiscoveryTypes>
<DiscoveryClass TypeID="Microsoft.Windows.DHCPServer.2003.Server"/>
</DiscoveryTypes>
<DataSource ID="Microsoft.Windows.DHCPServer.2003.Discovery.Server" RunAs="DHCP!Microsoft.Windows.DHCPServer.Library.ActionAccount" TypeID="Microsoft.Windows.DHCPServer.2003.DataSource.ServerDiscovery">
<IntervalSeconds>43200</IntervalSeconds>
<SyncTime/>
<TimeoutSeconds>300</TimeoutSeconds>
<DebugFlag>false</DebugFlag>
</DataSource>
</Discovery>