If the Discovery Wizard cannot locate a system that it should be able to find, use the following procedures to diagnose the problem.
Verifying That Systems Can Be Contacted
Verify that discovered computers can be contacted.
To verify that systems can be contacted
In the Administration pane, click Discovery Wizard, or if the Wizard is already open, click Previous to return to the Auto or Advanced? page.
Select the Advanced discovery option.
Select Verify discovered computers can be contacted.
Proceed through the wizard.
Checking Active Directory
Check whether the computer is listed in Active Directory by using the Active Directory Users and Computers tool.
- The Active Directory Users and Computers tool
is installed by default on Windows Server 2003.
- The Active Directory Users and Computers tool
can be installed on Windows XP Professional from the Windows
Server 2003 Resource Kit Tools, which is available at http://go.microsoft.com/fwlink/?LinkId=92512.
To check whether a system is listed in Active Directory
In Control Panel, double-click Administrative Tools, double-click Component Services, and then expand Active Directory Users and Computers.
Right-click the Saved Queries folder, click New, and then click Query to open the New Query dialog box.
Enter a name for the query.
Click Define Query.
Click the Find drop-down list, and then select Computers.
Enter the name or search prefix, and then click OK.
Click OK to close the New Query dialog box.
Verify that the computer appears in the list of results.
If some computers are not listed, it might be because there are errors in the query or because the computers are not joined to the target domain.
|Make sure the DNSHostname property is set correctly for the computer. The DNSHostname property can be viewed on the General tab of the computer’s property dialog box in Active Directory Users and Computers.|
Check whether the computer can be reached from the management server or gateway server.
To check whether the server can reach a system
From the management server or gateway server, use the ping command to reach the computer, using the same name that is provided to the Discovery Wizard.
When the computer responds to the ping command, run ping with the -a switch and the IP address. The -a switch displays the Domain Name System (DNS) name of the computer, which should match what you used in your first ping command.
Use nbtstat -a <computer name> to see the registered NetBIOS name and the domain for the computer. Use nbtstat -A <IP address> to see the registered NetBIOS name and the domain based on the IP address.
If the computer does not respond to a ping command or if it fails a remote agent install with RPC Service Unavailable, then the Windows Firewall is turned on. Set exceptions to allow File and Printer Sharing and, optionally, ICMP Echo. For more information, see http://go.microsoft.com/fwlink/?LinkId=92545.
If the NetBIOS name and the fully qualified domain name (FQDN) name do not match, then the DNS records for the computer must be corrected. Consult your network administrator.
If the agent installs but fails to contact the Operations Manager management server, connect to the agent computer by using Terminal Services or Remote Desktop, and use the ping and nbtstat commands to verify that the agent can resolve the NetBIOS and FQDN names of the Operations Manager management server that will manage it. Also, you can look at the Operations Manager event log by using Event Viewer on the agent computer.
If the Discovery Wizard displays a Discovery failed message, the cause may be account permissions. The account that is used for discovery must have appropriate permissions on the target computer.
To verify an account has correct permissions
Open a Command Prompt window with the Run As option and use the account that is used for discovery. By default, the Discovery Wizard uses the Management Server Action Account.
Use the net view ComputerName command to verify that the account can connect to the specified system.
- The result There are no entries in the
list means that the computer does not have any publicly visible
- The result Access denied means that
the account used does not have permission to contact the
- The result The command completed
successfully means that the computer is properly configured for
- The result There are no entries in the list means that the computer does not have any publicly visible shares.
If the account does not have permission, select a different account that does have permission to contact the computer. By default, members of the local Administrators and Power Users groups should have this permission.
If the Discovery Wizard can find a system but cannot install the agent due to permissions, use the following procedure.
To select an appropriate account for installing agents
In the Administration pane, reject the pending agent installation from the Pending Management view under Device Management.
Run the Discovery Wizard again.
On the Administrator Account page, select Other user account, and then provide an account (domain or local) that has administrator privileges on the computer.
If the account is a local account or does not have rights to access Active Directory, select This is a local computer account, not a domain account on the Administrator Account page of the Discovery Wizard. The computer uses the management server action account for discovery and the local computer account for agent installation.
Continue through the Discovery Wizard.
TasksHow to Deploy the Operations Manager 2007 Agent to Windows-Based Computers from the Operations Console
ConceptsOperations Manager 2007 Accounts
Security for Discovery-Based Deployment in Operations Manager 2007
Other ResourcesHow to Use Active Directory Domain Services to Assign Computers to Operations Manager 2007 Management Groups
Did you find this information useful? Please send your suggestions and comments about the documentation.