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:

Hyper-V Virtual Machine Error 0x80070569

If you find you are getting a similar error 0x80070569 on Hyper-V 2012, you might be experiencing something similar to this.

So I jumped on to one of my Hyper-V hosts the other day to bang out a fresh Virtual Machine. I clicked on Create New Virtual Machine and BAM!, I get this error.


30-04-2013 6-11-55 PM


Try restarting the Hyper-V Virtual Machine Management Service.

I wasn't sure if I could restart this service while I had Virtual Machines running, but since it was on my home lab environment, I thought I'd give it a shot. The service restarted with no issues on any of my virtual machines. What's more, when I tried to create a virtual machine, it worked, no error. I'm not sure why this happens or why restarting the service fixes it as it seems by the error to be a permissions issue but as a work around it seems to do the trick.


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!