SCOM 2012 SP1 Agent install issue

Dear all,
Wheni try to push SCOM client , getting below error. Any idea what would be issue ?
The Operations Manager Server could not execute WMI Query "Select * from Win32_OperatingSystem" on computer XXX.XXX.XXX
Operation: Agent Install
Install account: XXXXXX
Error Code: 800706BA
Error Description: The RPC server is unavailable.

Looks Firewall issue only , i have opened below ports , is there any mandatory ports required for SCOM agent installation ?
443
TCP
445
TCP
135
TCP

Similar Messages

Error 1723 when removing scom 2012 sp1 agent

Hi All,
I am trying to remove the scom 2012 SP1 agent from a machine and i get an error - 'Error 1723. There is a problem
with this Windows Installer package. A DLL required for this install to complete could not be run.
Any idea how can i remove the agent from the box. Let me now if any other info required to give a hint to the problem.
Durgesh Kumar

Hi,
Reinstall the agent, and the uninstall ? If possible, reboot the server and then uninstall?
Same issue here:
http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/get-error-1723-there-is-a-problem-with-windows/3d68fc4b-c968-4796-a270-27027a52de3f?page=2
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Upgrading SCOM 2012 SP1 agent to SCOM 2012 R2

Hello All
We have created a new SCOM 2012 R2 environment and now planning to upgrade our agents which are in SCOM 2012 SP1 environment . We want to keep the agents dual homed for some time . I would like to know if there is any kind of automation/script that someone
has already made to upgrade SCOM agent from SP1 to R2 ,and at the same time have it dual homed (pointing to 2 MG)

You may try
1) upgrade the SCOM agent by
msiexec /i MOMAgent.msi /qn /l*v D:\logs\AgentUpgrade.log AcceptEndUserLicenseAgreement=1
2) Add additional management group y using following vb script
Option Explicit
Dim objMSConfig
Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
‘Add a management group
Call objMSConfig.AddManagementGroup ("MyManagementGroupToAdd", "company.sm.net",5723)
For detail, pls. refer to
http://technet.microsoft.com/en-us/library/jj899848.aspx
http://msdn.microsoft.com/en-us/library/hh329017.aspx
Roger

SCCM 2012 SP1 agent install via WSUS

Hi guys,
I'm having got an issue when I try installing the agent via WSUS. When I try installing manually everything seems to work.
Here are the infos from the ccmsetup.log:
==========[ ccmsetup started in process 2252 ]========== ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on platform X86 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Launch from folder C:\WINDOWS\SoftwareDistribution\Download\Install\ ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CcmSetup version: 5.0.7804.1000 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Ccmsetup command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSJoinedToADDomain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Local Machine is joined to an AD domain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetAssignedSiteFromAD ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Begin checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
spNamespace.Open(sNamespacePath), HRESULT=8004100e (e:\nts_sccm_release\sms\framework\ccmutillib\ccmiputil.cpp,1109) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Finished checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADSiteName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD site of machine is DE-Zeilarn ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Attempting to query AD for assigned site code ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2887256160)(MSSMSRangedIPHigh>=2887256160))))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.24.8.0)(mSSMSRoamingBoundaries=DE-Zeilarn)(mSSMSSiteCode=XYZ)))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Verifying Site Compatibility for <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1000' for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site Version = '5.00.7804.1000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities> ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
LSIsSiteVersionCompatible : Site Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site <XYZ> Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetAssignedSiteFromAD : Trying to Assign to the Site <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Got site code 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
HTTP is selected for Client. The current state is 0. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
The MP name retrieved is 'mysccmserver.mydomain.tld' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities>' ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
MP 'mysccmserver.mydomain.tld' is not compatible ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieved 0 MP records from AD for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
SslState value: 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Detected sitecode 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPPORT:    80 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSPORT:    443 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSSTATE:    480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSCERTNAME:    ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FSP:    ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTISSUERS:    CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMFIRSTCERT:    1 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Creating CCMCertStore ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTID:    SMS;FB0F35392A7FF68D2FA9C97D0CD54A3E0057964E ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Looking for MPs from AD... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current directory 'C:\WINDOWS\SoftwareDistribution\Download\Install' is not a valid source location. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
DetermineInstallSource(), HRESULT=80004005 (e:\nts_sccm_release\sms\setup\ccmsetup\ccmsetup.cpp,4426) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Failed to parse '"C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ' with error 0x80004005 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='307' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
ParseCommandLine(), HRESULT=80004005
My boundaries and boundary groups are configured, I can see the objects in the Systems Management Container in AD, but still the agent install via WSUS will not work. Any suggestions?
Cheers
Sebastian Bammer

see my latest post. It looks like a bug in the setup. It selects a certificate but still it presents information that iis on the mp does not accept. Check your iis logs. Manual install works for ssl only sites. I haven't got any other methods yet. I will
keep you updated.

SCOM 2012 R2 Agent Deployment - Uninstall Old and Install New

By chance anyone come up with a scripted method for removing an existing SCOM 2012 SP1 agent and installing a new 2012 R2 agent? While I've come across a few scripts I'm trying to kill a few birds with one stone. This is a cross-domain attempt where the
SCOM servers sit in one domain and the member servers are scattered across multiple domains. Member servers range from Windows Server 2003, 2008, and 2012. In most cases the servers have the 2012 SP1 agent installed and in some cases there are multiple management
groups from previous SCOM standups. In addition there's a separate DEV SCOM 2012 R2 environment to manage DEV/QA servers. Active Directory Integration is configured and I have the necessary security groups created. There is a group policy created which is
filtered to just that security group. So the plan is to simply drop the servers into the correct group and have the agent installed via group policy start up script. ADI should have DEV servers appear in DEV SCOM and PROD in PROD SCOM.
Although there are ways to facilitate agent deployment via the console I need to perform a staged migration against a ton of server so as to not impact the existing production environment. So I'd rather do this remotely to pre-selected servers. This process
should involve removing the existing agent, installing the new one, and if possible removing any existing management groups. So far I've come up with the following:
Uninstall SCOM Agent:
%WinDir%\System32\msiexec.exe /x <path>\MOMAgent.msi /qb
Install SCOM Agent:
msiexec.exe /i \\path\Directory\MOMAgent.msi /qn /l*v \logs\MOMAgent_install.log USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=<MG_Name> MANAGEMENT_SERVER_DNS=<MSDNSName> ACTIONS_USE_COMPUTER_ACCOUNT=0 ACTIONSUSER=<AccountUser> ACTIONSDOMAIN=<AccountDomain>
ACTIONSPASSWORD=<AccountPassword>
Remove Management Group via Script
http://gallery.technet.microsoft.com/Remove-a-Management-group-336c849a/view/Discussions#content
I'm guessing this wheel has already been invented or maybe there's a better way. So I'm open to ideas or suggestions.
Any responses appreciated.

Wow! 4 days and no responses, not good Microsoft SCOM Community. So here's a status on this issue.
As stated I have Active Directory Integration configured which means:
I see the OperationsManager container in AD: dev_scom
I see the HealthService SCP and separate OU's for each of my management servers.
I have an ADI security group containing my management servers and scom action account.
I have an Agent security group which will contain servers the scom agent will be deployed via group policy.
I also have an AD LDAP query set to target the SCOM agent group.
(&(objectCategory=group)(name=DSCOM_ADI))
I finally get the script to install via the following steps:
Reference:
http://technet.microsoft.com/en-us/library/cc754995.aspx
http://technet.microsoft.com/en-us/library/cc770556.aspx
http://blog.coretech.dk/msk/install-a-scom-2012-agent-silent/
1. Launch Notepad ++ and enter the following:
msiexec /i
\\server.yourdomain.com\opsmgragent\%Processor_Architecture%\MOMAgent.msi USE_SETTINGS_FROM_AD=1 MANAGEMENT_GROUP=DEV_SCOM MANAGEMENT_SERVER_DNS=YourSCOMsrvr1.yourdomain.com ACTIONS_USE_COMPUTER_ACCOUNT=0 USE_MANUALLY_SPECIFIED_SETTINGS=0 ACTIONSUSER=svc_dscom
ACTIONSDOMAIN=yourdomain ACTIONSPASSWORD=YourPassword! AcceptEndUserLicenseAgreement=1 /qn /l*v c:\scom2012r2mmainstall.log
2. Save the script to a name of your choice. For me it's installdopsmgragent.cmd. Watch the extensions as you may end up saving it as installdopsmgragent.cmd.txt.
Note: Make note of this steps in the reference articles listed above:
"In the Add a Script dialog box, do the following:
In the Script Name box, type the path to the script, or click Browse to search for the script file in the Netlogon shared folder on the domain controller."
It's been a while since having to use a startup script so it took me a minute to figure this out. "getting too old 'fer this..."
3. Copy the script to the Netlogon folder which is located in the following directory on my Windows 2012 server: E:\SYSVOL\sysvol\yourdomain.com\scripts
4. Launch the group policy management console, create a new policy, edit it, and navigate to the following location:
Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown)
5. Double-click Startup to open the Startup Properties window.
6. Click Add and browse to the location of the script which you copied to the Netlogon share.
7. Click OK to close the Startup Properties window.
8. Close the Group Policy Management Editor.
9. Link the policy to an OU containing the servers.
10. Add the SCOM Agent group to the Security Filtering area of the group policy. I also remove Authenticated Users.
Note: make sure you have a few test servers in your Agent security group.
11. Drop to a command line and run gpupdate /force. You can also use gpupdate /force /sync but you will have to reboot the box you're running this from.
12. Log into one of the servers you have slated to deploy the agent to, drop to a command line, and run the same gpupdate command.
13. Follow this with a gpresult /r command to ensure that you see the policy applied in the Computer Settings area.
14. Reboot the server and you should see the startup script run.
15. Log into the server and launch the Control Panel.
16. If all went well you'll see the "Microsoft Monitoring Agent" icon.
17. Launch Event Viewer, navigate to the Operations Manager events node located under Applications and Services Logs and validate the logs.
17. If all didn't go well check the error log located, for me, on the C:\scom2012r2mmainstall.log
My issue: I don't see the management info in the Agent properties.
I installed this last night and waited until the next day still no changes. Event logs show the following:
Event ID: 2011 The Health Service did not find any policy in Active Directory
Event ID: 2003 No management groups were started. This may either be because no management groups are currently configured or a configured management group failed to start. The Health Service will wait for policy from Active Directory configuring
a management group to run.
I see the HealthService is Running in Task Manager on this server and of course I don't see anything listed in the Management Groups registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HealthService\Parameters\
I don't want to manually add the management group info. Checking as I may have missed something in one of the switches.
Any responses appreciated.

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

SCOM 2012 R2 agent upgrade fails crippling agents

Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
Keith

Hi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Three agent UR versions gets installed from gateway - SCOM 2012 SP1 UR4

Hi,
We have a SCOM 2012 SP1 UR4 installation with several gateways that servers connect to and get installation from.
We noticed that when the agent get installed on a client server it gets first the agent itself, then UR1, UR2 and last UR4.
From the XML-section in the task that has installed the agent one can read the following:
SoftwareUpdateInstalled KB2784734-amd64-Agent.msp;KB2826664-amd64-Agent.msp;KB2880799-amd64-Agent.msp; SoftwareUpdateInstalled
Below is from the application log of a newly installed server that got the agent installed.
The question I have is if this is correct? Why are all three UR installed?
Shouldn't it be enough with the latest version of UR? Are they not cumulative?
Can I simply delete the older versions in the agent directory of the Gateway?
Regards S-E
Windows Installer installed the product. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR1 Update Patch.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR2 Update Patch.
Installation success or error status: 0.
Windows Installer installed an update. Product Name: System Center 2012 - Operations Manager Agent.
Product Version: 7.0.9538.0. Product Language: 0. Manufacturer: Microsoft Corporation.
Update Name: System Center 2012 - Operations Manager SP1 UR4 Update Patch.
Installation success or error status: 0.
Windows Installer installed the product. Product Name: Active Directory Management Pack Helper Object.
Product Version: 1.1.0. Product Language: 1033. Manufacturer: Microsoft Corporation.
Installation success or error status: 0.

Hi,
This should be normal, as we can see in the below two articles. When applying Update Rollup 2, UR1 is listed there, and when applying Update Rollup 3, UR1 and UR2 is listed there also.
http://blogs.technet.com/b/kevinholman/archive/2013/04/11/applying-update-rollup-2-ur2-to-opsmgr-2012-sp1.aspx
http://blogs.technet.com/b/kevinholman/archive/2013/09/27/applying-update-rollup-3-ur3-to-opsmgr-2012-sp1.aspx
For example, UR3 can be applied to System Center Operations Manager 2012 SP1 (as released) or a SCOM 2012 SP1 deployment that has had UR1 or UR2 already applied.
Regards,
Yan Li
Regards, Yan Li

SCOM 2012 R2 Agent Issue: Error 25211.Failed to install performance counters.. Error Code: -2147024809

Hi All,
I'm trying to deploy SCOM 2012 R2 agent onto a domain controller and I get the following error "Product: Microsoft Monitoring Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.)."
I've installed the agent successfully onto 4 other domain controllers with out any issues.</p><p>The domain controllers are all VM's running on VMWare and are Windows Server 2012 R2.
I've rebuilt the Perfmon Counters based on this article: https://support.microsoft.com/en-us/kb/2554336?a=wsignin1.0
I've also enabled verbose logging on the msi installation:
InstallHSPerfCounters: Custom Action Data. C:\Program Files\Microsoft Monitoring Agent\Agent\
InstallHSPerfCounters: Installing agent perf counters.
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\HealthServiceCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. HealthService
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
InstallPerfCountersLib: Retry Count : .
InstallCounters: LoadPerfCounterTextStrings() failed . Error Code: 0x80070057. momv3 "C:\Program Files\Microsoft Monitoring Agent\Agent\MOMConnectorCounters.ini"
InstallPerfCountersHelper: pcCounterInstaller->InstallCounters() for the default counters failed. Error Code: 0x80070057. MOMConnector
InstallPerfCountersLib: InstallHealthServicePerfCounters() failed . Error Code: 0x80070057.
Any help on this would be great.

Hi Stefan,
I've successfully installed the agent. The server needed a reboot after fixing the corrupt perfmon counters.
I know have a issue with the agent on the domain controller. It kkeeps on greying out and have used hslockdown to allow the local system access by using the following command.
HSLockdown.exe "ManagementGroupName" /A "NT AUTHORITY\Authenticated Users"
Further digging into the issue I see in the SCOM Management Server the following error "The entity servername is not heartbeating"
Written a SQL query to gather more information. SQL query I used is:
SELECT
ME.FullName,
HSO.StartDateTime AS OutageStartDateTime,
DATEDIFF (DD, hso.StartDateTime, GETDATE()) AS OutageDays,
HSO.ReasonCode,
DS.Name AS ReasonString
FROM vManagedEntity AS ME
INNER JOIN vHealthServiceOutage AS HSO ON HSO.ManagedEntityRowId = ME.ManagedEntityRowId
INNER JOIN vStringResource AS SR ON HSO.ReasonCode =
REPLACE(LEFT(SR.StringResourceSystemName, LEN(SR.StringResourceSystemName)
– CHARINDEX(‘.’, REVERSE(SR.StringResourceSystemName))), ‘System.Availability.StateData.Reasons.’, ”)
INNER JOIN vDisplayString AS DS ON DS.ElementGuid = SR.StringResourceGuid
WHERE (SR.StringResourceSystemName LIKE ‘System.Availability.StateData.Reasons.[0-9]%’)
AND DS.LanguageCode = ‘ENU’
AND ME.FullName like ‘%SERVER NAME%’ –Change name here or leave %% for ALL SERVERS
ORDER BY OutageStartDateTime
This gives me the following reason behind the failure : "The heartbeat from System Center Management Service is missing."
Have I missed anything? The agent is running fine, however SCOM is reporting that the heartbeat is missing.
Any help on this would be great.

How SCOM Agent will get degraded which is installed on the monitored server while reverting Back from CU6 to CU3 of SCOM 2012 SP1?

Hi,
I have SCOM 2012 SP1 (CU3) inatalled on base server 2012 Standard which is a VM.
Now I am planning to Go for CU6 and thinking to take snapshot of complete SCOM server instead of taking Data Base Backup. Which should I prefer?
If i am going for the Snapshot for complete SCOM server and run the CU6 complete setup. And some thing went wrong and not able to fix the issue.
And I need to reverted back to CU3 using Snspshot.
Now, how can I revert the Agent Version to CU3 level which is already upgraded to CU6?
Thanks
Amit Raj

Hi,
all agents with CU6 will be work fine with SCOM CU6.
But if you decide back to the CU3 you need to backup your OPsDB and DWH (if CU6 contains sql scripts).
In regard agents you can use repair from OPsMGR console.

Issue upgrading SCOM 2012 SP1 to SCOM 2012 R2

I have been having a really fun time trying to get my test SCOM 2012 SP1 environment upgraded to SCOM 2012 R2. I initially had an issue with the DB server not accepting connections to SMB which was causing the upgrade to fail stating database permission
issues (that was a fun one to troubleshoot). Once I figured out that problem I am now getting an error in the OpsMgrSetupWizard log that is stating the following:
[14:46:47]: Always:
:LaunchMsiSetup: Complete: 2 seconds
[14:46:47]: Error:
:LaunchMsiSetup: Failed, return code: 1612
[14:46:47]: Error:
:Error:Failed to uninstall previous MOM product on this machine, cannot proceed with upgrade
[14:46:47]: Error:
:Error:Failed to uninstall Operations Manager Agent on this machine. This is fatal error, we cannot proceed with upgrade
[14:46:50]: Error:
:LaunchMSI: MSI E:\Setup\AMD64\Server\OMServer.msi returned error 1603
[14:46:50]: Error:
:ProcessInstalls: Install Item Management Server failed to install. We did not launch the post process delegate.
In the application log I am getting the following error:
"Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service
Manager is already installed. These must be uninstalled to proceed."
I have verified that I don't have any of these installed and have even gone so far as to remove my Config man agent and System Center Endpoint Protection just in case it was getting confused with System Center Essentials.
I am at a loss as to what to try next. Any suggestions?

Hi,
Check if you have the following registry. If so, please back it up first, then delete for a test.
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\C96403E8AD6025B4F9E1FE9C574E34AE
Also, please uninstall MOM product and Operations Manager Agent manually to check the result.
Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
http://technet.microsoft.com/en-us/library/dn249707.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Non supported version of SQL with new install of SCOM 2012 SP1

I have SQL 2012 SP1 running on Server 2012. I have tried the SCOM installation with and without CU2 (to fix the 1618 installation error)
SC VMM installed cleanly and appears to work.
The install for SCOM produces an error that says, "The installed version of SQL Server is not supported". I have not been able to find any log from the install that has that error in it.
Also, I have not been able to determine the true requirements of the SQL server for SCOM. (I found dock SCOM 2012 RTM and SQL 2008 R2, but noting for 2012 SP1.
Can someone point me to the correct place for the install log with (hopefully more information) and/or the requrements for the SQL installation?
Roy

The log is not created yet because it has not started the install.
The firewall is the most common issue indeed. Temporarily Disable the firewall and see whether you can continue.
Are you using a developers edition? The only 2 editions supported are standard and Enterprise.
The true requirements for SCOM 2012 sp1:
We recommend that you check for updates and hotfixes for SQL Server. Note the following database considerations for Operations Manager:
SQL Server 2008 R2 and SQL Server 2012 are available in both Standard and Enterprise editions. Operations Manager will function with both editions.
Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.
Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.
SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation
settings are supported.
The SQL Server Agent service must be started, and the startup type must be set to automatic.
Side-by-side installation of System Center Operations Manager 2007 R2 reporting and System Center 2012 Service Pack 1 (SP1), Operations Manager reporting on the same server is not supported.
The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start.
For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change
If you plan to use the Network Monitoring features of System Center 2012 – Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
tempdb Database.
Found here:
http://technet.microsoft.com/en-us/library/jj656654.aspx#BKMK_RBF_OperationsDatabase
It's doing common things uncommonly well that brings succes.

SCOM 2007 R2 to SCOM 2012 SP1 upgrade issues.

We have SCOM 2007 R2 on one of our development Environment.
The plan was to upgrade to SCOM 2012 R2 so we installed the SCOM 2007 R2 CU5.
We are having issues to upgrade now from SCOM 2007 R2 CU5 to SCOM 2012 SP1.
While upgrading we received the below message:
Unable to Proceed
Setup is unable to proceed with installation for the following reason:
At least one of the following application is installed on the computer.Due to incompatibility with system center 2012 - operations manager,these applications must be uninstalled.
-System Center 2012 - operations manager beta
-system center operations manager 2007
-system center operations manager 2007 sp1
--system center operations manager 2007 r2
-system center service manager agent
--system center essentials agent

Hi,
You cannot upgrade from SCOM2007R2 to SCOM2012SP1, you must upgrade to SCOM2012 and the upgrade to SCOM2012SP1
Cameron Fuller has a blog:
http://blogs.catapultsystems.com/cfuller/archive/2013/02/11/can-you-upgrade-from-opsmgr-2007-r2-to-opsmgr-2012-sp1-scom-sysctr.aspx
Upgrading System Center 2012 – Operations Manager to System Center 2012 SP1
http://technet.microsoft.com/en-us/library/jj899854.aspx
"The only supported upgrade path to System Center 2012 Service Pack 1 (SP1), Operations Manager is from System Center 2012 – Operations Manager. If you are upgrading from System Center Operations Manager 2007 R2, you must first upgrade to System Center 2012
– Operations Manager"
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

SCOM 2012 SP1 is failing to install - SQL not compatible

I'm getting an error when installing SCOM 2012 SP1 stating the SQL is not supported. I have seen a few posts on the forum about this error message but so far none of the resolutions resolved my issue.
Using named instance on port 2433. Entering SQL\instance and port 2433 yields same message as seen in another post:
"The installed version of SQL server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation. Please see the Supported Configurations document for further information."
I noticed I get this in my OpsMgrSetupWizard.log
[15:03:28]: Error: :StackTrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[15:03:28]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
Notice the last line - IsSQLOnAValidComputer is null/empty. The solutions I found are to open the ports between these servers but the SQL server and SCOM server are on the same network - no firewall between them. The registry key for domain firewall
policy to 'EnableFirewall' is 0. The firewall service is disabled on both machines.
I am running the installation as a domain service account - for the DAA. It has local admin on the SQL and SCOM server. It has sysadmin DB access to the instance.
SCOM Server:
Server 2008 R2 Standard SP1
SQL Server:
Server 2008 R2 Enterprise SP1 | SQL 2012 RM 64-bit version 11.0.2100.60
Any help is greatly appreciated.

Glad to hear the issue has been resolved. Thanks for the update.
Niki Han
TechNet Community Support

Installation of SCOM 2012 R2 with Orchestrator 2012 SP1 already installed

I'm new here and found this set up.
SCOM 2012 SP1 that was mis-installed badly. No DW, no Data Read or write account used. SPN's missing etc. Nothing is working on the SCOM Server. It's not connected to any other parts of System Center.
Orchestrator 2012 SP1 installed and seems to be working fine.
I know that I'm suppose to upgrade Orchestrator to R2 before upgrading SCOM 2012 to R2. But, I need to install SCOM 2012 R2 right now to ensure monitoring is in place. The question I have is can I install a fresh SCOM 2012 R2 and then go back and upgrade
Orchestrator to R2 or do I have to upgrade Orchestrator 2012 to R2 before I install the new SCOM 2012 R2?

Hi Bigredchief,
Yes, it's recommended by Microsoft to update the Orchestrator first and then SCOM.
Look at the diagram between SC components here:
http://social.technet.microsoft.com/wiki/contents/articles/13188.system-center-2012-integration-guide.aspx
and for Orchestrator here:
http://social.technet.microsoft.com/wiki/contents/articles/13185.system-center-2012-integration-guide-orchestrator.aspx
It’s clear visible from diagrams that SCOM monitors the Orchestrator by Management Pack and Orchestrator is connected to SCOM by Integration pack through Operations Manager SDK connection. The second link as well describes the integration between these 2
components of SC (see #5.3).
You should analyse your System Center components integration, and check if any Orchestrator runbooks communicate to SCOM. In general it will be 2 risk components in such upgrade (SCOM and then Orchestrator) in my opinion - not supported officially by MS
in case of any issues, and stopped working SCOM connected runbooks.
Natalya

SCOM 2012 SP1 Agent install issue

Similar Messages

Maybe you are looking for