my personal blog about systemcenter

All posts in Service Manager

Install SCOM Agent on computer with Service Manager Console Installed

Categories: SCOM, Service Manager
Comments Off on Install SCOM Agent on computer with Service Manager Console Installed

After a recent upgrade to R2 we wanted to update all SCOM agents , however push to service with Service Manager Console installed failed (this is mostly admin servers and Citrix servers in our enviroment

The SCOM Agent detect is Service Manager is installed and if its installed the installer exits

THIS IS UNSUPPORTED AND IT WILL KILL YOUR SERVICE MANGER SERVER if you force the install on a server , ONLY do this on admin servers or clients that have both the agent and the console installed NEVER on Service Manager Servers

Action ended 09:18:23: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8. Return value 1.

MSI (s) (40:60) [09:18:23:922]: PROPERTY CHANGE: Adding WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 property. Its value is ‘C:\Windows\’.

Action start 09:18:23: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.

MSI (s) (40:60) [09:18:23:922]: Doing action: FindRelatedProducts

Action ended 09:18:23: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9. Return value 1.

Action start 09:18:23: FindRelatedProducts.

MSI (s) (40:60) [09:18:23:923]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT_SMRTM property. Its value is ‘{FE333322-19E9-4B03-B248-DB327D96A92A}’.

MSI (s) (40:60) [09:18:23:923]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)

MSI (s) (40:60) [09:18:23:924]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)

MSI (s) (40:60) [09:18:23:924]: Skipping action: _Set_OM_AGENT_FOUND (condition is false)

MSI (s) (40:60) [09:18:23:924]: Skipping action: _Set_MOMV3_AGENT_FOUND (condition is false)

MSI (s) (40:60) [09:18:23:924]: Doing action: _Set_CORECOMPONENTPRESENT

Action ended 09:18:23: FindRelatedProducts. Return value 1.

MSI (s) (40:60) [09:18:23:924]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT property. Its value is ‘{FE333322-19E9-4B03-B248-DB327D96A92A}’.

Action start 09:18:23: _Set_CORECOMPONENTPRESENT.

MSI (s) (40:60) [09:18:23:924]: Skipping action: _AbortDowngradeProductAttempt (condition is false)

MSI (s) (40:60) [09:18:23:924]: Doing action: _AbortCoreComponentPresent

Action ended 09:18:23: _Set_CORECOMPONENTPRESENT. Return value 1.

Action start 09:18:23: _AbortCoreComponentPresent.

MSI (s) (40:60) [09:18:23:925]: Product: Microsoft Monitoring Agent — The Microsoft Monitoring Agent cannot be installed on a computer on which the Operations Manager management server, gateway server, Operations console, operational database, web console, System Center Essentials, or System Center Service Manager is already installed.

The Microsoft Monitoring Agent cannot be installed on a computer on which the Operations Manager management server, gateway server, Operations console, operational database, web console, System Center Essentials, or System Center Service Manager is already installed.

Action ended 09:18:23: _AbortCoreComponentPresent. Return value 3.

—-

The workaround is normally to uninstall the Service Manager Console , Install the Agent and Install the Console Again

clip_image002

However if we rename the Service Manager Installer registry key

clip_image004

We can then install the SCOM agent

and then rename the registry back to normal

MSI (s) (40:94) [09:27:48:572]: Note: 1: 1707

MSI (s) (40:94) [09:27:48:572]: Product: Microsoft Monitoring Agent — Installation operation completed successfully.

MSI (s) (40:94) [09:27:48:578]: Windows Installer har installeret produktet. Produktnavn: Microsoft Monitoring Agent. Produktversion: 7.1.10184.0. Produktsprog: 0. Producent: Microsoft Corporation. Installationen lykkedes eller fejlstatus: 0.

New Service Manager Book out from Microsoft Press

Categories: Book, Service Manager, Thomas Ellerman
Comments Off on New Service Manager Book out from Microsoft Press

Hi All

Thomas Ellerman , Kathleen Wilsen , Karsten Nielsen and John Clark have written a book for Microsoft Press and edition by Mitch Tulloch

Microsoft System Center: Optimizing Service Manager

Its a free ebook so just in time for a early xmas gift for all your friends :)

http://shop.oreilly.com/product/0790145396716.do , the book is out in print for about 2 cups of coffee

 

Its that time a year again a clean install of the servers in our combined playground and demo enviroment , ripped out 5 old servers and added 4 new ones saving 20kw hours a day and with our power cost its adds up to 150ish euro a month.

The enviroment currently is mixed playground and customer facing demo enviroment this is mainly due to resource constrains and with new servers version hopefully presented at build its not getting any easier to fit , so more servers are on their way

 

image

Part one is the basic hyper-v enviroment , next is vmware and xen adding up with 6 servers dedicated to hypervisors.

Part two is Data Protection Manager 2012 SP1 running in a phsycial box to protect the enviroment

There are 2 other servers reserved for Virtual Machine Manager bare metal deployment everything else will be virtual.

Part three is “just” the remaining systemcenter parts , with focus om VMM/Service Manager and Operations Manager , and the integration glue with Orchestrator , Config Manager will follow for patching and protection but since i need to do a windows-noob.com from end to end to deploy it its a nice to have at some point in time.

Part four is Direct Access , PKI , Remote Desktop Services

Part five is everything else Smiley

 

Service Manager 2012 SP1 installs a Operations Manager agent on the Service Manager

 

image

So instead of having to rely in agentless monitoring of the Service Manager management servers we now have the agent supplied in the box , not that the install path is also in service manager not in operations manager

 

image

 

On the operations Manager Server we need to ensure that manual agent install is permitted

 

image

In the control panel on the service manager server add the management group that use used for operations manager , and you will see the agent in operations manager after you apply the changes