Maps SCOM 2012

Hello Guys
I have installed SCOM 2012 R2 and I need to map the monitored servers but no license sharepoint enterprise to create with Visio pluging monitoring views.
I've already posted dashboard in SharePoint but I have not found another way to create a similar topology to what can be achieved with Visio.
I would like your help to know if there is another way to create topologies (maps) and be published by example in html o in sharepoint.
Regards
SAN

No, you will need to create Maps for SCOM 2012 R2 by Dashboards. you can't do it through SharePoint by .html
http://blogs.technet.com/b/momteam/archive/2012/05/31/using-the-web-application-availability-monitoring-to-monitor-web-applications-health.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
Technical | Twitter:
Mai Ali

Similar Messages

  • SCOM 2012 Service Level Dashboard

    I have been tasked with creating a Service level dashboard for SCOM 2012. After reading up on various blogs and sites around methods and BI / reporting tools I am no closer to knowing what would be the best solution, and would appreciate some guidance.
    I want to create SLO groups for applications - Exchange, AD, SQL, SCCM etc. and have a high level heat map with measures like CPU util, Disk space %, latency etc. updated every minute and displayed in each block (preferably using corners of a single block),
    and if possible to add a bootstrap style icon into each block.
    I would like drill down functionality on each group that then breaks down into another heatmap (per server).
    And then to drill down further which displays a SLD type dashboard on that instance.
    I am comfortable with creating the final level SLD using widgets, would it be possible to use Visio for the heatmaps ?
    I have looked into using Power View, would conditional formatting be a better option ? 
    Id like to publish the dashboard into Sharepoint.
    Would appreciate your feedback. Once i know which solution to look into, it would become much easier to focus my attention.

    Hi,
    I would like to suggest you refer to the articles below:
    Creating a Service Level Dashboard
    http://technet.microsoft.com/en-us/library/hh212692.aspx
    Monitoring Service Level Objectives by Using Operations Manager
    http://technet.microsoft.com/en-us/library/hh212753.aspx
    For more information on the Visio 2010, Sharepoint 2010 and Savision LiveMaps
    solutions, see the excellent blog series by SCOM MVP Marnix Wolf from the link
    below:
    http://thoughtsonopsmgr.blogspot.com/2010/09/scom-and-dashboards.html
    Regards,
    Yan Li
    Regards, Yan Li

  • General hardware monitoring on SCOM 2012 R2

    Hello everybody. Sorry for maybe common question, i'm absolutely newbie in SCOM. I'm standing at task of monitoring basic servers counters - Memory utilization, disk free space & CPU utilization. After reading some articles about SCOM architecture I
    get a little frustrated - cannot get full understanding about monitoring mechanisms. What I want from my monitors:
    - Monitor 2,3...N groups of servers with _different_ disk free space thresholds and sending alerts (email) to specific people.
    I've already have imported management pack for Windows OS, configure channels & subscribers.
    I get a lot of question trying to configure such monitoring, maybe you can help me (or send me to manuals)
    1. I can use monitor's for specific OS (i.e. logical disk free space), then I need to override it(why? I can't use it?) and select servers.
    2. How can I map a group of servers to monitor?
    3. Do I need rules?
    4. New monitor sets in installed agents automatically?
    Cannot understand steps, in which I should resolve my task..

    1. Windows OS management pack has default monitor for disk free space and CPU utilization. If you 2,3,...N groups of servers with different disk free space thresholds, you should create Groups which contains the required servers and using override with target
    of the gorups.
    For how to create an override, pls. refer
    http://jimmoldenhauer.blogspot.hk/2012/11/scom-2012-creating-overides.html
    2. The target of the monitor is set to the groups of server
    3. It depend on situation
    Rules do not affect the health state of the target object. They are used for one of three functions
    a) Alerting Rules
    Alerting rules create an alert when a particular event is detected. This can be any of the different kinds of events shown in Data Sources. Alerting rules do not affect health state.
    b) Collection Rules
    Collection rules collect events or performance data to the Operations Manager database and data warehouse. They do not create alerts or set health state.
    Collection rules can use each of the data sources shown in Data Sources. The data will be converted to either an event or to performance data depending on the particular kind of collection rule you are creating. For some wizards, you will need to provide
    the specific information from the data source that will be used for different properties of the data being collected.
    c) Command Rules
    Command rules will run a script or command on a schedule. They do not create alerts or collect any data.
    4) All agents will automatic download updated its monitor and rule which applicable to the server.
    Roger

  • The problem with forecast reports in SCOM 2012 after integration with VMM 2012

    Hello.
    I have problem with forecast reports in SCOM 2012 after integration with VMM 2012. All other reports (not forecasting) works fine. For example, report “Host Group Forecasting” don’t work. The report is generated, but I have error: “Subreport
    could not be shown”. I find only errors in SQL Server Reporting logs like this:
    library!ReportServer_0-13!1758!06/26/2012-18:26:23:: i INFO: RenderForNewSession('/Microsoft.SystemCenter.VirtualMachineManager.2012.Reports/Microsoft.SystemCenter.VirtualMachineManager.2012.Report.ForecastHostGroup')
    processing!ReportServer_0-13!1758!06/26/2012-18:26:28:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Не удалось выполнить
    запрос для набора данных "DiskSpaceUsageForecasting". ---> Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Execution of the managed stored procedure GetTimeSeriesForecast failed with the following error: Exception has been thrown by
    the target of an invocation..
    Query (5, 58) Parser: The syntax for '6' is incorrect.
       at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteTabular(CommandBehavior behavior, ICommandContentProvider contentProvider,
    AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
       at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteReader(CommandBehavior behavior)
       at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
       at Microsoft.ReportingServices.DataExtensions.AdoMdCommand.ExecuteReader(CommandBehavior behavior)
       at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSet.RunEmbeddedQuery(Boolean& readerExtensionsSupported, Boolean& readerFieldProperties, List`1 queryParams, Object[] paramValues)
       --- End of inner exception stack trace ---;
    The Russian string “Не удалось
    выполнить запрос для набора данных "DiskSpaceUsageForecasting"” is translated to “Could not execute query for data set "DiskSpaceUsageForecasting"”.
    I have clean installation SCOM 2012 RU1, VMM 2012 RU1. Integration SCOM with VMM work fine.
    SQL collation for all SQL DB instances (SCOM and VMM and SCOM reporting) – “SQL_Latin1_General_CP1_CI_AS”
    SQL Analysis service: SQL collation – “Latin1_General” ; language for the server – English (United States)
    I think the problem in regional settings. By my opinion there are two possible mistakes:
    SQL collation  for all SQL DB instances. May be need use “Latin1_General_CI_AS”
    as provided by
    http://blogs.technet.com/b/momteam/archive/2012/05/25/clarification-on-sql-server-collation-requirements-for-system-center-2012.aspx
    Need change regional setting. Question is for what (OS regional setting, SQL Analysis service settings,…) ?

    Error: Subreport could not be shown
    Opening a report for Client Security might result in the following error being displayed in one or more areas of the report: "Error: Subreport could not be shown."
    Background
    There are two possible reasons for this error:
    1. Wrong location   The reporting server is pointing to the wrong computer running SQL Server or a SQL Server instance.
    2. Insufficient permissions   The account configured (in SQL Server Reporting Services) to connect to the reporting database does not have appropriate permissions for the database.
    Solution
    To determine which reason is causing the error, attempt to directly open the subreport reporting the error, by clicking the name of the subreport.
    If the reporting server is pointing to a wrong location, the report displays an error similar to the following: 
    Error message
    An error has occurred during report processing.
    Cannot create a connection to data source 'SystemCenterReporting'. Cannot open database "SystemCenterReporting" requested by the login. The login failed. Login failed for user username.
    To verify the correct SQL Server computer and instance path
    In Report Manager, navigate to the report generating the error and click the Properties tab.
    Click Data Sources and under a Shared data source, note the path.
    Open the reporting Web site. If you chose the default virtual directory for reports, the URL is: http://hostname/Reports/
    If you chose to secure the viewing of reports with HTTPS, the URL is: https://hostname/Reports/
    Click SCDW.
    In the Connection type list, ensure that Microsoft SQL Server is selected.
    In the Connection string box, ensure that the correct SQL Server computer and instance name are entered.
    Note:
    A period (.) denotes the local computer.
    If the account has insufficient permissions, the report displays an error similar to the following: 
    Error message
    An error has occurred during report processing. (rsProcessingAborted) Query execution failed for data set 'DSDashboardComputersTrend'. (rsErrorExecutingCommand) EXECUTE permission denied on object 'prSAS_UX_DashboardComputersTrend', database 'SystemCenterReporting',
    schema 'dbo'.
    To determine if you are experiencing the SQL Server permissions issue
    Open the reporting Web site. If you chose the default virtual directory for reports, the URL is:http://hostname/Reportserver/
    If you chose to secure the viewing of reports with HTTPS, the URL is:https://hostname/Reportserver/
    Click Microsoft Operations Manager Reporting, click Microsoft Forefront Client Security, and scroll to DashboardComputersTrend.
    Click DashboardComputersTrend.
    If you are experiencing a SQL Server permissions issue, an error similar to the preceding error appears.
    To grant permissions to the SQL Server computer
    1. In Report Manager, click SCDW and note the account in the Connect using section. This is the account under which the database is contacted.
    2. On the server with the System Center Reporting database, start SQL Server Management Studio.
    3. In the tree, expand Security, and then expand Logins. Do one of the following:
    If the user account is listed, right-click the account, click Properties, and then go to step 5.
    If the user account is not listed, right-click Logins and choose New Login.
    4. In the Login name box, enter the user account (domain\username).
    5. In the Login Properties dialog box, click User Mapping, and then under Users mapped to this login, select the System Center Reporting check box.
    6. Under Database role membership for: System Center Reporting, select the db_owner check box, and then click OK.
    Thanks,
    Yog Li
    TechNet Community Support

  • SharePoint 2010 SP2 hosted on Windows 2012 R2 NOT discovered by SCOM 2012 R2 + 2 SP MP's

    What is the process to get SharePoint 2010 Management Packs loaded in System Center 2012 R2 to discover/monitor SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2?
    View of installed system:
     System Center 2012 R2 loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
    -Microsoft SharePoint 2010 Products Management Pack for System Center Operations Manager 2007
    -System Center 2012 Monitoring Pack for SharePoint 2010
     SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
    The SharePoint 2010 Management Shell works fine!
    Result
    Event 0, Operations Manager - Cannot identify which SharePoint farm server is associated with. Check the management pack guide for troubleshooting information.
    Looked at these already:
    KB2690744, Configuring the SharePoint 2010 Management Pack for System Center Operations Manager. 
    http://om2012.wordpress.com/2013/05/24/sharepoint-2010-mp-on-scom-2012/
    Further, if the xml push does have the command get-farm instead of get-spfarm, that could be the issue. i.e.
    http://www.scom2k7.com/advanced-troubleshooting-of-the-sharepoint-2010-mp/
    Thanks,
    +Tony
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

    Peter,
     I recommend to remove the Windows 2012 R2 server out of the farm and redeploy on W2008 R2.
    This issue does not have an easy fix.
    Summarizing, this appears to be the issue:
    1. Windows Management Framework 3.0 is integrated with Windows 2012 R2, which installs .NET 4 and Powershell 4.0. Not uninstallable.
    2. The Add-PSSnapin Microsoft.SharePoint.PowerShell is not supported with Powershell 4.0.
    3. The SCOM SP2010 MP puts a package on the defined farm server and when the agent launches the package, it calls Powershell (v4 in theis case) and errors out. The target W2012 server will have an Error 0 in the Operations Manager Event log. See below.
    Options:
    1. Work around maybe - Develop method for manual discovery (I'm working on that now).
    2. Rebuild SP2010 farm on Windows 2008 R2
    3. System Center Team - Write a new MP to down version Powershell (Powershell.exe -Version 2)
    4. Powershell Team - Write a SharePoint Snapin for Powershell 4
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

  • SCOM 2012 SP1 availability report in MS Generic Report Libary shows inaccurate data

    Hi,
    in SCOM 2012 sp1, we have the generic availability report showing many of our web sites with no up time beyond a certain date.   The web sites are ok,  the web availability monitors are all healthy and the monitors test ok
    None of these web availability tests are in Maintenance mode although what we are observing certainly makes us think that they are.
    We also have a Web transaction login monitor for WEBSITE(A)  that does not show this same outage for a login test.
    However WEBSITE(A)'s availability monitor shows the same downtime as the other web availability tests.
    Any thoughts on where to look for this problem?  Im guessing its a problem placing the data in the Warehouse?
    Thanks Lance

    Hi,
    Based on my understanding, the report shows there is downtime for the web site, but the web site did work well always.
    It seems like that there is old data stored in data warehouse, would you please check the report for recent date, such as one day or two days.
    Regards,
    Yan Li
    Regards, Yan Li

  • How to create a group in SCOM 2012 R2 based on SCCM Collection?

    Is there a way to create a group in SCOM 2012 R2 based on sccm collection? I am planning to use that group for maintenance mode.
    Thanks, Samer

    Hi,
    I think you could query all the collectin members from SCCM database then use powershell to add them to a specific OU.
    How to Create Groups in Operations Manager
    http://technet.microsoft.com/en-us/library/hh298605.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.

  • Can overrides from SCOM 2007 R2 be used in a new SCOM 2012 R2 installation?

    Hi All,
    I'm wondering if we can "easily" use our overrides/configuration from our current SCOM 2007 R2 implementation and use them in a new SCOM
    2012 R2 environment that we plan on standing up.  We are using SCOM to monitor approx. 400 servers (physical and virtual).
    We have been using 2007 R2 for a few years and we'd like to start using 2012 R2.  Instead of using the update path (2007 R2 to 2012
    to 2012 SP1 to 2012 R2), we are planning on setting up a new 2012 R2 environment and configuring our servers to start reporting to 2012 R2 (after it has been configured in such a way as to "mimic" our 2007 R2 environment).
    Ideally, we'd like to avoid going through the upgrade path.  (We'll leave our 2007 R2 environment running so that we can still access "historical
    data" until the new 2012 R2 environment has had a chance to build up its own "historical data".)
    So ... I was thinking we could export our overrides from 2007 R2 and import them into 2012 R2, but I'd like to verify that this approach makes
    sense.  We haven't done extensive customizations to 2007 R2 in terms of Distributed Applications or Management Pack Objects (although we have made some changes - which I guess we could manually configure in 2012 R2 to offer the same "experience").
    The following are some of the Management Packs that we are using in 2007 R2:
    Microsoft Windows Active Directory
    Active Directory Certificate Services
    EMC Storage Monitoring
    IBM Hardware
    Microsoft Exchange Server 2010
    McAfee
    Microsoft Forefront Server Protection 2010
    Microsoft Office SharePoint Server 2007
    Microsoft SQL Server
    Microsoft Windows DNS Server
    Microsoft Windows WINS
    Microsoft Windows Hyper-V
    Microsoft Windows Internet Information Services
     Microsoft Windows Server
    Microsoft Windows DHCP
    NetBackup Operations Manager
    Office Communications Server
    OpsLogix (BlackBerry)
    Service Level Dashboard for OpsMgr 2007 R2
    SolarWinds Orion
    Schedule Maintenance Mode
    Team Foundation Server 2010
    Virtual Machine Manager
    Microsoft Windows Cluster
    Operations Manager 2007 R2
    I appreciate all feedback and the sharing of you expertise.
    Thanks, Joe.

    As long as the base pack works and you wish to retain the customisation then you should be ok, there’s a good article
    here which explains how to perform the migration and some of implication/things to check.
    There will be complications if you’ve stored anything in the default mp but this is explained in the above article.

  • 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]

  • Getting Error code -2130771961 while Discovering Cross platform server from SCOM 2012 r2.

    Below is the Error
    Unexpected DiscoveryResult.ErrorData type.  Please file bug report.
    ErrorData: Microsoft.SystemCenter.CrossPlatform.ClientLibrary.Common.SDKAbstraction.TaskInvocationException
    Task invocation failed with error code -2130771961. Error message was: Creation of module with CLSID "{ED8C18C7-FEF4-488D-AAAF-830366BF0B40}" failed with error "Illegal operation attempted on a registry key that has been marked for deletion."
    in rule "Microsoft.Unix.HostEntryResolution.Task" running for instance "Linux Resource Pool" with id:"{7337E4AE-136A-1099-B024-2F4633B1AE1A}" in management group "pslmgmt".
       at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
       at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
       at Microsoft.SystemCenter.CrossPlatform.ClientActions.DefaultDiscovery.InvokeWorkflow(IManagedObject managementActionPoint, DiscoveryTargetEndpoint criteria, IInstallableAgents installableAgents) 
    can some one please help me ?

    Hi Pandit,
    Have you tried restarting the SCOM service on the management server that you are performing the discovery on? Refer below articles for more information.
    http://social.technet.microsoft.com/wiki/contents/articles/4966.troubleshooting-unixlinux-agent-discovery-in-system-center-2012-operations-manager.aspx
    http://www.systemcentercentral.com/forums-archive/topic/scom-2012-r2-discovery-was-not-succesful-for-solaris/
    Thanks,
    Janaka
    Janaka Rangama MCT MIEEE MBCS (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable.)

  • 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.

  • 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

  • Upgrade to R2 from SCOM 2012 SP 1 UR 4 - Final configuration failed to install

    I was upgrading our test SCOM 2012 SP1 UR 4 sever to R2 and ran into the following issue:
    Setup cannot be completed…  Final configuration failed to install.
    Everything else upgraded fine.
    There was no rollback performed…. The log states “Skipping rollback for install item Final Configuration as it was not successfully installed”
    Looking in OpsManagerSetupWizard.log in the section for Final Configuration I see the following:
    [16:00:43]:           Always: :!***** Installing: POSTINSTALL ***
    [16:00:43]:           Info:      :SetProgressScreen: StartMinorStep.
    [16:00:43]:           Warn:    :ApplyUpdates: Unable to load QFE file.
    [16:00:43]:           Always: :Doing Preinstall task for POSTINSTALL
    [16:00:43]:           Warn:    :CheckAndLoadUpdateFiles: Unable to load QFE file.
    [16:00:43]:           Always: :Doing Install task for POSTINSTALL
    [16:00:44]:           Debug: :DoInstallTask: Found Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall;PostInstallProcessor as type and method.
    [16:00:44]:           Info:      :Type: Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall  Method: PostInstallProcessor
    [16:00:44]:           Info:      :SetProgressScreen: Init Exe Install progress.
    [16:00:44]:           Info:      :AddUninstallChangeEntry: Cleaning out existing files at the ARP file cache location D:\Program Files\System Center 2012\Operations
    Manager\Setup
    [16:00:44]:           Error:     :InstallActionProcessor.DoInstallTask: method PostInstallProcessor threw exception.  We will return installSuccessful = false.:
    Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
    [16:00:44]:           Error:     :StackTrace:   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at Microsoft.SystemCenter.Essentials.SetupFramework.InstallActionProcessor.DoInstallTask(InstallItemsInstallDataItem itemToInstall)
    [16:00:44]:           Error:     :Inner Exception.Type: System.UnauthorizedAccessException, Exception Error Code: 0x80131604, Exception.Message: Access to the path 'EULA_EN_EVAL.RTF'
    is denied.
    [16:00:44]:           Error:     :InnerException.StackTrace:   at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean
    throwOnTopLevelDirectoryNotFound)
       at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.ARPFileCache()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.AddUninstallChangeEntry()
       at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall.PostInstallProcessor(Func`3 setProgressScreen)
    [16:00:44]:           Error:     :ProcessInstalls: Install Item Final Configuration failed to install.  We did not launch the post process delegate.
    [16:00:44]:           Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Final Configuration
    [16:00:44]:           Info:      :SetProgressScreen: FinishMinorStep.
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Always: :****Starting*RollBack*******************************************
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Info:      :SetProgressScreen: StartMinorStep.
    [16:00:44]:           Always: :ProcessRollback: Skipping rollback for install item Final Configuration as it was not successfully installed.
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Always: :****Ended*RollBack**********************************************
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Always: :Entering Page: FinishPage
    The log states “Access to the path 'EULA_EN_EVAL.RTF' is denied.”  I was able to find this file in D:\Program Files\System Center 2012\Operations Manager\SetupTemp\EN, but when viewing its contents I see it
    was from the SP 1 upgrade as it starts off with “MICROSOFT EVALUATION SOFTWARE LICENSE TERMS MICROSOFT SYSTEM CENTER 2012 STANDARD SERVICE PACK 1.”  Based on everything else referenced in the log file previously, it seems like it was trying to locate
    this file in D:\Program Files\System Center 2012\Operations Manager\Setup.  Also, I applied the product key after installing SP1 previously, so it was not running with an evaluation license.
    Running Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a
    gives me:
    SkuForLicense Version     TimeOfExpiration
           Retail 7.1.10226.0 12/31/9999 11:59:59 PM
    The version (7.1.10226.0) is that of SCOM 2012 R2 (as I noted before, there was no rollback.)  Everything seems to be functioning fine (Console, Web Console, Reporting Services.)
    Is there a way to get it to re-run only the Final Configuration steps (which will probably fail again as the EULA file does not exist where it expects it)?  I am not sure if there were supposed to be any further
    configuration steps that did not get completed, so i dont know how stable SCOM is now.  Should I re-run the R2 installer?  Or is it OK as is?  The only info online about a SCOM Install where the final configuration failed to install dealt with
    an error upgrading the SCOM Console, which is not relevant to my situation.  This is my test SCOM environment, running on a VM.  I could revert to the pre-upgrade snapshot and see if another upgrade attempt completes successfully, but if that does
    work I am concerned that something like this may happen in my prod environment, which is not running on a VM, so has no ability to revert to a snapshot.

    Hi,
    Please refer to the following links:
    Do I need a specific Cumulative Update Release (UR) in order to upgrade to SCOM 2012 or 2012 SP1 or 2012 R2?
    http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
    Upgrading Operations Manager from 2012 SP1 to 2012 R2 step by step
    http://www.systemcentercentral.com/upgrading-operations-manager-from-2012-sp1-to-2012-r2-step-by-step-upgrading-to-2012-r2-series/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcenterforum+%28System+Center+Central+Rollup%29
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    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.

  • 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

  • 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.

Maybe you are looking for

  • Retenção INSS

    Pessoal bom dia, Aqui no cliente há necessidade de se efetuar os lançamentos de retenções do INSS no momento do faturamento de SD. Ocorre que o valor do INSS é calculado por uma condition, e o valor dessa condição representa 11% do valor de outra con

  • Logical database vs direct access of database table

    Hi I have created a FI report.    I am trying to get data from large FI tables like BSAK, BSEG, BKPF, RSEG.  eventhough there are 10 records as per my criteria, system is taking morethan an hour time even in background processing.  This may be becaz

  • H-61MU-E35 (B3) 4MB BIOS Chip Vs 8MB BIOS BIN File - WinBond 25Q32BV

    Hello, I have MSI H-61MU-E35 (B3) motherboard with Ivy Bridge Processor, and everything was working fine,  Using Windows XP, I may have updated BIOS with different model no, so upon booting I was getting message that "BIOS File Not Found..."  In past

  • Corrupt files and RAM upgrade

    I have been having trouble with some corrupted Files in Aperture and after reading some discussion groups I was led to beIieve it might be a hardware problem and not just a software bug-some people experiencing similar problems traced it back to bad

  • Similar issue: data package

    Hi all, I have to load data to an ODS to Cube. Requirement is while loading data, records with same key should be selected in same datapackage. I am using 3.5 update rule and infopackage for updating the target. For example Article Area 123    01 123