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:
Next we need to go into the properties of the "smsschm_users” role:
Next we need to add our service account to be a Role Member:
Select “Browse” and then select the service account you want to use.
Here we have our service account selected, then click “ok”.
Once you verified the service account is listed in the Role Members pane, then select “ok”.
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
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.
There is a new series on the TechNet forums that will be going through the R3 Power Management piece.
In this post series I will go through System Center Configuration Manager 2007 R3 Power Management showing general overview and prerequisites for the new SCCM 2007 R3 Power Management feature and then deeply go through the step by step to enable and configure SCCM 2007 R3 Power Management feature,
In this 1st part I will give a general overview about the new feature and the prerequisites.
Management in Microsoft System Center Configuration Manager 2007 R3 addresses the need that many organizations have to monitor and reduce the power consumption of their computers. The feature leverages the power management features built in to Windows to apply relevant and consistent settings to computers in the organization. Different power settings can be applied during and outside of working hours. For example, it might be acceptable to apply a more restrictive power plan during non-peak hours. In cases where computers must always remain switched on, you can prevent power management settings from being applied.
This blog will be a walkthrough and setup guide for Configuration Manager (ConfigMgr) R3 prestaged media. This will cover the basic steps required in order to use the new R3 feature in your environment.
First some background on prestaged media from Microsoft:
Prestaged media is an alternative way to deploy an operating system to computers. Prestaged media is a Windows Image (.wim) file that can be installed on bare metal computers by the computer manufacturer or at an enterprise staging center. This media includes a boot image and an operating system image that an administrator can predeploy to a hard disk prior. Prestaged media reduces network traffic and the time required to provision a computer. Prestaged media works with existing task sequences to provide a complete operating system deployment.
Prestaged media is suitable for use in environments where you would want to deploy content to a computer, but do not want to or are unable to have the computer fully provisioned, for example during the computer manufacturing process or at an enterprise staging center. Computers are distributed within the enterprise with the prestaged media already loaded. When the computer starts for the first time, the computer will boot into WinPE and connect to the Configuration Manager site management point to check for available task sequences.
NOTE: When creating prestaged media, ensure that the boot image you are using has the appropriate network and mass storage drivers need for the system to complete the provisioning process.
Creating the prestaged media image
Right click on Task Sequences and select “Create Task Sequence Media”.
Select “Prestaged Media”.
Enter any information you want added to the .wim file, then specify the location and name of the file, then click Next.
Take note of what you put in the Created By field because whatever you put there, will end up the name of the drive as in these examples.
You can however change the field in the image properties. If you leave it blank, then “SCCM” will be added automatically for you.
Next, you can select whether or not to enable unknown computer support, password protect the media, as well as the certificate options.
Next, we need to select the boot image and operating system you want to stage to the computer.
Then we have our summary before the operation begins.
Click Close when the process is completed.
Importing the prestaged image into ConfigMgr
Next we need to import our newly created .wim into ConfigMgr.
Browse to the path where you put the prestaged wim we previously created. Then select Next.
Provide properties for the image, then select Next.
Review the summary and then select Next.
Click Close when the process has completed.
Next you will need to distribute the image out to the distribution points. Right-click on the image and select Manage Distribution Points. Then select “Copy the package to new distribution points”. Then select Next.
Select the Distribution Points you want to copy the image to, then select Next.
Click Close when the process completes. You can monitor distrmgr.log to review the distribution status.
Creating a Task Sequence to deploy the prestaged image to a computer
Right-click on Task Sequences and select New – Task Sequence.
Select “Create a new custom Task Sequence”.
Name the Task Sequence appropriately and then select Next.
After the process completes successfully, click Close.
Ensure the Task Sequence has the appropriate boot media. You can do this by selecting Properties on the Task Sequence.
Ensure the boot image selected is the same one as you used when creating the Prestaged Media image.
Next we need to edit the Task Sequence and add the appropriate steps.
First we need to add a “Format and Partition Disk” step.
If you are using Bitlocker, then you’ll need to create a 100mb partition, something similar to this example.
If you are not using bitlocker, then you can just create a single partition.
NOTE: You do not need a Bootsect.exe command as you may have seen with other documentation. This is unnecessary as the Format and Partition disk step takes care of this for you.
Next we need to add a “Apply Data Image” step. Select the Prestaged media image you had previously imported.
If you are not using bitlocker, then you can leave the Destination as “next available formatted partition”.
If you are using bitlocker, then you need to change the Destination to match your configuration.
Next we need to add another “Run Command Line” step to shutdown the computer and end the Task Sequence.
Using a command line of “wpeutil shutdown”.
The finalized Task Sequence should look something like this.
Next if you advertise this Task Sequence to the appropriate collection, then you can run this Task Sequence on a reference machine to apply the prestaged image to that machine. (Other Task Sequences have been removed from the screenshot)
Configuring a Task Sequence to “finish” a prestaged image
Prestaged media is designed to work with your existing Task Sequences. We only need to make one minor change to the “Partition Disk” step in order for Prestaged media to work successfully. We need to add a Task Sequence variable step that says _SMSTSMediaType not equals OEMmedia. This tells the Task Sequence to skip this step when using Prestaged media, so that we don’t delete the content we’ve prestaged.
No change is required to the Apply Operating System step as the logic already exists to detect OEMMedia.
You will however, need to configure your Destination to match whether or not you are deploying bitlocker or whatever other custom setup you may have.
If you are using bitlocker, ensure this step matches the configuration you used when applying the prestaged image to the disk.
If you are not using bitlocker, then just use the default configuration.
Executing the Task Sequence on a prestaged machine
If you power on a computer that has a prestage image applied to it, it will automatically boot the WinPE image that is staged on the machine.
Then we can contact the ConfigMgr server and get our policies.
You will see it run through the first Task Sequence steps fairly quickly.
After a couple minutes you’ll see the system reboot.
Sysprep will then run, along with whatever final configurations you have in your Task Sequence and you should find yourself with a computer joined to the domain and ready to log in within a few minutes. In my Hyper-V lab, without any additional software applications to install, the login prompt was presented in less than 10 minutes after starting the Task Sequence.
This information is provided as-is, you at your own risk.
Updated my HTA for creating AD groups and collections with a few tweaks and wanted to post the new version. I originally blogged an older version here. I had taken an HTA from SMSUtils and heavily modified it to do what I needed. I have since updated it with some additional appearance changes, and the big change is that I added support for R3’s “Dynamically Add New Resources” to the collection. You can now select that as an option to set when creating collections.
Updated to V1.6: Added sorting function to drop downs
Updated to V1.5: Added option to pick collection update times
Updated to V1.4: Some other formatting changes were made as well.
New support for ConfigMgr R3:
I also tweaked the logging window so that it’ll automatically scroll as you create multiple entries.
I hope you find this tool as useful as I have over the years.
I wanted to take some time to show you some of the power management reports that are provided with R3. There are quite a number of reports, however there are a few key ones that I think most people will want to use.
For all of these reports I will be showing data against my hyper-v environment. So you probably will see different data in your own test environment if you have physical machines, and for that matter, just more data in general.
I think one of the first ones that people will look at is the “Power Capabilities Report”, this report will show you the capabilities of the targeted systems.
“Power Computer Activity” is a neat one because it’ll show you when the computers are on, and when users are actually using the computers. It will also show you the monitor activity, however I don’t have data to show that from my virtual environment.
“Environmental Impact Report” displays a graph showing carbon dioxide emissions saved by a given collection over a specified time period.
“Power Consumption” displays the total computer power consumptions (in kW) for a specified collection over a specified time period.
“Power Cost” displays the total computer power consumption cost (in dollars) for a specified collection over a specified time period.
“Power Settings” displays an aggregated list of power settings used by computers in the specified collection. You can drill-down into this report to see a list of computers using specific power settings. (Note this is not the full report, there are many more options not in this screenshot)
This blog will cover the installation of ConfigMgr R3 into your lab environment as well as provide some additional information in regards to R3. R3 is still in beta, so I would not recommend you install it in production. I’ve actually been working with a client that is in the R3 TAP, so I wanted to post some information regarding R3 for the general public to get a glimpse as well, as I haven’t seen much information out there on R3 yet.
Please be sure to read the notes at the very bottom of this post as there is some really good information there that I haven’t seen listed anywhere else yet.
ConfigMgr 2007 R3 Beta Requirements:
- R3 beta can only be installed on a ConfigMgr SP2 environment
- R3 beta can only be installed on an evaluation copy of ConfigMgr. 2007 (this is fixed with the latest Beta refresh on Connect)
ConfigMgr 2007 R3 Main Features:
- Power Management (Server OS’s are not supported)
- Collection/discovery improvements
- New OEM task sequence media (pre-staged media)
- 300,000 Clients when using default settings
For a overview of R3, please see the attached documents from Microsoft.
This installation will be against a R2 environment, however, if you want to do a clean install, you can go straight to R3. R3 DOES include R2.
Once you extract out the download from Microsoft Connect, you will notice two files. One is the .exe for the R3 install, the second one is KB977384, which must be applied to your site server before the R3 install.
So here is our ConfigMgr Site, SP2 and R2 installed:
First lets get the KB installed:
In the middle of the install, you will also be prompted for what you would like to do with a patch for the ConfigMgr client:
Next we need to extract out the R3 install:
Next, we open up the splash screen and can read the notes, or install:
Now we can see that R3 is installed:
First, you’ll notice you have now have a “Power Management Client Agent” under Site Management – Site Settings – Client Agents:
You’ll need to enable this to start collecting data to show in the reports:
You will also now have a “Power Management” tab on Collection settings:
Initially you probably don’t want to enable this and start forcing power policies, you probably just want to collect some data for a few weeks to see how your systems are being used.
Here is some more information on the power settings you can apply:
Next we’ll want to configure the reports so you can view the data you are gathering, and preferably before you start enforcing policies. The reports are SQL Reporting Services only and have to imported.
Browse to “C:\Program files (x86)\Configuration Manager\Reports\Power Management”
And now you’ll see the new reports listed:
In terms of OSD, there is a new option available for pre-staged media, this is media containing both the operating system image and bootable media.
There is also a new feature to add resources to a collection:
If you are selected on a resource, you will have 2 new options as well:
“Add To Collection” adds the currently selected resource(s) to an existing collection. “New Collection” adds the currently selected resource(s) to a new collection.
R3 also enables you to have “delta” discoveries, there is a new “Enable Delta Discovery” option on the discovery methods. This allows for faster collection updates and for getting resources into collections quicker. This is a favorite feature of mine for AD System Group Discovery, if you are using AD groups for targeted software distribution.
There is also a setting on collections for adding in new resources as they discovered instead of waiting for a full collection evaluation.
Here are some additional notes as well to take into consideration.
- If user changes settings, R3 will set it back at the next power interval change
- If there are multiple Wakup Times, then the closest to midnight wins
- If there are in multiple collections, one with power settings, one without, the “non” power policy will take precedence
- Wakeup timer is a one-shot at time to wakeup
- Reports are SSRS only, there is a cab to import to show reports (demonstrated above)
- Focus for R3 is evaluating new sytems
- “Fast Evalualtion” setting on collections
- A new collection needs a full evaluation to show existing clients
- Collections are eval’d by periodically executing a query
- Results are inserted into temp table
- Table is merged with master collection results table (collectionmembers)
- If there is no change in results, master results table not changed
- If only a few resources have changed, evaluation process faster due to only processing changed resources
- “Dynamically add new resources” works for OSD, or first time a client sends in inventory, 5 minutes to discover, 5 minutes to update collection