To implement MOM functions, we must deploy MOM agents on all monitored servers efficiently. In MOM 2005, we can remotely push out MOM agent from MOM Administrators console. However, since the productive environment is complex, the remote push installation may be failed due to various reasons.
To improve MOM agent push installation successful rate and prevent potential push installation errors, we provide the following content for your reference:
A. Supported/suggested environment for push installation:
- MOM agents and MOM servers are in the same domain. Or the MOM agent domain and MOM server domain are trusted each other.
- There is no firewall enabled between MOM agent and MOM server.
- There is no slow link between MOM agent and MOM server.
- Machines in workgroup are supported in MOM 2005. However, for these machines, we can only manually install MOM agent on them.
- If there is firewall between MOM agent and MOM server, we can still use remote push installation method to deploy MOM agent on them after enable proper ports on firewall. You can refer to the following web site to know more information:
- For the slow link connection, it is referring to the link which speed is below than 512K bites per second.
- For the machines which are not suggested to use remote push installation method, we have to manually install MOM agent on them using the method in the above KB article Q904866.
B. Supported Operation Systems for push installation:
- 32-bit Windows 2000 server SP4 and above version.
- 32-bit Windows XP profession
- 32-bit Windows 2003 server.
Note: For all 64-bit computes, we have to manually install 64-bit MOM agent on them by running MOMAgent.msi under MOM installation CD and ia64 folder.
C. Pre-requirement for push installation.
- The MOM Server action account or the account input during MOM agent push installation wizard should be in the local administrators group on the targeted agent machines. We can use the setactionaccount.exe tool to query the MOM server action account (see http://support.microsoft.com/default.aspx?scid=KB;en-us;Q883347 for more information)
- The remote registry service should be started on the targeted agent machines.
- The admin shares (such as ADMIN$, C$, D$) are enabled on the MOM agent machines.
- The Server service and workstation service are started on the targeted agent machine.
- Windows Installer 3.1 is installed on the targeted agent machines. The Windows installer 3.1 can be downloaded from the following web site:
- If the targeted agent machine is Windows XP SP 2 or Windows 2003 SP1, we need to enable proper ports and ensure the MsMgmtAuxiliary.exe application and run over network. For more information, please refer to the following KB article:
- If the targeted agent machine or the MOM server is Windows 2003 SP1, please ensure that the following hotfixes have been applied:
Note: in KB Q912998, there is no available hotfix file. We need to follow the steps in this KB article to change the LSA registry value.
Appendix: The normal MOM agent push installation process and troubleshooting logs.
MOM Agent push installation process is:
1. Connect to the targeted agent machine’s registry key to get the general Operations System information.
2. Connect to the targeted agent machine’s system drive.
3. Create a temp folder on the root folder of system drive. Then copy MOM agent installation files from MOM server to the temp folder.
4. Install and start MsMgmtAuxiliary service on remote agent computer.
5. The MsMgmtAuxiliary service will then start the Windows Installer service to install actual MOM agent. If the installation is failed after the Windows Installer service start, there will be a detailed MSI log named as %AgentComputerName%AgentInstall.log. We can find this log file on MOM server and MOM Installation folder \AgentLogs folder.
Author: Simon Xin
To implement MOM functions, we must deploy MOM agents on all monitored servers efficiently. In MOM 2005,
PingBack from http://alpesh.nakars.com/blog/?p=104