Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.
X
Aside

System Center 2012 Configuration Manager Database Requirements – 4/26/2012

The below requirements are the listed requirements as of 4/26/2012 for ConfigMgr 2012.

Make sure to review the supported configurations on the TechNet site.

SQL Server Versions

  • SQL Server 2008 SP2 with CU9 (Standard or Enterprise)
  • SQL Server 2008 SP3 with CU4 (Standard or Enterprise)
  • SQL Server 2008 R2 with SP1 and CU6 (Standard or Enterprise)
  • SQL Server Express 2008 R2 with SP1 and CU4 (Secondary Sites)

NOTE: If you use SQL Server Standard, your CAS will only support 50k clients

Database Collation

ConfigMgr 2012 requires SQL_Latin1_General_CP1_CI_AS collation.

image

SQL Server Features

  • Only Database Engine Services is required. SQL Server replication is not needed.
  • Windows Authentication is required.
  • You must use a dedicated instance of SQL server.
  • It is HIGHLY recommended to limit the amount of memory assigned to SQL.
Aside

Configuration Manager-Reporting Services Access Denied When Running R3 Power Management Reports

Ran into an issue at a client this week that I haven’t run into before.  When trying to access the new R3 power management reports, we were receiving an access denied.  The errors we received were the following:

An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset ‘DataSet2’. (rsErrorExecutingCommand)
For more information about this error navigate to the report server on the local server machine, or enable remote errors

An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for dataset ‘DataSet2’. (rsErrorExecutingCommand)
The EXECUTE permission was denied on the object ‘PowerManagementGetPowerCapabilities’, database ‘SMS_XXX’, schema ‘dbo’.  

All other reports in Reporting Services worked fine.  The reason turned out to be that the new R3 reports use some stored procedures in the ConfigMgr database.  Web reports are typically just queries that use tables and views.  The new R3 reports are the first ones for ConfigMgr that are Reporting Services only reports.  Typically when locking down permissions on reports or a reporting service account, you would just assign the account DB_Reader rights in the SQL database.  This works for all the web reports but didn’t work for the R3 reports.  DB_Reader doesn’t have access to run the stored procedures that are required for the power management reports. 
 
In order for the R3 reports to run successfully, we need to add the service account to the “smsschm_users” database role. Huge thanks to Kent Agerlund and Garth Jones for providing me with the appropriate fix.

First, lets open up the database and drill down to the database roles:

image

Next we need to go into the properties of the "smsschm_users” role:

image

Next we need to add our service account to be a Role Member:

image

Select “Browse” and then select the service account you want to use.

image

Here we have our service account selected, then click “ok”.

image

Once you verified the service account is listed in the Role Members pane, then select “ok”.

image

Another way to add the necessary rights is to go into the login properties of your service account. Then go to “user mapping” and select the SMS/ConfigMgr DB and check the database role membership. This is probably the easier method (less clicks), but it’s good to know there are 2 ways to do it Smile

image

Kent Agerlund also has a post on this.  I wasn’t able to find his post when I encountered the issue and used Google, however I was told that using Bing would have resolved my issue, but I haven’t tested that. 

http://blog.coretech.dk/kea/modifying-the-dataset-execution-account-after-installing-configuraiton-manager-r3/

Aside

ConfigMgr–Prerequisite Checker-SQL Server Sysadmin Rights Bug

Was working on setting up a new Central Site for a client today and noticed what appears to be a bug in the pre-req checker.  This was building a new site server on Server 2008 R2 with SQL 2008 R2 from ConfigMgr SP2 media.  I wanted to run the pre-req checker before launching the install and received the following error talking about the SQL Sysadmin rights.

1

I double-checked everything and was still sure I had everything correct.  On a whim, I decided to launch the ConfigMgr install to see if I still received the same error.  Lo and behold the error no longer surfaced on the box, without any changes having been made. 

2

Hope this helps someone else from pulling their hair out!