Unable to setup MOM management pack on Exchange 2007 CAS and HT servers
Hi
I have installed two Exchange 2007 SP1 Client Access servers and two Hub Transport servers in a our existing Exchange 2003 organization.
The first HT and CAS installations were successful, both installed with update rollup 9. The second HT and CAS installations were installed, but Exchange services wouldn't start. After installing update rollup 9 on these servers aswell, the services started automatically after reboot.
Everything works fine.
But then a collegue of mine was going to deploy MOM with Exchange management packs to the servers, and he realized that MOM was unable to "see" the second HT and CAS server.
He found out that MOM is looking for Exchange roles in the registry. It looks for ConfiguredVersion = "8.*".
The registry keys:
First Hub Transport server - OK
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"ConfiguredVersion"="8.1.2
Second Hub Transport server - Initial install failed, worked after Update Rollup 9
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"Action"="Install"
"Watermark"=dword:cf64a9b8
First Client Access Server - OK
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"ConfiguredVersion"="8.1.2
Second Client Access server - Initial install failed, worked after Update Rollup 9
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"Action"="Install"
"Watermark"=dword:00ed997e
The ConfiguredVersion item is missing from the second HT and CAS server.
I have search the net for information on this, but without luck.
Is there anyone who can explain why this happened? Is it because I installed the update rollup on the first server before installing the second server?
Installation order:
1. First HT
2. Update rollup 9 on first HT
3. Second HT
4. Update rollup 9 on second HT
5. First CAS
6. Update rollup 9 on first CAS
7. Second CAS
8. Update rollup 9 on second CAS
How do I solve this issue? I'm affraid a reinstallation will end up with the same result.
Maybe it is safe to make the corrections to the registry? It seems straight forward.
Thanks
Regards
Michael
I have installed two Exchange 2007 SP1 Client Access servers and two Hub Transport servers in a our existing Exchange 2003 organization.
The first HT and CAS installations were successful, both installed with update rollup 9. The second HT and CAS installations were installed, but Exchange services wouldn't start. After installing update rollup 9 on these servers aswell, the services started automatically after reboot.
Everything works fine.
But then a collegue of mine was going to deploy MOM with Exchange management packs to the servers, and he realized that MOM was unable to "see" the second HT and CAS server.
He found out that MOM is looking for Exchange roles in the registry. It looks for ConfiguredVersion = "8.*".
The registry keys:
First Hub Transport server - OK
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"ConfiguredVersion"="8.1.2
Second Hub Transport server - Initial install failed, worked after Update Rollup 9
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"Action"="Install"
"Watermark"=dword:cf64a9b8
First Client Access Server - OK
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"ConfiguredVersion"="8.1.2
Second Client Access server - Initial install failed, worked after Update Rollup 9
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWA
"UnpackedVersion"="8.1.240
"Action"="Install"
"Watermark"=dword:00ed997e
The ConfiguredVersion item is missing from the second HT and CAS server.
I have search the net for information on this, but without luck.
Is there anyone who can explain why this happened? Is it because I installed the update rollup on the first server before installing the second server?
Installation order:
1. First HT
2. Update rollup 9 on first HT
3. Second HT
4. Update rollup 9 on second HT
5. First CAS
6. Update rollup 9 on first CAS
7. Second CAS
8. Update rollup 9 on second CAS
How do I solve this issue? I'm affraid a reinstallation will end up with the same result.
Maybe it is safe to make the corrections to the registry? It seems straight forward.
Thanks
Regards
Michael
avishar
The Exchange Installation has nothing to do with the MOM/SCOM agent installation, how are you installing the agents, from the MOM Console or locally on the Exchange server's.
ASKER
Thanks for the quick answer.
I know. The issue is really the difference in registry on the same type of servers, and how do I fix that.
The MP is deployed from the MOM console
I know. The issue is really the difference in registry on the same type of servers, and how do I fix that.
The MP is deployed from the MOM console
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We'll try just creating the missing ConfiguredVersion registry key.
I'll get back with the result
I'll get back with the result
ASKER
We currently have some trouble to get MOM to recognize Exchange, even though we have fulfiled MOM's search criteria by adding the ConfiguredVersion registry key.
1).Is the MOM client installed on those Exchange boxes ? If yes then what events do you see in the
MOM event log's on the Exchange box.
2).Are there orphan entries for these boxes in the SCOM database, what is the output of the following
sql command ?
>select toplevelhostentityid from basemanagedentity where path like '%computername%'
MOM event log's on the Exchange box.
2).Are there orphan entries for these boxes in the SCOM database, what is the output of the following
sql command ?
>select toplevelhostentityid from basemanagedentity where path like '%computername%'
ASKER
The MOM client is installed and is monitoring Windows
We currently use MOM 2005, so the table refered to doesn't exist.
My colleuge is going to uninstall the agent and reinstall it.
We currently use MOM 2005, so the table refered to doesn't exist.
My colleuge is going to uninstall the agent and reinstall it.
ASKER
We never got MOM to discover the second CAS and HT servers by it self. My collegue had to manually configure MOM to monitor Exchange.
But I never got real answer to how this happene, with the misconfiguration in registry and how solve it in a proper way.
But we managed to get problem with MOM solved as noted above.
But I never got real answer to how this happene, with the misconfiguration in registry and how solve it in a proper way.
But we managed to get problem with MOM solved as noted above.
ASKER
A proper (documented) way to solve this issue was never found.