Hello folks

Since the release of version 6.0.7303.0 of Windows Server Operating System MP, many of you have reported regression bugs in the management pack. We now fixed all those issues in the latest released version 6.0.7316.0: https://www.microsoft.com/en-us/download/details.aspx?id=9296. The MP guide available in this link has details about the various bugs that were fixed. If you have any feedback on the MP, please provide it on our user voice website. 

Ravi Chivukula | SCOM Program Manager | Microsoft
Get the latest System Center news on Facebook and Twitter
Main System Center blog: http://blogs.technet.com/b/systemcenter/
Operations Manager Team blog: http://blogs.technet.com/momteam/

Hi everyone, my name is Mihai Sarbulescu and today I wanted to share a quick support tip with you. Please be aware that some Management Packs for Microsoft System Center Operations Manager have workflows that need to connect to the Internet in order to perform various actions. The Office 365 Management Pack is a good example of this as it needs to connect to the Internet to complete certain actions related to discovery and monitoring. In such situations, if a proxy server is needed to connect to the Internet from the System Center Operations Manager Management Servers, the proxy configured in Internet Explorer or WinHTTP will not be taken into account by the System Center Operations Manager processes – here MonitoringHost.exe processes which are running the actual workflows.

In order to configure the correct proxy server, the MonitoringHost.exe.config file needs to be modified on all management servers from the All Management Servers Resource Pool. The MonioringHost.exe.config file can be found in the System Center Operations Manager installation folder under %ProgramFiles%\Microsoft System Center 2012\Operations Manager\Server\. Make a backup of the MonitoringHost.exe.config file and then add these lines in the <configuration> section of the config XML:

<system.net>
  <defaultProxy enabled=”true” useDefaultCredentials=”true”>
    <proxy proxyaddress=”http://<PROXYADDRESS>:<PORT>” bypassonlocal=”true” />
    <bypasslist>
    </bypasslist>
  </defaultProxy>
</system.net>

Make sure that you replace <PROXYADDRESS> with the correct proxy server address and <PORT> with the correct proxy server port. When done, simply save the MonitoringHost.exe.config file and close it and you’re all set.

Mihai Sarbulescu | Escalation Engineer | Microsoft

Microsoft System Center Operations Manager, along with the Service Manager management packs, provides an excellent monitoring platform for Service Manager. Many important pieces that are vital to Service Manager health can be monitored, including:

• Checking SQL Server to be sure the Broker Service is enabled
• Checking the Service Manager Grooming History to be sure cleanup of the CMDB is taking place
• Checking workflows for problems
• Checking MPS sync for failures

…and much more. The full list of rules and monitors can be found in the Service Manager Management Pack Guide that you can download along with the Management Packs, and I would encourage you to read that guide thoroughly before deploying the Management Packs and bringing your Service Manager monitoring online.

One key note in the guide is where it says “This management pack requires agentless monitoring…” It’s been a while since the guide was released, and that, along with the fact that the SP1 release for System Center 2012 introduced a Control Panel applet for the Microsoft Monitoring Agent (HealthService), has contributed to some confusion over Agent versus Agentless monitoring. This post addresses one of the possible drawbacks of using Agent-based monitoring and then receiving the following events in your Service Manager management server’s Operations Manager Event log:

Event ID 6024
LaunchRestartHealthService.js : Launching Restart Health Service. Health Service exceeded Process\Handle Count or Private Bytes threshhold.

Event ID 6060
RestartHealthService.js : Restarting Health Service. Error: Failed to Terminate Health Service

Event ID 6062
RestartHealthService.js : Restarting Health Service. Service successfully restarted.

For more information on this, see https://blogs.technet.microsoft.com/omx/2013/10/17/health-service-restarts-on-service-manager-servers-with-scom-agents/.

In Service Manager, the Microsoft Monitoring Agent’s primary role is managing all the Service Manager workflows, including workflow subscriptions, group calculations, connectors, configuration, etc. Adding the Service Manger HealthService as an Operations Manager agent can result in a negative impact on the Service Manger workflows when the Operations Manager workflows run on their configured schedules.
So how do you find out whether you’re agent managed or not, and how do you switch?

First, check in Control Panel on your Service Manager Workflow Management server. If you have anything listed under Management Groups you’re probably Agent managed:

You can also check in Operations Manager. Open the console and navigate to Administration –> Device Management –> Agent Managed and search for your Service Manager Workflow Management server. If it’s in there, you’re definitely Agent managed.

The good news is that it’s easy to switch. First, clear everything from Control Panel on your Service Manager Workflow Management server, including the Automatically update management group assignments from AD DS check box. Next, select the Service Manager Workflow Management server from Operations Manager and click Delete from the task pane.

Give everything a few minutes to settle in, and then from Operations Manager, right-click Device Management and open the Discovery Wizard:

At this point I’m going to assume you’re familiar with Operations Manager and skip to the important part; the Select Objects to Manage page. Select your Service Manager Workflow Management server from here, then at the bottom of the wizard dialog, choose Agentless from the Management Mode: dropdown list:

After you choose Agentless, you’ll have the option to choose your Proxy Agent:

The proxy agent should be an Operations Manager Management Server or another computer in your environment (not one running Service Manager!) that is running the Microsoft Monitoring Agent and reports to the desired Operations Manager management group. The MP deployment guide has more details about what is required of your proxy agent.

One more thing before closing: The MP deployment guide section on the Service Manager Database Account profile in Operations Manager has an omission. One of the rules uses a function within SQL which requires Execute permissions in SQL. Instead of choosing the db_datareader role in SQL, you can choose something in SQL that includes Execute permissions, or much better, just give your data reader account permission to execute that single object in SQL.

Start with the Database User you created. Select the user and then Properties:

Select the Securables page and then click Search. You will get the dialog below. Select Specific Objects, then click OK.

From Select Objects, click Object Types, and then click OK, then select Scalar functions, and click OK.

Click, Browse and locate the dbo.fn_GetEntityChangeLogGroomingWatermark function, select it, and click OK.
Note that after you click OK, you have the option to check names. You can use this if you wish to be sure you have the correct name. When done, click OK again.

Give the user Grant->Execute permissions on the object, then click OK and you’re done.

You can confirm that you set the desired permissions by opening SQL Management Studio as the user you created for DB Reader. Expand the Functions Folder under the Database, and then expand Scalar Functions. You should only see the one for which you granted permissions. You can also test by running this query using the user account for which you granted permissions.

SELECT dbo.fn_GetEntityChangeLogGroomingWatermark() AS HighWaterMark

Now, you’re agentless!

REMINDER: Be sure you go through the MP deployment guide to get the correct security configurations for all the pieces of this monitoring solution.

The good news is that there’s a solution for monitoring your Service Manager environment, and you probably already have it: Microsoft System Center Operations Manager. Go forth and monitor, and go agentless, this will keep you informed of many known issues in Service Manager and help keep your HealthService healthy.

Scott Walker, Senior Support Escalation Engineer
Microsoft Enterprise Cloud Group

We recently published a new KB article that lists all of the cumulative updates that were released for Microsoft System Center 2012 R2 Operations Manager (OpsMgr 2012 R2). The updates are listed according to release date and include the associated build number. Also note the following:

• Cumulative update build numbers with a larger numeric value include the fixes from all previously released cumulative updates.
• Any version of OpsMgr 2012 R2 can be updated to a later cumulative update.
• You cannot uninstall a later-version cumulative update to downgrade to an earlier-version cumulative update.

For the complete list, please see the following:

3193857 – Cumulative update releases for Microsoft System Center 2012 R2 Operations Manager (https://support.microsoft.com/en-us/kb/3193857)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

We recently published a new KB article that lists all of the cumulative updates that were released for Microsoft System Center 2012 Operations Manager Service Pack 1 (OpsMgr 2012 SP1). The updates are listed according to release date and include the associated build number. Also note the following:

• Cumulative update build numbers with a larger numeric value include the fixes from all previously released cumulative updates.
• Any version of OpsMgr 2012 Service Pack 1 can be updated to a later cumulative update.
• You cannot uninstall a later-version cumulative update to downgrade to an earlier-version cumulative update.

For the complete list, please see the following:

3193856 – Cumulative update releases for Microsoft System Center 2012 Operations Manager Service Pack 1 (https://support.microsoft.com/en-us/kb/3193856)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

Microsoft System Center Reporting Manager 2006 has reached its end of support date as of October 11, 2016. System Center Reporting Manager 2006 was built as a Microsoft SQL Server-based data warehouse that integrated management data from Microsoft Operations Manager (MOM) 2005, asset information from Microsoft Systems Management Server (SMS) 2003, and business context data to create customized queries and reports. No subsequent versions of this product were released. 

For monitoring and reporting capabilities available today, learn more about Microsoft System Center Operations Manager and Microsoft System Center Configuration Manager.

Have questions about supported products? Visit Microsoft Support Lifecycle to view a list of supported products and related policies.

Just a quick note to let you know that Update Rollup 1 for System Center 2016 Operations Manager (OpsMgr 2016 UR1) is now available. For all the details regarding UR1for OpsMgr 2016, please see the following:

3190029 – Update Rollup 1 for System Center 2016 Operations Manager (https://support.microsoft.com/en-us/kb/3190029)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

A critical problem that IT Professionals face today is separating critical alerts and non-essential alerts. They are flooded with alerts, many of which do not warrant concern, or should be the center of focus in one scenario or environment and inconsequential in another. Data Driven Alert Management, a new feature of System Center 2016 Operations Manager, can come in handy while breaking through the clutter.

One typically sees such behavior if monitors or rules in a management pack haven’t been tuned to suit the specific scenario or environment dependent monitoring requirement. The default settings (configuration of monitors and rules) in a management pack have been designed to cater to wider set of customer monitoring requirements. Since each environment is different, the default settings of a management pack should be tuned to suit specific environment needs. The Management Pack Lifecycle article outlines the best practices to tune and customize a management pack.

The process to tune management packs comes with the following challenging tasks:

1. Analysis of data from Ops DB
2. Generation of reports to understand which management pack, monitors, rules, or sources have been generating a lot of noise (non-essential alerts)
3. Modification of parameters associated with MP

With the inclusion of this feature one can get a single view to gather quick insights on data pertaining to alerts that are being generated at different levels: management packs, individual monitors and rules, or sources. It also empowers the user by providing the ability to take requisite actions from the same pane:

1. Tuning the thresholds
2. Disabling a monitor/rule
3. Overriding parameters of a monitor/rule

Based on the requirement, the tuning can be done at different levels, as described below.

This feature, along with the management pack  Updates and Recommendations feature completes the full Management Pack Lifecycle process.

Feature Description

The Tune Management Packs screen displays different Management Packs (MPs) and the counts of alerts associated with each; management packs are listed only if the total number of alerts associated with them exceeds a certain threshold. The threshold and the time period during which alerts were captured can be adjusted by using Identify Management Packs to Tune option. One can view relevant information pertaining to the listed MPs by selecting the properties option (this information is useful to understand the respective management pack). Based on the information at hand, one can decide which management pack seems to be noisy and must be tuned. One can then use Tune Alerts option to delve
deeper into the tuning process.

Once there, one can use the following information (listed in bullets below) along with the information available under View or edit settings of this Monitor/ Rule option to tune individual alerts:

1. Alerts associated with the Management Pack
2. Corresponding counts
3. Severity of the corresponding alerts
4. Priority of the listed alerts
5. Source of the alerts (Monitor vs Rule)
6. Name of the corresponding Monitor or Rule

Additionally, the tuning feature also lets users identify the sources of an individual alert, and associated counts per source. Alerts can be tuned per source as well as at different levels – for all objects of the target class, for a group, for a specific object of a class, and for all objects of another class.

Tuning involves enabling/ disabling individual alerts or overriding associated parameters such as priority, severity, etc.

The detailed steps to use this feature can be found under Data Driven Alert Management section of the corresponding Technet documentation.

You can find the System Center 2016 GA here.

We request you to try out Data Driven Alert Management feature in Operations Console. You can submit your feedback at our SCOM Feedback site.

System Center Operations Manager users may face the following common challenges during the lifecycle of a Management Pack (MP):

1. Continually reviewing the ever-changing IT environments (dynamic) for new workloads or updates to old workloads to add or update the requisite MP
2. Understanding which MPs were not installed or imported while setting up monitoring of a workload so that the missing MPs can be installed or imported to monitor the workload completely (a situation wherein not all MPs required to monitor a workload completely were installed, resulting in partial monitoring of the workload)
3. Tracking availability of updates from the Online Catalog (OC) to an already installed MP, corresponding to a Workload
4. Searching the desired MP on Online Catalog Manually (a time-consuming process)

The new management pack Updates and Recommendations feature in System Center 2016 Operations Manager of provides an indispensable solution to these challenges by introducing significant automation in these often cumbersome activities. At the same time, it provides a single location to perform these interrelated activities for ease of use.

The workloads listed here are supported by this feature. Also, for this feature to work, agents should be installed on the servers (on which workloads are running), and the machine hosting the console must be connected to the internet. This feature along with the Data Driven Alert Management feature provides a holistic solution to the challenges faced during Lifecycle Management of a management pack.

Feature Description

This feature enables allocation of a status relevant to the state a workload is in, from the perspective of MP Lifecycle Management. Based on the same following scenarios are enabled from a single end point/ screen:

1. Discovering: Recognizes supported workloads (whether new or old) that aren’t being monitored but are a part of the respective management group
2. Resolving partial installations: Recognizes which MP files are missing to enable complete monitoring of a Workload
3. Updating: Recognizes and indicates availability of updates to various MPs that have been installed
4. Finding: The above mentioned scenarios are empowered by the ability of the feature to leverage Microsoft Management Pack Catalog Web Service and pin-point the updates and missing MPs, so that users can resolve inconsistencies within a few clicks

Users can delve deeper on the action items by using the more information option which will help them understand why a recommendation was displayed and why a particular workload has a specific status, view the corresponding DLC page and guide by using the respective option, and install/ import or update MPs with respect to a selected workload or all listed the workloads listed on the main screen by using Get MP or Get All MPs options respectively.

Also, for users that rely on non-English management packs, the enhanced Get MP option includes language selection settings, if available.

Note: The discovery logic runs every 24 hours by default, and can be modified to run at a higher frequency using appropriate Cmdlets in Operations Manager Shell. One can also use the script that can be found here.

The detailed steps to use this feature can be found under Updates and Recommendations section of the corresponding Technet documentation.

You can find the System Center 2016 GA here.

We request you to try out MP Updates and Recommendation feature in Operations Console. You can submit your feedback at our SCOM Feedback site.

We have received feedback from customers like you to have an HTML-based web console and not Silverlight-based. We are happy to announce that we have transitioned to an HTML-based web console, with the exception of the dashboards views. Dashboard views today are still Silverlight-based, but we will continue our investments to provide you HTML5-based dashboards in the future. With this change, you can now access System Center 2016 Operations Manager web console from a variety of browsers, such as Google Chrome, Microsoft Edge and Mozilla Firefox.

As part of this HTML web console implementation we have also made significant performance improvements in loading data, views, monitoring tree, and tasks.

You can find the System Center 2016 GA here.

We request you to try this feature. You can submit your feedback at our SCOM Feedback site.

Performance improvements have been made to State views and Diagram views in the System Center 2016 Operations Manager console to increase responsiveness. You will now see the following improvements:

1. State view is optimized to load efficiently
2. Diagram view is optimized to load efficiently

These improvements will be more visible in an environment where the load on the Operations Manager database is high.

Improving the responsiveness of the UI continues to be a top priority for us, and this update follows the improvements from the System Center 2016 TP5 release, details of which can be found here.

You can find the System Center 2016 GA here.

We request you to try this feature. You can submit your feedback at our SCOM Feedback site.

Until System Center 2012 Operations Manager R2, you could get only basic monitoring for your network devices, such as “Availability Monitoring” and “Port/Interface Monitoring”. To get Extended Monitoring for your network devices, you had to work with Microsoft to get your devices supported in Operations Manager. This extended monitoring capability was limited to only processor and memory components, in addition to the basic monitoring.

With the release of System Center 2016 Operations Manager, you now have access to the new Network Monitoring Management Pack generator tool which provides you with extended monitoring for your SNMP-enabled devices by generating your own custom Management Pack.

Tool Description

Network Monitoring Management Pack generation tool includes an SNMP_MPGenerator UI tool and a NetMonMPGenerator.exe command line tool.

1. SNMP_MPGenerator UI tool has an inbuilt MIB browser. Users can load MIB files, search through the Object Identifiers (OIDs) of the component they wish to add workflows for and create rules and monitors.
2. Users can add workflows (monitors and rules) for device components such as processor, memory, fan, temperature sensor, power supply, voltage sensor and custom device components.
3. This tool can also support custom devices in addition to already supported devices like Switch, Router, Firewall and Load Balancer.
4. Users can define monitors and rules for multiple devices in the project file and generate a single Management Pack for all of their devices.
5. This tool includes the command line equivalent NetMonMPGenerator.exe for users who wish to generate MP through command line interface. Users need to define device information and workflows in an input XML file and use the commandline tool to generate custom management pack.

The tool and the user guide can be downloaded here. The management pack generated by this tool is currently supported by System Center 2016 Operations Manager and System Center 2012 R2 Operations Manager.

Before initiating the maintenance of IT infrastructure elements, one would want to initiate Maintenance Mode to suppress monitoring of infrastructure elements undergoing maintenance. This will prevent the monitoring tool from generating alerts and events pertaining to these elements, while they are under maintenance. Schedule Maintenance Mode feature (listed in Administration Workspace, earlier) allowed users to achieve this, but it was here that we identified the following gaps:

1. Typically, in large organizations, Operators who manage the designated hosts, would also intend to maintain them as part of planned and unplanned maintenance workflows, and hence they, not just Administrators, should be allowed to set Maintenance schedules from the console
2. Maintenance process is automated and is typically initiated from the client end (in batches)

Hence we have now enabled Maintenance Mode from Client side via agent, and moved “Maintenance Schedules” from the Administration pane to the Monitoring pane (which is accessible to Operators), so that operators can access this feature. These improvements have implemented in System Center 2016 Operations Manager.

Now, a machine can be put into maintenance from client side via agent, and operators will be able to access “Maintenance Schedules” from the Monitoring pane of Operations Console.

The detailed steps to use this feature can be found under How to suspend monitoring temporarily by using maintenance mode section of the corresponding Technet documentation.

You can find the System Center 2016 GA here.

We request you to try this feature. You can submit your feedback at our SCOM Feedback site.

We at Microsoft are committed towards understanding and solving the problems of our customers. Your response to this survey will aid us in that endeavor. With your inputs we will be able to make the required improvements to Microsoft’s IT Operations Management solutions (such as SCOM, OMS, etc.), this will help us serve you better.

Hence, we request you to take 5 – 10 minutes out of your busy schedule to respond to this survey.

Follow this link to the Survey:

https://microsoft.qualtrics.com/SE/?SID=SV_a5A41w7hE94LLj7

If you have any query, please post it as a comment below.

The Visual Studio Authoring Extension now allows you to create management packs for System Center 2016 Operations Manager. When creating a new management pack project in Visual Studio, you can now select the “Operations Manager 2016 Management Pack ” template. This template uses the same schema as System Center 2012 R2 Operations Manager (2.0 schema), but has all the latest libraries of System Center 2016 Operations Manager.

If you are importing an existing management pack, then this latest extension will allow you to select the System Center 2016 Operations Manager schema for the management packs chosen. 

The Visual Studio Authoring Extension can be downloaded from here. You can submit your feedback at our System Center Operations Manager Feedback site.

Are you worried about the health of your Operations Manager environment? Looking for a tool that can help keep Operations Manager up-to-date and run efficiently?

We present you the System Center Operations Manager Assessment solution that assesses the risk and health of your System Center Operations Manager Server environments. This solution is available to all 2012 SP1 and 2012 R2 Operations Manager users on Operations Management Suite (OMS) for free!

Solution Description

System Center Operations Manager Assessment solution on OMS assesses your Operations Manager environment against best practices that were collected over the years from Microsoft Knowledge Base articles and field engineers across multiple environments, industries and scenarios. This solution provides a health check and risk assessment of the Operations Manager environment and recommendations to fix the issues identified.

Installing and Configuring the solution

Use the following information to install and configure the solution

• Before you can use an assessment solution in OMS, you must have the solution installed. To read more about installing solutions, see Add Log Analytics solutions from the Solutions Gallery.
• Configure the System Center Operations Manager Assessment rule
• Set the Run As account for System Center Operations Manager Assessment

Configure the System Center Operations Manager Assessment rule

System Center Operations Manager Assessment Solution’s Management Pack consists of a rule by name “Microsoft System Center Advisor SCOM Assessment Run Assessment Rule”. This rule is responsible for the run of the assessment. To enable the rule and configure the frequency, follow the steps below.

Enable the assessment to run

By default, “Microsoft System Center Advisor SCOM Assessment Run Assessment Rule” rule is in disabled state. To run the assessment, this rule has to be enabled against a Management Server. To do this, follow the steps below:

• Enable the rule for a specific Management Server
  • In the Authoring workspace of the Ops Manager console, search for the Rule “Microsoft System Center Advisor SCOM Assessment Run Assessment Rule” in Rules pane
  • From the search results appeared, select the one with “Type: Management Server”
  • Right click on the above selected rule and click on Overrides  For a specific object of class: Management Server
  • Select the Management Server that this rule should execute on from the available Management servers
  • Make sure to change the property value of Enable to “True” as in the screenshot shown below:

While still in this window, to configure the frequency of the run, follow the steps below

Configure the frequency of the run

The assessment is configured to run 10080 minutes (or 7 days), the default interval. This interval can be overridden to a value of at least 1440 minutes (or 1 day). This value represents the minimum time gap required between successive assessment runs. To override the interval, follow the steps below:

• Override the interval of the assessment run
  • In the Authoring workspace of the Ops Manager console, search for the Rule “Microsoft System Center Advisor SCOM Assessment Run Assessment Rule” in Rules pane
  • From the search results appeared, select the one with “Type: Management Server”
  • Right click on the above selected rule and click on “Override the Rule  For all objects of class: Management Server”
  • Change the parameter value of Interval to the desired interval value.
    In the screenshot below, this value is set to 1440 minutes i.e. 1 day
    
  • Note that if the value is set to less than 1440 minutes, then the rule runs at a one day interval i.e. the rule ignores this interval value and runs at a frequency of 1 day

Set the Run As account for System Center Operations Manager Assessment

OMS builds upon management packs for workloads to provide value-add services. Each workload requires workload-specific privileges to run management packs in a different security context, such as a domain account. You need to provide credential information by configuring an Operations Manager Run As account.

Use the following information to set the Operations Manager run-as account for System Center Operations Manager Assessment.

• In the Operations Manager Console, go to the Administrations tab
• Under the Run As Configuration, click Accounts
• Create the Run As Account, following through the Wizard, creating a Windows account. The account to be used is the one identified and having all the prerequisites below
  • A domain account member of the local Administrators group on all servers in the environment (All Operations Manager Roles – Management Server, OpsMgr Database, Data Warehouse, Reporting, Web Console, Gateway)
  • Operation Manager Administrator Role for the management group being assessed
  • Execute the script to grant granular permissions to the account on SQL instance used by Operations Manager.
    Note: If this account has sysadmin rights already, then skip the script execution.
• Under Distribution Security, select More secure
• Specify the Management Server on which this account will be distributed
• Go back to the Run As Configuration and click Profiles
• Search for the System Center Operations Manager Assessment Profile
• The profile name should be, “Microsoft System Center Advisor SCOM Assessment Run As Profile”
• Right click and update its properties, and add the recently created Run As Account we just created in step 3

 SQL Script to grant granular permissions to the Run As account

Execute below script to grant required permissions to the Run As account on the SQL Instance used by Operations Manager

-- Replace <UserName> with the actual user name being used as Run As Account.
 USE master

-- Create login for the user, comment this line if login is already created.
 CREATE LOGIN [UserName] FROM WINDOWS

--GRANT permissions to user.
 GRANT VIEW SERVER STATE TO [UserName]
 GRANT VIEW ANY DEFINITION TO [UserName]
 GRANT VIEW ANY DATABASE TO [UserName]

-- Add database user for all the databases on SQL Server Instance, this is required for connecting to individual databases.
 -- NOTE: This command must be run anytime new databases are added to SQL Server instances.
 EXEC sp_msforeachdb N'USE [?]; CREATE USER [UserName] FOR LOGIN [UserName];'

Use msdb
 GRANT SELECT To [UserName]
 Go

--Give SELECT permission on all Operations Manager related Databases
 --Replace the Operations Manager database name with the one in your environment
 Use [OperationsManager];
 GRANT SELECT To [UserName]
 GO

--Replace the Operations Manager DatawareHouse database name with the one in your environment
 Use [OperationsManagerDW];
 GRANT SELECT To [UserName]
 GO

--Replace the Operations Manager Audit Collection database name with the one in your environment
 Use [OperationsManagerAC];
 GRANT SELECT To [UserName]
 GO

--Give db_owner on [OperationsManager] DB
 --Replace the Operations Manager database name with the one in your environment
 USE [OperationsManager]
 GO

ALTER ROLE [db_owner] ADD MEMBER [UserName]
 GO

Solution Details

After a successful assessment of the Operations Manager environment, recommendations are generated. Users can view these recommendations in their OMS workspace by clicking the System Center Operations Manager Assessment tile.

Each recommendation has a weightage assigned based on probability of occurrence, impact if occurred and effort required to fix. This will guide the user to prioritize the recommendations to act on.

Clicking on any of the recommendations, will open a new screen with details such as description of the issue, suggested actions, affected objects etc.

Next Steps

Try this solution today on your Operations Manager environment and we would love to hear your feedback on this.
Get started with Operations Management Suite and activate your free account

How to share feedback?

User Voice : To suggest any improvements/ideas on this solution, visit the SCOM UserVoice page
Email: Tell us at scompm@microsoft.com
OMS Forums: Good general discussion of OMS.  Visit the OMS Forums.

We’ve seen a tremendous amount of interest in System Center 2016 Operations Manager so I thought I’d take a minute and share a few resources that should help you get started on the right track. This isn’t a comprehensive list but they’re some of the resources that I’ve found most helpful. Whether you’re just starting to look at what OpsMgr 2016 has to offer or if you’re already rolled it out, this is a good starting point for questions you may have,

Getting Started

If you’re still in the investigative phase and looking to get more information on what Operations Manager 2016 has to offer, you can see what’s new and even download a free trial via the links below.

• What’s new in Operations Manager: https://technet.microsoft.com/en-us/system-center-docs/om/get-started/whats-new-in-operations-manager
• Download a free evaluation: https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-technical-preview

Product Documentation

The core product documentation for Microsoft System Center 2016 Operations Manager can be found using the links below. Topics cover everything from planning your deployment to usage and troubleshooting.

• Getting Started with System Center 2016 Operations Manager: Written for customers who are either new to Operations Manager or are looking for “What’s New” information.
• Planning for System Center 2016 – Operations Manager: Review information to help you plan the deployment of Operations Manager into your organization.
• Deploying System Center 2016 – Operations Manager: Read these topics to learn how to deploy Operations Manager in your environment.
• Initial Monitoring After Operations Manager Is Installed: Read these topics to get started with monitoring your environment.
• System Center 2016 – Operations Manager Operations Guide: Read these topics once you have Operations Manager up and running and are looking for procedures for day to day operations.
• Management Pack Authoring Guide for Operations Manager: The Management Pack Authoring Guide for Operations Manager provides information on creating custom monitoring for your service or application.

Video Learning

If you were lucky enough to attend Microsoft Ignite back in September then you may have already seen our sessions on Operations Manager, but if not you can view them on-demand here:

• Monitor your changing datacenter using Microsoft System Center 2016 Operations Manager: https://myignite.microsoft.com/videos/3022
• Monitor and diagnose web apps & services with Application Insights & SCOM: https://myignite.microsoft.com/videos/2744

Staying Current

It’s important to stay up to date on what’s happening in Operations Manager and there are a few options available to do this. The best resource is our System Center Operations Manager Team Blog. Here you will find tips and tricks from our OpsMgr support engineers, announcements from the product team, information about the latest product updates and downloads, as well as notifications for every new piece of content/documentation we release.

If you subscribe to our blog via RSS (here), you will automatically be notified any time something new is posted. Personally, I use Outlook when subscribing to RSS feeds since I’m in there all day checking email already, so if you need a newsreader and already use Outlook then that might be a good solution for you. If social media is more your thing, we make the same announcements on Twitter and Facebook via the links below.

• Twitter
• Facebook

Getting Help

One of the best resources for finding answers is our Operations Manager support forum. There you will find a community of experts, MVPs, as well as members of the support team and the product group who collectively hold a wealth of information about to implement, use and troubleshoot OpsMgr in a virtually any kind of environment. If you need help with a problem or maybe just need some advice, the good folks there will get you pointed in the right direction. And of course, Microsoft product support is here 24/7 to help with any Operations Manager issue or question you may have. You can find more information on the support options available here.

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

We are releasing an updated version of Microsoft System Center Management Pack for Office 365. The new Management Pack(MP) has upgrades to subscription authorization method, the application to monitor can now be either automatic for which Microsoft Office 365 Global Administrator credentials are required or manual for which Azure application creation is necessary. New message center messages and categorizations have been added. The new MP supports two factor authentication, as the MP now inquires Office 365 Service Communications API V2. To support Chinese subscription, an ability to customize the endpoints and resources is also provided. Various customer bugs have been addressed, the MP guide has more details.

We encourage you to try this MP and provide us feedback on our user voice website.

We want to let you know that we are releasing an updated version of “Microsoft System Center 2016 Management Pack for Windows Server Operating System“. Some of the changes in this new MP are

• New object types have been added for Nano to help users differentiate and manage them accurately
• New monitor is added to alert when the Storport miniport driver times out a request
• Various bugs related to Nano server such as issues with Nano Server Cluster Disk and Nano Server Cluster Shared Volumes health discoveries, Free Space monitors on Nano Server are fixed
• Fixed multiple customer and regression bugs, please refer to the Management Pack guide for details

You can find all the details as well as a download link here: https://www.microsoft.com/en-us/download/details.aspx?id=54303. Provide us feedback on our user voice website.