SCCM 2012 R2 – MDT 2013 UEFI OS Deployment Error

I recently upgraded to SCCM 2012 R2 and also upgraded to MDT 2013 to take full advantage of its OS deployment goodies. Everything has been going well until I decided I’d like to deploy an OS to a 2nd Generation Hyper-V Virtual Machine. I started getting all sorts of different errors. It really started driving me insane. A lot of four letter words were used. For that I am sorry. Good news is, I got it working in the end.

Here are some of the errors that I was receiving. Sometimes it would error before it pre staged the WINPE image, sometimes after. Sometimes after a reboot.

I received a (0xC00000005) error.


A generic memory error.


An “Unable to find a raw disk that could be partitioned as the system disk” error that resulted in a (0x8007000F) error.


And the weirdest one I got, was after the partitions and disk had been setup and SCCM rebooted, it came up with a 0xc0000359 error saying the storvsc.sys was missing.



By this time I’d be round and round and round in circles. It’s then I found a blog post that showed me to change the Partition Variable for the OSDisk from OSDTemporaryDrive to OSDisk. This is apparently set by default to OSDTemporaryDrive in MDT 2013. Seems like a bit of a fail to me L Could I please have a day and half of my life back please Microsoft. That is all.

In the task sequence, look in the Initialization folder for the 4 different format and partition steps.

If you look at the OSDisk partition, you’ll find that its variable is set to OSDTemporary Drive.


Change this to OSDisk.

That’s all you need to do.




SCCM 2012 SSRS Error – DataSource Reverts

I was mucking around in my test lab tonight and managed to break SSRS (again) on my SCCM 2012 installation again. I was getting the following error.

  • “An error occurred during client rendering.
    • An error has occurred during report processing. (rsProcessingAborted)
      • Cannot impersonate user for data source ‘AutoGen__5C6358F2_4BB6_4a1b_A16E_8D96795D8602_’. (rsErrorImpersonatingUser)
        • Log on failed. (rsLogonFailed)
          • For more information about this error navigate to the report server on the local server machine, or enable remote errors ”


I worked out that I could go into the Report via the Reporting Website, create a new Datasource, and then it would work fine again….until, SCCM reverts the permissions back every 10 minutes to what is stored and encrypted in the SSRS Database. I then thought uninstalling the Reporting Services point and re-installing SSRS would do the trick. But it didn’t change anything. As soon as the Reporting Services point was back up, I started getting the same issues.

To get it to work, here are the steps I used…

  • I recreated the account that the Reporting Services Point was using to connect to the Reporting Server. (Not sure if this needs to be done, or whether the next step fixed it completely….)
  • I then changed the following registry key HKLM\SOFTWARE\Microsoft\SMS\SRSRP\SRSInitializeState key
    on the Site Server to a value of 0. This re-imports the all of the Reports again.

Check the SRSRP.log file to see what is happening under the hood.

Looks like something is going to happen?

Sure enough, all the reports start to rebuild. This also seems to recrate the DataSet / DataSource for the connection which seems to get rid of that error!

Assigning Users to ConfigMgr ReportUsers group in SCCM 2012

I have found that delegating permissions so that specific users are only allowed to view reports in SCCM 2012 can be a little tricky. I wanted to be able to add an Active Directory group to the ConfigMgr ReportUsers group in SCCM 2012. Then these users could simply view certain reports but not be able to build, create, edit or manage those reports and also not have access to the ConfigMgr Console. I think that’s a reasonable request. After all, one of the benefits of combining the reporting services point with SSRS in 2012 is being able to view the reports through the web console. Here is a little rundown of the pain that I’ve been through troubleshooting this issue.

I tried setting the permissions via the Web Console. I thought I could set the permissions and then those permissions would propagate down to the lower folders. This is the default behaviour after all.

Unfortunately, the permissions didn’t propagate. Not only did they not propagate, but I found that if I manually went through and set the permissions on the sub folders, within 10 minutes or so, those permissions would revert back to default. This mad me sad, and angry. But mostly sad.

So I thought I better do a little fishing, I decided to check the SRSRP.log file on the ConfigMgr server to see if could find out what was going on. I found this.

It turns out that SCCM is checking every 10 minutes or so, to see if the permissions are the same with what is in SCCM. If the permissions have changed in the Web Console, SCCM promptly changes them back.

So then, how do we assign user to the ConfigMgr Report user group?

In order to get it working here are the steps that I needed to follow. First, create the group that you would like to delegate the privileges to in Active Directory Users and Groups. Fill that group with the users you would like to delegate access to.

In the SCCM console, navigate to Administration > Security > Security Roles and COPY the Read-Only Analyst role.

You will now need to go through each individual permission and make sure run report is the only permission assigned. This will take a long time. The other option is to just associate the Read-Only Analyst role. This might give more permissions than you would like to give however. That’s up to you.

Now in the SCCM console, navigate to Administration > Security > Administrative Users. Right click Administrative Users and click Add User or Group.


Fill out the wizard. Leave the Collections and Security Scope as default.

Now go back to your web browser to check that the permissions have applied. It might take up to 10 minutes to resync. You can check the log file if you like. CMtrace.exe is a tail log viewer so it will update in real time.

You should see your group listed with the rights ConfigMgr Report Users. Now your users can view reports without breaking anything! Woohoo!

You can find more information on Reporting Services in SCCM 2012, here >









App-V – Installing the App-V 5.0 Sequencer

Before you get started on installing the App-V 5.0 Sequencer, there are a few things that you may have to do to get your environment ready.

  • Create a Windows 7 Virtual Desktop machine with 2 partitions eg. C:\ and Q:\. This will be used to create the App-V packages. It is recommended that the Sequencing Workstation be on the OS that is the lowest that is used in your environment. (In this case, in my test environment, I don't really have anything older than Windows 7, Windows 2008 R2.)
  • Download the Desktop Optimization Pack 2012.
  • Make sure .NET 4.0 is installed. (If Windows 7)
  • Powershell 3.0 (If Windows 7)
  • Make sure KB2533623 is installed. (If Windows 7)

Guide – Step by Step

On the Windows 7 workstation, mount the Desktop Optimization Pack DVD, and then select Application Virtualization for Desktops.

Select the App-V 5.0 Sequencer.

Click Yes.

Make sure .NET 4.0 is installed.

Make sure Powershell 3.0 is installed.

Make sure KB2533623 is installed.

Click Install.

Click Next.

Join the CEIP.

Click Close.


More info can be found here:

Uninstalling & Reinstalling SQL Server Reporting Services 2012

​I had some issues with uninstalling and reinstalling Microsoft SQL Server 2012 Reporting Services in my SCCM Lab environment. It turns out there are a few steps not mentioned in the microsoft documentation that you need to do in order to do a fresh install, without carrying any configuration settings over from the previous install. Here are a few dot points on what I had to do.

  • Remove the Reporting Services Point from SCCM
  • Appwiz.cpl > Microsoft SQL Server 2012 > Remove > Remove Reporting Services
  • Manually delete the ReportServer Database and the Temp Report Server Database
  • Delete the C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER) folder.
  • Reboot
  • Reinstall SQL Server Reporting Services and select install only during the installation.
  • Open up Reporting Services Configuration Manager and configure your accounts.
  • Make sure that the Websites are set in Reporting Services Configuration Manager or you won’t see a Sql Instance when you try to create the Reporting Services point in SCCM.


Report Builder 3.0 Fails to Install

If you find that the Report Builder 3.0 Click Once Application fails to install, you might have the same issue I have had in this blog post.


I tried to create a Report in SCCM and when the ClickOnce Application for Report Builder 3.0 tried to install it got this error.


WOW, soo helpful, thanks Microsoft! Click on Details, and you will get some more helpful information. Scan the log file for something similar to below.



    Below is a summary of the errors, details of these errors are listed later in the log.

    * Activation of http://<server>/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application?http://<server>/ReportServer/ConfigMgr_MTL/Hardware%20-%20Memory/Memory resulted in exception. Following failure messages were detected:

        + Unable to install this application because an application with the same identity is already installed. To install this application, either modify the manifest version for this application or uninstall the preexisting application.

This is most likely generated because you have installed Report Builder 3.0 once before. To fix this all you need to do is to clear the Click Once Application cache. Open up a command prompt and then type the following "rundll dfshim CleanOnlineAppCache" **NOTE** this command is case sensitive, I found that I had to type it exactly.

Now try again to Create or Edit a report.

Hope this helps!




Windows Assessment and Deployment Kit – Stuck at 0% Complete


Windows Assessment and Deployment Kit – Stuck at 0% Complete?

If you are installing the Windows Assessment and Deployment Kit and find yourself stuck at Overall Progress: 0% complete. You may start to think that the Windows Assessment and Deployment Kit installer isn't working and has crashed.

Windows Assessment and Deployment Kit Window

To make sure things are still ticking along under the covers, you can navigate to %temp%/adk to look at the installation log file to make sure that things are still progressing behind the scenes. The installation can be quite large up to 5.1 GB, so if you are on a slow internet connection, you may be stuck at 0% complete for up to 15 mins or more before you see any change in the progress bar. In the log file, look for the time that you kicked off the installation and also the time of the last log entry. You should be able to see some activity, namely 'acquiring package'. This will mean that it's downloading the package in the background.

Windows Assessment and Deployment Kit Log File

My installation took about 15 mins before I started to see any movement. My internet connection was saturated at that time, so that is why it took so long for me.

Windows Assessment and Deployment Kit Window 2


Where can I get it?

You can download the Windows Assessment and Deployment Kit installation file here.

You can also find more information about installing the Windows Assessment and Deployment Kit at Microsoft's site, here.