O365 SCOM 2012 requirements

hi,
I have recently tried to install the O365 Management Pack on our SCOM 2012 Mgmt Server. I ran into the following requirements:
O365 MP needs:
System Center Core Library / Microsoft.SystemCenter.Library 7.0.8432.0, currently 7.0.8427.0
Health Library / System.Health.Library 7.0.8432.0, currently 7.0.8427.0
Microsoft.SystemCenter.Visualization.Library / Microsoft.SystemCenter.Visualization.Library 7.0.9538.0, currently 7.0.8560
Unfortunately, our current libraries are not at the level of the requirements. How/where can I get the required MPs ? I thought O365 supports SCOM 2012!
dave

Hi,
Office 365 management pack:
Supported Operating System
Windows Server 2012 R2
The Office 365 Management Pack for Operations Manager is designed for the following versions of System Center Operations Manager: • System Center
Operations Manager 2012 • System Center Operations Manager 2012 SP1 • System Center Operations Manager 2012 R2
More details:
http://www.microsoft.com/en-us/download/details.aspx?id=43708
As we can see the management pack require Windows Server 2012 R2. Did your environment meet this requirement?
Regards,
Yan Li
Regards, Yan Li

Similar Messages

SCOM 2012 R2 Hardware Requirements

Hi,
I am trying to work out what specification machines to use for a deployment of SCOM 2012 R2. I have searched on this forum, online generally and used the sizing guide but its all a bit vague. The sizing guide spat out the result below but as you can see
it makes no mention of CPU speeds or server HDD space apart from the DW server which says 300GB. The sizing wizard also spat out 14.43GB for the Ops DB and 427.45GB for the DW DB based on managing 600 servers, no network devices or applications.
Minimum Hardware Recommendation:
Role: (Total: 2) (1) management server managing up to 1000 agents, plus (1) management server for HA, managing up to 10 SDK users total
Hardware:
• 4 disk RAID 10
• 16 GB RAM
• 4 Cores
Role: Operations Database Server
Hardware:
• 6 disk RAID 10 (Data)
• 2 disk RAID 1 (Log)
• 16 GB RAM
• 4 Cores
Role: Operations Data Warehouse Server
Hardware:
• 12 disk RAID 10 (Data) (300 GB)
• 2 disk RAID 1 (Log)
• 16 GB RAM
• 4 Cores
Role: Web Console Server & SQL Server Reporting Services Server
Hardware:
• 2 disk RAID 1
• 8 GB RAM
• 4 Cores
I have also seen in the documentation that the management servers only require 1024MB of free space on the System Drive, that seems a bit overkill to have that spread across 4 disks at RAID 10. With regards to the DW disk requirements does it really need
300GB on 12 disk RAID 10 plus the 427.45GB for the Data Warehouse?
If someone could possibly clear this up I would be extremely grateful.
S

Your 4 cores CPU have met the requirement. SCOM does not use CPU resource much.
Juke Chou
TechNet Community Support

SCOM 2012 R2 - How to create a Web Application Monitor for an URL requiring certificate authentication

Hi All,
It looks like in SCOM 2012 there are two ways to monitor a web application (URL monitoring):
Way no 1: (Using the Web Application Transaction Monitoring template)
Way no 2: (Using the Web
Application Availability Monitoring template)
We have created some monitors using
Web Application Availability Monitoring to check if URL is up without any authentication method.
However, we have few URLs for which we need Client Certificates to be used for accessing them but found no option in SCOM 2012 to configured the certificates.
I have searched a lot on the Tech Net library but no clue. Does anyone know how to successfully monitor an URL requiring certificate authentication on SCOM 2012 ? or, at least, using no matter which method?
Thanks.
Regards,
Raju.

Hi,
Based on my research, it is not possible by using the built-in monitoring templates. Both of them handles “normal”, server-side, SSL-certs, and the transaction monitor handles basic/digest/NTLM authentication, but client certificate based authentication
is not a configurable option.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM 2012 R2 Domain Functional Requirement

Hi
We are planning to deploy SCOM 2012 R2 in our environment. We are running Windows 2012 AD and have Domain and Forest functional levels of
Windows Server 2012 R2. The Environmental prerequisites stated on Technet article
http://technet.microsoft.com/en-us/library/hh487285.aspx under section "Domain Functional Level", following description is provided:
Windows Server Active Directory can operate at different functional levels. These levels are distinguished by the version of the Windows Server operating system that is permitted on the domain controllers present in the domain. System Center 2012 – Operations
Manager requires that the domain functional level be Windows 2000 native, Windows Server 2003 interim, Windows Server 2003, or Windows Server 2008. The domain functional level of Windows Server 2008 R2 is also supported (for the SP1 version of System Center
2012 – Operations Manager, Windows Server 2008 R2 SP1 and Windows Server 2012 are supported). For System Center 2012 – Operations Manager to function properly, you must check the domain functional level and raise it to the appropriate version.
This description does not includes Domain Functional Level of Windows Server 2012 R2.
Does SCOM 2012 R2 supports domain and forest functional levels of Windows Server 2012 R2?
Thanks
Taranjeet Singh
zamn

Yes.
I has a SCOM 2012 R2 deploy in domain with forest and domain functional levels of Windows Server 2012 R2 and it work fine. Moreover, SCOM monitoring is more depend on kerberos encrpytion of data transfer rather than functional level.
Roger

SQL version could not be verified error while installing the SCOM 2012 R2 reporting component

I have the below SCOM server roles in my SCOM 2012 R2 set up
1) All servers with Windows Server 2008 R2 SP1, MS - SCOM1, DB & DW - DB1, Reporting Server - DB2
2) All the DB servers with SQL 2012 SP1
3) Windows firewall is turned off on all the servers.
4) Success fully installed all the components except SCOM reporting.
While installing the SCOM 2012 R2 reporting component on DB2 ( Iam running this set up on the server where I instllaed the SQL DB engine and reportin services in Native mode. Configured the SQL reporting database and reporting URLs successfully in SQL reporting
configuration manager) getting the below error in the Rporting server instance page. Kindly advise.
I ran mofcomp.exe and there is no firewall restrictions. My account also has DB owner & sysadmin permissions.
Also tried re installing the SQL on Reporting server.
"The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information".

Hi,
As far as I know, after installing SSRS, we don't need to configure the database and reporting URLs manully. When we install the reporting service for SCOM, it will configure those automatically.
If possible, you may re-install SSRS and then install SCOM reporting service.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

Hi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li

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.

Logical Disk space on a virtual Computer (not a Server) in SCOM 2012

Hello all-
   I have a sort of unique situation for our SCOM environment. We are already doing logical disk space monitoring on all of our SERVERS with no issues. Now we have one user who requires monitoring on their computer. This is really
a virtual workstation, as opposed to a real computer.   Since it's virtual, it's really online all the time.    Whether its right or wrong, they are using this virtual workstation sort of as a server. Anyway, they want me to
monitor the disk space for the C drive on this virtual computer. I'm having difficulty setting up such a monitor on a computer like that...
I got the SCOM agent installed onto the computer. SCOM is reporting it as being "Healthy".   Now how can I define a logical disk space monitor for it?   I attempt to create a monitor:   Windows Performance Counters,
Static Thresholds, Single Threshold. Then how can I direct the monitor at the C drive on the computer? I have to fill in the Object, Counter and Instanace. Normally I would click on the
Select button, then I would type in the server name and hit Enter and it would bring up all the objects it will allow me to monitor. Unfortunately it doesn't let me type in the computer name and hit enter in the same way. When I
do so, it says "The network path was not found". If I click on the
... button next to the Computer field, it brings me to a Select Computer screen. In here, I am type in the computer name and then I click
Check Name and it does appear to find it, and it underlines the computer's name.    So I then click
OK to bring me back to the previous screen where it presents me with the same "The network path was not found" error immediately. So I can't seem to navigate to the computer in SCOM and select the C drive, as I would be able
to for a server.
I tried to sort of force it in, instead of browsing for the computer and selecting the C drive. I simply put
LogicalDisk in for the Object then Free Megabytes for the Counter, then
C: for the Instance (as shown in the attached screen print.
Then I just applied my new rule to the computer via SCOM. I don't get any error messages when setting it up that way, but it certainly doesn't work.
So with all that said, can anyone help me out setting up a logical disk space monitoring for a COMPUTER in SCOM 2012 SP1 please? Please let me know if you need any more information!

Thanks, that would probably do it, I'm going to keep that as my backup plan. However, my current feeling is that it might be a bit overkill to install a whole management pack, when all I want to do is monitor a single C drive on a single workstation.
The rest of the monitors in the management pack I wouldn't have any interest it.   Let me ask you a question maybe you will know the answer to... Shouldn't I be able to monitor that drive even without that management pack installed?   I
mean some combination of settings for the Logical Disk Space rule in that management pack works for computers/workstations. Shouldn't I be able to reproduce that one single rule without the management pack? Does anyone have that management pack
installed? Could you possibly look at the Client OS Logical Disk Space rule and send me some screen shots or something?   Or am I missing something? Is the management pack needed for other reasons in order to monitor this?

SCOM 2012 R2 System Performance Report issue

Dear All,
We have SCOM 2012 R2 with SQL Server 2012.
For last few days we are stucked with SCOM System Performance Report. We are trying to achieve following:
Generate a report of last 15 days of all the following components in a single report.
Get Memory Utilization of a Particular Server in Line Chart form with Horizontal counter showing 0 to 100% Utilization and vertical couter showing Time line. Also showing total Memory of the server.
Get Processor Utilization report of a Particular Server in Line Chart form with Horizontal counter showing 0 to 100% Utilization and vertical couter showing Time line. Also showing process installed on the server.
Get Disk Time report with (I/O) MB / Sec in Line Chart form.
I have tried creating a sample with photo editor to provide you better understanding of my requirement.
We can go for customizing reports with Report builder or any other tool which can help us achieve this task. Need your suggestion for the above.
Thanks
VN

1) open the url http://reportserver/reports where reportserver is your report server
2) navigate the folder Microsoft.systemCenter.Datawarehouse.Report.library
3) click the arrow of report Microsoft.SystemCenter.Datawarehouse.Report.Performance and select download
4) repeat setp 3) for Microsoft.SystemCenter.Datawarehouse.Report.Performance.rpdl
5) rename its file name and upload its into the folder Microsoft.systemCenter.Datawarehouse.Report.library
6) click the arrow of report which you upload on step 5) and select manage
7) update its DataWarehousMain --> A shared data source as /Data Warehouse Main
8) update Custom data source as Credentials are not required and click Apply
9) click the arrow of report which you upload on step 5) and select Edit in Report Builder
10) right click the unwanted part and delete
Roger

SCOM 2012 R2 HA design but using SQL 2014 Standard edition

Hi All,
I want to deploy SCOM 2012r2 with a HA design (but have constraints!)
Plan is two management servers with all roles to each (fresh deployment so 2012r2 RU5)
SQL servers need to be 2014 standard edition due to licensing and cost constraints.
Design is to be split between two datacentres that are fibre connected and sub 3ms latency
Plan was to have a Management Server and a SQL server at each location.
Each location has a dedicated SAN but SAN replication is not an option.
What are my SQL options for the DB??
AlwaysOn FCI is not preferable as it gives a single point of failure due to shared storage requirement.
I read Database mirroring is not a supported config but this isn't Microsoft direct info just blog post, is this correct.
Which leaves me with log shipping, is this supported and the best option??
Would be great to get advice on what works well in the field with a contraint of having to use SQL Standard edition!
Thanks
James

Hi,
No additional licenses are needed for management servers or SQL Server technology.
System Center 2012 R2 licensing
http://www.microsoft.com/en-us/Licensing/product-licensing/system-center-2012-r2.aspx#tab=2
Reference:
SCOM 2012 R2 HA options with Server 2012 and SQL 2012
https://gallery.technet.microsoft.com/SCOM-2012-R2-HA-options-540beb95
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Performance of Network Monitoring in SCOM 2012 SP1

Hi all!
I´ve problems with performance of the network monitoring feature in SCOM 2012 SP1.
According to the
guide the following should be adeqate:
•1000 network devices (approximately 12,500 monitored ports) managed by a resource pool that has three or more management servers
•500 network devices (approximately 6,250 monitored ports) managed by a resource pool that has two or more gateway servers
We have 800 network devices with a total of 24000 ports,
BUT only 1500 of them are monitored. This is basically what happens automatically after discovery, since only ports between monitored devices are monitored by default.
For this setup I first used only one management server dedicated to the Network Pool,
based on my assumption that if two servers could monitor 6250 ports, one server would be more than enough for 1500. I found this configuration working very poorly so I added another server. I now have two servers
dedicated for the Network Resource Pool. (They are NOT members of the “All management servers resource pool”)
Still, I get constant alerts regarding Health Services Private Bytes on these servers. They vary between 1-2Gbytes. Furthermore, if one of the servers goes offline, the network devices that was monitored by that server becomes grey for
several hours. Even if the server only is rebooted it takes forever to get everything online and green again.
I don´t really know what I should do now. I had a plan to replace our current network monitoring system (SNMPc) which easily handles this load on only one server. They are of course completely different beasts, but still. SCOM seems to
require a massive back-end to produce equivalent real life results.
Any suggestions or reflections from the field are highly appreciated!
Regards
Peter

Hi,
Try to overide the monitor Health Services Private Bytes by the following steps.
◾Go Authoring space – Management Pack Objects – Monitors
◾Go to change scope – select clear all – look for Health Service – tick it and press OK.
◾Expand Health Service – expand Entity Health – expand Performance – expand Health Service Performance
◾Select the Health Health Service Private Bytes Threshold.
◾Right click the mouse and choose to overide the monitor for a group
◾Select the group called Management Server Computer Group and press OK
◾Select the Agent Performance Monitor Type – Threshold and change the value 104857600 to ex. 2610612736.
◾Select to store the overide in a management pack you have created and press OK
Juke Chou
TechNet Community Support

SCOM 2012 R2 installtion wizard not able to contact SQL server cluster

Hi,
This is about the error faced while installing SCOM 2012 R2.
My customer has SQL 2012 SP1 cluster installed. I am trying to install the SCOM 2012 R2 with this installed SQL cluster. The SQL cluster is installed with default instance and with AAG (Always on Availability Group).
The edition of SQL server is, SQL Server Enterprise edition with SP1
After check services on both the SQL nodes found that SQL Full text is not installed (as the related SQL Full text service not present in the services.msc) on any of the SQL cluster node & SQL Browser service is not running.
The running services for SQL are, SQL Server (MSSQLSERVER) & SQL Server Agent (MSSQLSERVER).
When I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, This SQL Server could not be found.
After installed SQL full text, the service is showing in services.msc as "SQL Full-text Filter Daemon Launcher (MSSQLSERVER)".
Now when I started to install the SCOM 2012 R2, Within a SCOM 2012 wizard, On the Configure the Operational Database screen, entered only the name of SQL cluster & no instance as it is with default instance MSSQLSERVER.
I faced error as, The installed version of SQL Server could not be verified or is not supported.
Followings test carried out for the connectivity between SCOM 2012 MS &SQL Cluster
Ping SQL Cluster successfully
Telnet SQL Cluster for port 1433 successfully
Tracert SQL Cluster – completed successfully with single hops.
The windows firewall is off on both sides
The SQL services running on the Active node 1 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Running & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL services running on the Passive node 2 of the cluster are as follows:
SQL Full Text Filter Daemon Launcher (MSSQLSERVER) -- Running & Manual
SQL Server (MSSQLSERVER) -- Running & Automatic
SQL Server Agent (MSSQLSERVER) -- Stopped & Automatic
SQL serve Browser - Stopped & Manual
SQL Server VSS Writer -- Running & Automatic
The SQL Server Agent (MSSQLSERVER) service is not running on the second node. It is running only on first node which is active.
The account used to install SCOM has the local admin privilege on the SQL server
To ping the cluster use the cluster name & it solved the whole FQDN of cluster in ping result. When ping with IP address with -a it not resolve to name.
Is any one can provide their valuable inputs.
Regards,
SandeepK

Hi SandeepK,
Before Installing Operations Manager on an availability group, please
1. Make sure to use the Group listener Name and port when installing Operations Manager for the databases that are going to be added to the availability databases.
2. The first management server will use the Group listener to get the primary SQL instance, and will install the databases on that instance.
System Requirements: System Center 2012 R2 Operations Manager
http://technet.microsoft.com/en-us/library/dn249696.aspx#BKMK_ClusterConfig
Niki Han
TechNet Community Support

Which type of SQL DB do I need for SCOM 2012?

Hello everyone,
We would like to install a SCOM 2012 Server for reporting and alerting of our Exchange and Lync Server.
Our guys from database management asks me, what type of SQL DB do I need. "An SQL DB with 100GB" shouldn't be enough :-( I'm not very familiar with SQL.
So, which informations could be missing?
Thanks in advance and best regards
Daniel
Beste Grüße

Daniel,
usually Standard Edition is enough and included in the SCOM (agent) license.
Here you find more about requirements:
https://technet.microsoft.com/en-us/library/dn249696.aspx
SQL specific:
Check for updates and hotfixes for Microsoft SQL Server. See
SQL Server in System Center 2012 R2.
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.
For SQL Server collation settings, see
SQL Server in System Center 2012 R2
The SQL Server Agent service must be started, and the startup type must be set to automatic.
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 R2 Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see
tempdb Database.
You should have a look at the sizing calculator:
http://download.microsoft.com/download/C/A/6/CA60425C-950B-456E-986C-C5F2FCD5668D/System%20Center%202012%20Operations%20Manager%20Sizing%20Helper%20Tool%20v1.xls
Good luck,
Patrick
Please remember to click “Mark as Answer” on the post that helped you.
Patrick Seidl (System Center and Private Cloud)
Website: http://www.syliance.com
Blog: http://www.systemcenterrocks.com

SSRS for SCOM 2012 need separate instance of SQL

Hi All,
My customer has planned to install SCOM 2012 R2 in their environment. I designed for them as followings:
Planned 3 MS servers namely, MS1, MS2 & MS3
The rolls planned on those MS servers as follows:
MS1 – Management Server,
Operation console & Web console
MS2 – Management Server,
Operation console & Web console
MS3 – Management Server,
ACS, SQL Reporting services & SCOM Reporting server
Customer has their existing SQL cluster database configured. This existing SQL database is also utilized by other applications.
I am planning to keep all the SCOM databases (Operation Manager DB, Operation DW DB, Reporting DB & ACS DB) on the central location on SAN storage of the SQL cluster.
For this, I requested to customer for a new instance of SQL to install SCOM DBs & SQL Server Reporting services.
Customer raised a concern on Why would need to install the databases & SQL Server Reporting services on a separate instance.
I replied as, The new instance requested will host the databases along with the SQL Server reporting services (SSRS).
The installation of SQL server report server will integrate the security of selected SSRS instance with Operation Manager role based security. Any reports that were previously installed on this
SQL server instance might become inaccessible. No other applications that are using SQL Server Reporting Services can be installed on this instance of SQL Server.
On this, Customer says if SSRS is planning to install on the MS3 server then there would not need to create a separate instance on SQL cluster. We can go with the existing instance for installation
of SCOM databases on SQL cluster and SSRS on MS3 server.
I need your inputs on this, as can I still require the new instance of SQL on SQL cluster or can go with the existing instance for installation of SCOM databases on SQL cluster and SSRS on MS3 server.
Kindly provide your inputs.
Regards,
SandeepK

Although SCOM can share a single instance running SQL Server to store data, this is not a recommended configuration. The SSRS is the same, no document says that it can be shared with others.
Also, refer to
http://social.technet.microsoft.com/Forums/en-US/84e89021-6794-421e-b41c-5da1186aae2e/sccm-and-scom-reporting-on-the-same-sql-instance?forum=configmgrreporting
Juke Chou
TechNet Community Support

How to use the SCOM 2012 Web Reporting page

Hello all-
   We are on SCOM 2012 SP1. I just have a general question about reporting. I know there is a "Reporting" tab in the real, locally installed, SCOM Operations Console software. That part I get. I see that there
are many pre-made reports the for me to run. For example under Microsoft Server 2008 Operating System (Monitoring) folder there is a
Performance History report. When I double click on it, it takes me to the report window where I can click
Add Object and add a server and then click
Run.
This is pretty simple in concept.   BUT very few people at my company have the full Operations Console installed on their machine. And as I'm sure you know, the SCOM Web Console does not have a Reporting Tab. So they have to use the
SCOM Reporting website to run such reports. I found that you can get to this page at the url:
http://<reporting server>/Reports
This does bring up the Reporting console. On the list I do see a Report.Windows.Server.2008.PerformanceHistory listed. So this surely seems to be the equivalent from my screenshot above.   However, it's not even close to user friendly like
the Reporting area in the SCOM operations console software. There's multiple fields at the top. All of which are required, and almost none of which have dropbox or other ways to help you fill them in. I have no idea what to put into these boxes or the format
to use.
What am I missing here? Is there a more user friendly interface anywhere? In an ideal world, I'd really love to have a user interface where I can post the links to a few popular reports, like CPU and Disk Space for example. Then ideally
all the user would have to do is select their servers and the time frame and that's all.   Which really is what you do in the Operations Console software.   So isn't is it that easy in the web reporting tool? Is there a guide or how-to
section somewhere I'm missing? Or just a more friendly looking way to get at this information?

Well, my first screen shot above is squished, so you really can't see it. But what I'm saying is that the same report in the SCOM software has the level of configuration I want on it.   It allows you to pick the date range and add objects
to it, then you can click on Run.     However when I access the same report on the reporting console, it has all these extra fields. None of which I know how to fill in properly.
I would ultimately like my customers to be able to do exactly that in the web version. Pick their server and their date range and run it.   There are not likely going to be too many reports like you're mentioning which I can completely configure
before hand, so they just click on the link to have it run. Most times I'd like my users to at least be able to select a server name.
Any idea how I would simplify the web version of the report? Or why they look so very different?

O365 SCOM 2012 requirements

Similar Messages

Maybe you are looking for