If you’re looking for a good resource for troubleshooting OpsMgr 2007 client agent install issues then this new KB article we published today is for you:
The System Center Operations Manager 2007 (SCOM 2007) agent can be deployed to Windows computers either via "remote push" from a management server or it can be manually installed on a target computer using MomAgent.msi. If the installation of the agent is not successful, there are a number of troubleshooting steps that can be used depending on where the error is occurring and how the agent will be deployed.
Verify the target computer meets the supported configuration The initial step in troubleshooting installation of the Operations Manager agent on a Windows computer is to verify that the potential agent meets the supported hardware and software configuration. The following article lists the requirements for an Operations Manager 2007 agent:
Operations Manager 2007 R2 Supported Configurations
If the target system is a Unix/Linux computer, verify that the distribution and version are supported. Please note that support for some versions requires post-R2 cumulative updates. The following article has the supported versions of Unix/Linux:
System Center Operations Manager 2007 R2 Cross Platform Monitoring Management Packs
Troubleshooting Agent Deployment via the Discovery Wizard in the Operations Manager Console If the agent will be deployed by means of discovery from the Operations Manager console, the agent will be installed from the management server or gateway server specified in the discovery wizard to manage the agent, not the server the operations console was connected to when it opened. Any testing, therefore, should be conducted from the management server or gateway specified when the wizard is run or a different management server/gateway should be specified during the wizard to see if the same error occurs.
The following articles provide some good background about deploying the Operations manager agent using discovery from the Management Server:
How to Deploy the Operations Manager 2007 Agent Using the Agent Setup Wizard How does Computer Discovery Work in OpsMgr 2007? Agent discovery and push troubleshooting in OpsMgr 2007 Console based Agent Deployment Troubleshooting table
Troubleshooting Agent Deployment via the Operations Manager Command Shell In some situations, automatic discovery of potential agents may time out due to very large or complex Active Directory environments. Other situations may require that automatic discovery be run with an LDAP query that is more limited than what is available in the UI. In these cases, automatic discovery of computers and remote installation of the Operations Manager agent is possible via the Operations Manager command shell. The following blog posting gives the syntax required to do this:
Discovering Windows Computers via PowerShell
Troubleshooting Agent Deployment via Verbose Windows Installer Logging If the installation of the agent on a remote computer fails during installation, a verbose Windows Installer log may be created on the management server in the following default location:
C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs
The log can be used to determine if there was a specific error encountered and may be useful to further troubleshoot installation of the Operations Manager agent on the target computer.
Look for the first entry with the string "Return Value 3" in the log. The preceding few lines will usually indicate the error that Windows Installer encountered. The format will typically be in the form of "function / description of error / error return code", and can indicate permission issues, missing files or other settings that need to be changed. Examples:
There are many possible errors that can be logged here. Other individual errors can be further researched on TechNet or the Online Knowledge Base.
Troubleshooting Manual installation of the Operations Manager Agent In cases where the Operations Manager agent cannot be deployed to a remote computer via the Discovery Wizard, the agent will need to be installed manually. This can be performed via command line using the MomAgent.msi file. The following references describe the various switches and configuration options available to perform a manual installation:
How to Deploy the Operations Manager 2007 Agent Using MOMAgent.msi from the Command Line Windows Agent Install MSI Use Cases and Commands Process Manual Agent Installations in Operations Manager 2007
If the agent is deployed via manual install, future Service Pack updates or cumulative updates will need to be manually deployed as well. Computers that have been manually installed will not be designated by the System Center Configuration Management service as being remotely manageable, and the option to upgrade them will not be presented in the Operations Console.
Other key considerations to account for during the manual installation of agents:
Errors that prevent agents from being installed manually can be identified in the Windows Installer setup logs. The following command can be used to enable verbose Windows Installer logging of the Operations Manager agent installation: msiexec.exe /i "MOMAgent.msi" /l*v "C:\Agent\MOMAgent_install.log"
As an alternative, the following article describes how to enable verbose Windows Installer logging globally on a Windows computer: How to enable Windows Installer logging
Look for the first entry with the string "Return Value 3" in the log. The preceding few lines will usually indicate the error that Windows Installer encountered. The format will typically be in the form of "function / description of error / error return code", and can indicate permission issues, missing files or other settings that need to be changed.
For the most current version of this article please see the following:
2566152: Troubleshooting the Installation of the System Center Operations Manager 2007 Agent
J.C. Hornbeck | System Center Knowledge Engineer
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/