Users Guide

○ To create hostname record
>dnscmd <DnsServer> /RecordAdd example.com omehost A XX.XX.XX.XX
○ To add records for server-initiated discovery
>dnscmd <DnsServer> /RecordAdd example.com _dcimprovsrv._tcp PTR
ptr.dcimprovsrv._tcp.example.com
>dnscmd <DnsServer> /RecordAdd example.com ptr.dcimprovsrv._tcp TXT URI=/api/
DiscoveryConfigService/Actions/DiscoveryConfigService.SignalNodePresence
>dnscmd <DnsServer> /RecordAdd example.com ptr.dcimprovsrv._tcp SRV 0 0 443
omehost.example.com
2. By default, the Discovery-Approval policy, in the appliance, is set to Automatic and the servers that establish contact with
the console are automatically discovered. To change the settings, see Manage Console preferences on page 157.
3. Once the appliance is configured as mentioned in the previous steps, the servers can initiate contact with OpenManage
Enterprise by querying the DNS. The appliance verifies the servers after ensuring that the client certificate of the servers is
signed by the Dell CA.
NOTE: If there are any changes in the server IP address or SSL certificate, the server reinitiates contact with
OpenManage Enterprise.
4. The Monitor > Server Initiated Discovery page lists the servers that establish contact with the console. Also, the servers
whose credentials have been added in the console, but which are yet to initiate contact are also listed. The following
statuses of the servers based on the previously mentioned conditions are displayed:
● Announced—Server initiates contact with the console, however, the credentials of the server are not added to the
console.
● Credentials Added—The credentials of the server are added in the console, however, the server has not initiated contact
with the console.
● Ready to Discover—The credentials of the server are added and the server has initiated contact.
NOTE:
The appliance triggers a Discovery job every 10 minutes to discover all the servers in the 'Ready to Discover'
status. However, if the Discovery-Approval policy in the appliance is set as 'Manual,' then the user should manually
trigger the Discovery job for each server. For more information, see Manage Console preferences on page 157
● Job submitted for Discovery—This status indicates that the discovery job is initiated either automatically or manually for
the server.
● Discovered—The server is discovered and is listed on the All Devices page.
The following tasks can be performed on the Monitor > Server Initiated Discovery page:
1. Import—To import the server credentials:
a. Click Import.
b. In the Import From File wizard, click Upload Service Tags File to navigate and select the .csv file.
To view a sample CSV file of the server credentials, click Download sample CSV file.
c. Click Finish
2. Discover—To manually discover the servers in 'Ready to Discover' status:
a. Select the servers listed on the Server-Initiated Discovery page which are in 'Ready to Discover' Status.
b. Click Discover.
A Discover job is triggered to discover the servers and post discovery these servers are listed on the All Devices page.
3. Delete—To delete the servers listed on the Server-Initiated Discovery page:
a. Select the servers on the Server-Initiated Discovery page which are already discovered and listed on the All Devices
page.
b. Click Delete.
The servers are deleted from the Server-Initiated Discovery page.
NOTE: Entries corresponding to discovered servers are automatically be purged after 30 days.
4. Export—To export the server credentials in HTML, CSV, or PDF formats:
a. Select one or more servers on the Sever-Initiated Discovery page.
b. Click Export.
Discovering devices for monitoring or management
41