SCOM 2012 Admin Kit

Is there a SCOM 2012 Admin kit that has the ability to test monitors that were created with Event IDs and Sources. It appears there was a feature in the SCOM 2007 Admin kit to do this. I can not find an Admin Kit for SCOM 2012.

I'm pretty sure the MP Event Analyzer from 2007 Admin Kit will still work exactly the same, since it doesn't actually require any SCOM component to work.

Similar Messages

  • SCOM 2012 Global Architecture, One management group or multiple?

    Hi Folks,
    I work for a global firm, we have multiple data caters in different regions. America, UK, Australia, China etc etc. We are looking to roll out SCOM 2012 for monitoring all systems. Our environment
    1,000 Windows servers
    All servers on the same Active Directory domain
    10 Mbps links between data centers.
    My question is around whether to use multiple management groups or one?   I’ve seen recommendations for both. For example
    In the Infrastructure Planning and Design guide for SCOM 2012 it is stated:
    “A centralized management model with large remote locations works best with a management group in each region and a local management group (which provides a consolidated view of alerts and status) in the parent location. In this case, the centralized management
    group connects through the software development kit (SDK) and functions as an additional console on each of the connected management groups.”
    However moderators in this forum have stated
    “Each management group has its own set of SQL Servers and Management Servers \ Gateways. It also adds considerably to administrative overhead. I'd try to avoid
    multiple management groups where possible.”
    ” It will get expensive in terms of hardware and software with multiple management groups and you will duplicate a lot of work with regards to overrides”
    “If you go with multiple Management Groups then you would need to add on a fair number of SQL licenses plus additional hardware. “
    “Presumably if I have multiple management groups will that mean I will have to
    create rules for each Management Group- correct. Same
    with overrides. It could add a lot of administrative overhead. “
    It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance. I’ve heard
    stories about SCOM deployments architected in this way not performing well because of network latency. i.e admins from all regions besides the region local to the SCOM deployment not wanting to use SCOM because application performance is too slow.
    What would the SCOM experts recommend for this scenario?
    MH

    1) My question is around whether to use multiple management groups or one?
    Factors to consider in determine the number of Management group
     • Scaling
     • Agents separated from their management server by WAN-speed network links
     • Political, administrative or security requirements within the organization requiring separate management groups.
     • A view of AD DS topology required across multiple forests.
     • A dedicated management group required for auditing purposes.
     • Disaster recovery functionality required.
     • Consolidated views of connected management groups required in Operations Manager.
     • Operations Manager integration with the VMM console.
     With refer to your situation
     a) 1,000 Windows servers
     b) All servers on the same Active Directory domain
     c) 10 Mbps links between data centers.
    It is suggest that one Management group is required.
    2) It would seem easier to just deploy one management group with the management servers in one datacenter but I’m concerned with performance
    It is recommend that you should deploy Gateway server in region office which has more than 10 agents.
    • Gateway server reduce network bandwidth utilization. Agents located across WAN links consume network bandwidth, potentially affecting service delivery to and from the remote location. A gateway server can consolidate the traffic.
    Roger

  • Manage DPM servers, running DPM jobs, etc from SCOM 2012 SP1

    Hi,
    Little background about our systems.
    We have a dedicated SCOM 2012.
    We have 22 DPM servers, DPM 2010 and DPM 2012 (we are upgrading to 2012 SP1, we have customers that still using Windows 2003 servers) to be managed by SCOM
    We have a few DPM servers that are not located on the same domain as the SCOM server (untrusted domain).
    Some problem we have
    1. When we try to manage the DPM servers from the SCOM server.
    From SCOM 2012 server I can “Manage DPM server” that are located in our domain but I cannot manage DPM servers located on untrusted domains (customer’s domains). I receive the below error message
    "Unable to connect to <untrusted domain DPM SERVER> ID: 948
    Verify that the DPM service is running on this computer"
    I guess it’s because the account that I’m using to run SCOM server located in our domain and does not have the permission to open the DPM console on the untrusted domain. So I wonder if it is possible to use “RUN AS profiles/accounts”
    to solve this issue, and how?
    2. I have installed SCOM 2012 Operations Manager Console on my computer and then installed DPM Central Console.
    When I select one dpm server (from my computer), that is on our domain, and then click “Manage DPM server” I got this error message
    "Unable to connect to <our domain DPM SERVER> ID: 33333
    1. Verify that the DPM service is running on this computer (YES)
    2. Verify that the current user has been added to at least one of the roles in Operations Manager. (YES)
    3. Open Operations Manage console and then try launching the DPM Console (THAT IS WHAT I AM TRYING TO DO)
    4. If you have re-imported the management pack recently, the role configuration may be corrupt. Open the DPM-specific roles and check if the roles have task assigned to them. If not, delete the roles and recreate the...."
    When I click on “Get more information” I get this error message.
    "You don´t have access permission to connect to the System Center Data Access service on <SCOM SERVER>. Please check if it is a permission issue".....
    Do you know why I cannot connect to any DPM server on our own domain?
    Why do I get access permission error on my computer but not on the SCOM server (using the same account)?
    What should we do to be able to connect to DPM servers that are on untrusted domain?
    3. Is it possible to see Last Recovery Point date/time in SCOM alerts?
    For me it is the first thing I look at. If it has failed 10 min ago it is not critical.
    But if it is a date and time more than 1 day old, then it is critical.
    I hope someone can help us with this
    Br
    SvBoho

    Hi,
    To manager DPM, I think we may need to add the account to local admin group of the DPM server.
    In addition, to connect to DPM the user needs permissions to DPM/SQL Server DPMDB.
    For your DCs, have your enabled agent proxy option? If not, please enable that option for all DCs.
    To monitor DPM with SCOM, please also go through the below links:
    http://kevingreeneitblog.blogspot.com/2011/10/managing-and-monitoring-system-center.html
    http://damatisystemcenter.com/2013/10/14/monitor-data-protection-manager-2012-using-scom-2012-sp1/
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Regards,
    Yan Li
    Regards, Yan Li

  • 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

  • Exchange 2013 SP1 and SCOM 2012 R2

    Hi there, 
    Hopefully someone can assist me with this issue, if it is one... 
    I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
    76 users in total, roughly 80GB of Public Folders.
    I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected. 
    Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues. 
    Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well. 
    Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010. 
    A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect. 
    Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy. 
    Attempted to reran the probe for EWS and got the error below:
    Is there perhaps anyone that can assist me with these errors?
    Cheers

    FYI... IIS ARR is not supported for Exchange Server.
    Check in event log if you are getting anything related to the issue.
    About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
    Are those mailboxes still moving or in move request?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Monitoring servers in SCOM 2012 via different locals within the same management group

    Hi,
    I have 2 management servers in a same management group. The 1st one is having English (US) locale while other is installed on Swedish locale. Both are accessed by different users having same admin rights.
    Once a USER 1 try to register a server through authoring tab from 1st management server(installed on English locale), a profile/group wrt the server registered is created successfully but the USER on 2nd management server (installed on Swedish locale) can
    not see the same in Authoring tab. He can view it in Monitoring tab as as well as Administration tab.
    The Vice versa is also true.
    Does any one have idea that is it SCOM 2012's expected behaviour wrt 2 2 different users on 2 different locales within a same management group ?
    Thanks in advance.

    Hi,
    I am a little confused, what do you mean by "register a server through authoring tab"?
    Do you mean that when you discover a server on 1st MS with discovery wizard then you cannot see it on 2nd MS(and the vice versa)?
    As far as I know, all those information should be stored in the operation database which is shared to both MSs within the same management group.
    We may use SQL query to find the discovered server on the operation database. Please also check operation manager event logs to get more information to troubleshoot this issue.
    Regards,
    Yan Li
    Regards, Yan Li

  • Errors installing SCOM 2012 Reporting Services

    I've run into an issue installing SCOM2012 Reporting Services, that I can't seem to figure out. I installed SQL Server 2008 R2 SP2 SSRS local to the SCOM server using an instance name of SCOM. I created the databases for this on another server (SQL server
    2008 R2 SP2) during the SSRS configuration. All from SSRS looks fine, and shows the scale out join, all good. I can browse to the reports page, add folders, all that normal stuff. I added the domain\datareader and datawriter accounts as SSRS admins in the
    site security, as well as ensured they are sysadmin in SQL, and local admins on the SQL and SCOM servers. So, all looks good. Until I go to add reporting services to SCOM 2012. It fails to complete, and the log shows:
    [12:28:36]: Warn: :Message:SRSPolicySetter SoapException Exception: System.Web.Services.Protocols.SoapException: An error occurred when invoking the authorization extension. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException:
    An error occurred when invoking the authorization extension. ---> System.ServiceModel.FaultException`1[[Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException, Microsoft.EnterpriseManagement.OperationsManager.Common, Version=7.0.5000.0,
    Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: The creator of this fault did not specify a Reason.
       at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.GetRoleProperties(String Name, Task[]& Tasks, String& Description)
       at Microsoft.ReportingServices.WebServer.ReportingService2005.GetRoleProperties(String Name, Task[]& Tasks, String& Description). Will retry..
    I then look in the SSRS logs, and see:
    library!ReportServer_0-1!89c!08/12/2013-12:28:34:: Call to GetRolePropertiesAction(Browser).
    library!ReportServer_0-1!89c!08/12/2013-12:28:36:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException: , Microsoft.ReportingServices.Diagnostics.Utilities.AuthorizationExtensionException: An error occurred when
    invoking the authorization extension. ---> System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to Microsoft.EnterpriseManagement.Common.UnauthorizedAccessMonitoringException:
    The user domain\DataReader does not have sufficient permission to perform the operation.).
    So, I'm at a loss. That user is a sysadmin in SQL, has been added to the SSRS security for site and folder with full permissions, has been added to the SSRS databases specifically, and is a local administrator on both the SSRS/SCOM server and the SQL server.
    What am I missing here folks? The SSRS is then completely hosed, and no longer works either. So, I have to uninstall and reinstall to even try again. This is getting frustrating.
    Please help! :)
    Thanks in advance,
    mpleaf

    After many google searches, and a lot of security changes, I think I found the right now that finally cured the issue. I had to add my datareader account to the Operations Manager Administrators in SCOM User Roles, and then it seemed to go through just fine.
    mpleaf

  • 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

  • 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

  • SQL server instance not getting detected during SCOM 2012 R2 Installation

    Hi All,
    This is related to the below thread which i created. But i wanted to test this practically in a LAB equipment
    https://social.technet.microsoft.com/Forums/en-US/96feece7-c168-4f42-b62e-4c0c20f8d525/does-scom-2012-2012-r2-setup-detect-a-sql-instance-of-a-sql-server-in-the-same-network-which-is-in?forum=operationsmanagerdeployment
    So i want to install SCOM in my domain, But i want to use a SQL server in my network which is in another domain.
    So i have 4 server machines as below:
    SERVER_DC1 - Domain controller of 1st domain.
    SERVER_DC2 - Domain controller of 2nd domain.
    SERVER_SQL - SQL server 2012 Enterprise installed for SCOM but is in Domain 1
    Server_SCOM - I want to install SCOM in this but which is in domain 2
    I created a trust relation between 2 domains with a Forest trust 2 way transitive.
    I have created a security group and added that as SQL Admin during the installation. Later i added one Domain administrator account from Domain 2 to this security group.
    When i do a installation in SERVER_DC1 for testing the SQL instance is being detected as below.
    When i do the installation in Server_SCOM which is in another domain then the instance is not getting detected.
    I have turned off windows firewall in all the machines.
    Before creating the trust i ran the setup in Server_SCOM then it was giving me a warning saying it is not able to access the SQL server due to permission issues.
    After giving permissions my instance is not at all getting detected.
    Can any one help plz.
    Gautam.75801

    Hi Yan Li,
    Really a helpful post. I tested the connection. I connected to the SQL server in Domain A using a server in domain B logged in as a domain B user to whom the SQL permissions are provided. The result says It was successful.
    Below is the screenshot.
    I don't understand why is it not getting detected in the SCOM setup.
    But 1 more important thing which i forgot to mention.
    When i log on to the server in which i want to install SCOM in domain B, But by using Domain A's user account (Added as a local user in SCOM server in domain B), Then the Instance is getting detected.
    Below is a screenshot of that.
    So has any one faced such a type of issue ?
    Gautam.75801

  • Deploy scom 2012 r2 on server 2012 r2

    Going to deploy scom 2012 r2 on server 2012 r2 with sql 2012 sp1. a few questions before starting:
    1. roles placement: server1 - management server, operation console;
                                 server2: database server, reporting server;
                                 Not sure where to place web console - server1 or server2?
    2. what are the least privileges to have for the installation account - domain user with local administrators?
        should the servers' system account need to be member of local administrators?
    3. what about other SCOM specific accounts? what least privileges they need?
    Thanks in advance.

    1. You can place it on the 1st server. do note however the downside doing all in one box SCOM components.
    2. It would be best to use a domain user account with local admin rights on the box
    3. Its all in the SCOM deployment docs..
    You might want to check this link
    http://blogs.technet.com/b/kevinholman/archive/2013/10/18/opsmgr-2012-r2-quickstart-deployment-guide.aspx (same as 
    Blake Mengotto)
    Hope this helps.
    Thanks,

  • SCOM 2012 - Additional Management Server - Database not Found (no errors)

    Hello,
    I am installing a second management server (SCOM 2012) and am running into an issue connecting to the existing database. 
    I selected Add a Management server to an existing management group.
    On the installer page Configuration/Configure the Operational Database, I enter the sql server name (fqdn) just as I did on the first management server (i took screenshots of the entire install so I could verify what I am
    doing). Then the installer takes over for a second to verify the server information.  There are no errors but the Database Name is blank, no choices in the drop down, nothing auto-populated.
    If I put an incorrect server name in there is an error (as is expected).  The port I am connecting on is the same one as the first management server: 1433.
    The servers are both running Windows Server 2008 R2 (64bit).  They were both created from the same template at the same time.
    I used the ODBC Data Source Administrator to test a connection to the SQL server from the Additional Management Server and the test completed successfully.
    I checked in the Operations Console to see if there was an entry in the Management Servers list for this second server and there is only the First management server listed there.
    Please let me know if you have any suggestions as to how I can see the database names when the server conneciton is not failing.  Thanks in advance.
    Zach

    Hi,
    Are the accounts permissions correct? Are you using the same account you used installing the first management server and is it a local admin on the 2nd management server?
    If all the above can be answered with yes please check if the 2nd management server is already known inside OpsMgr. If it is delete it from here and try again.
    You can also check the OpsMgrSetup.log for more detailed information.
    Your problem might be a known one:
    http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/25b05b2f-dd90-44e5-a5cb-c51c9e4944d2
    Hope this helps,

  • AD Integration: 1 Forest containing 2 Domains - Run Accounts/Profiles (SCOM 2012)

    I know there are plenty of threads on AD integration & Run As accounts\Profiles, but none quite answering my scenario...so here goes.
    1 Forest containing 2 domains -
    abc.com and
    def.com.
    abc.comcontains SCOM 2012 infrastructure (Mgmt Servers (MS1, MS2), Ops DB, Reporting DWDB).
    abc.com
    1. Created SCOM Admins
    Global Security group
    2. Created SCOM_MS_Action
    domain user account (used during SCOM setup & also Local Admin on all
    abc.com machines via Action Account AD group/GPO)
    3. Ran MomADAdmin.exe DEV-OPSMGR12 "abc\SCOM Admins" abc\SCOM_MS_Action abc.com
    (SCOM_MS_Action
    added to SCOM Admins group as a result)
    4. Created Auto Agent Assign
    rule for abc.com
    against MS1 for "servers", Run As Profile left as
    default setting.
    RESULT: All servers in abc.com
    populated MS_PrimarySG_xxx
    group as expected.
    def.com
    5. Created SCOM Admins
    Global Security group
    6. Created SCOM_AD_Assign
    domain user account 
    7. Ran MomADAdmin.exe DEV-OPSMGR12 "def\SCOM Admins" def\SCOM_AD_Assign def.com
    (SCOM_AD_Assign added to
    SCOM Admins group as a result)
    8. Created Run As Account (Windows) "def\SCOM_AD_Assign"
    Do I need to create this?
    9. Set "def\SCOM_AD_Assign"
    Run As account to "More Secure"
    Is"More Secure" correct, otherwise "Less Secure" causes errors on abc.com clients?
    10. Created Run As Profile "def AD Agent Discovery" & assigned to
    Default Management Pack
    Do I need to create a new Run As Profile?
    Was this the correct MP as when creating a new MP I got errors about it being unsealed when assigning to new Auto Agent Assign
    rule? I was under the impression never to use the Default MP?
    11. Associated "def\SCOM_AD_Assign" Run As account to "def AD Agent Discovery"
    Run As Profile, targetting "All Objects"
    Is this correct?
    12. Created Auto Agent Assign
    rule for def.com
    against MS1 for "servers", Run As Profile changed to "def AD Agent Discovery."
    RESULT: def.com contains OperationsManagement\DEV-OPSMGR12
    container but no MS_PrimarySG_xxx
    group exists?
    Do I need to add my Run As account to the "Active Directory Based Agent Assignment Account" Run As Profile as well as/instead of creating a Run As Profile? - and if so, do I target All Objects, Class, Group,
    Object?
    Thanks in advance - I find these Run As accounts very confusing when it comes to multiple domains!

    OK, solved this one myself. To answer my own questions :) this is what needed to be done (whether it's entirely correct or not is up for debate, however I ended up with the result I was after, so I am happy for now):
    def.com
    5. Created SCOM Admins
    Global Security group
    6. Created SCOM_AD_Assign
    domain user account
    7. Ran MomADAdmin.exe DEV-OPSMGR12 "def\SCOM Admins" def\SCOM_AD_Assign def.com
    (SCOM_AD_Assign added toSCOM Admins group as a result)
    8. Created Run As Account (Windows) "def\SCOM_AD_Assign"
    Do I need to create this? 
    YES
    9. Set "def\SCOM_AD_Assign"Run As account to
    "More Secure"
    Is "More Secure" correct, otherwise "Less Secure" causes errors on abc.com clients?
    YES, and added the Management Servers as "...the computers to which the credentials will be distributed"
    10. Created Run As Profile "def AD Agent Discovery" & assigned to
    Default Management Pack
    Do I need to create a new Run As Profile?
    YES
    Was this the correct MP as when creating a new MP I got errors about it being unsealed when assigning to new Auto Agent Assign rule? I was under the impression
    never to use the Default MP?
    Questionable, I did select the Default MP, otherwise the unsealed error occured when creating the Auto Agent Assign rule
    11. Associated "def\SCOM_AD_Assign" Run As account to "def AD Agent Discovery"
    Run As Profile, targeting "All Objects"
    Is this correct?
    NO, instead I targeted the Class "AD Assignment Resource Pool"
    12. Created Auto Agent Assign
    rule for def.com
    against MS1 for "servers", Run As Profile changed to "def AD Agent Discovery."
    Do I need to add my Run As account to the "Active Directory Based Agent Assignment Account" Run As Profile as well as/instead of creating a Run As Profile? - and if so, do I target All Objects, Class, Group, Object?
    NO, otherwise alerts appear in regards to abc.com discovery rules breaking. Looks like for additional domains this rule should not be touched.
    RESULT: All servers in def.com
    populated MS_PrimarySG_xxx
    group as expected
    Note: Domain Controllers should not be included in the Auto Assign rules supposedly (makes sense) so I altered the query to ensure they didn't populate in the
    MS_PrimarySG_xxx group:
    (&(sAMAccountType=805306369)(objectCategory=computer)(objectClass=computer)(operatingSystem=*Server*)) (!(primaryGroupID=516))
     (!(primaryGroupID=516)) equates to exclude DCs.
    Hope this helps others
    Steve

  • Audit collection services SCOM 2012 SP1

    Hi all,
    sorry for my englich . I have trouble with ACS . I set in the DC audit logs :
    http://www.techrepublic.com/blog/data-center/reporting-on-security-with-microsoft-audit-collection-services/.
    After this I try look to report Domain and Bultin administrators membwrschip changes . But the report is empty after i try change domain admins groups....
    And second questation :
    what mean report usage_sensitive security groups changes ? 
    thank you .....
    Falcon

    Hi,
    You may first check your secutiry logs to make sure those membership change event is generated.
    In addition, did you follow the link below when deploying ACS:
    http://blogs.technet.com/b/fesiro/archive/2013/01/08/how-to-deploy-audit-collection-services-acs-in-scom-2012.aspx
    Hope the article below can be helpful for you:
    http://scomandplus.blogspot.ca/2012/08/error-in-scom-2012-acs-report-sensitive.html
    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 The evaluation period for this product has expired. Please obtain a full version of this product.

    Hi
    I have a problem with expiration of SCOM 2012 R2, it's in the following state:
    i already trided activate it again and restart server but without success.

    Hi There,
    Faizan is correct. Seems there is some connectivity issue but the strange thing is that if your SCOM is not able to connect to the ops DB then the operations console will not at all open.
    Also Bllitz  - 
    Where is this SQL server located ? Same domain or remote domain ? Is the SCOM Action account added as local admin in the SQL & SCOM server ?
    What about the data reader and writer account ?
    Also Run the below tasks which can give some light on this issue.
    Go to Monitoring - > Operations manager - > Management server state and click on the MS and click on the tasks button on the top and Run the Failed Rules task and see the count how many rules / workflows have failed ? It should ideally
    be Zero. 
    If it is not zero Unhide the contents and paste it here.
    Post me the results.
    Gautam.75801

Maybe you are looking for