A WordPress.com site dedicated to System Center and Cloud Management

I encountered this error while attempting to install the System Center Data Protection Manager (DPM) Central Console on my Operations Manager (SCOM) Management Server.

DPM Central Console Installation Error

I was following this TechNet article: http://technet.microsoft.com/en-us/library/hh758189.aspx.

The TechNet article lists 2 steps for this process, namely Install the Operations Manager agent, and Install Central Console.

Of interesting note, the second step within the Install the Operations Manager agent step says:

After you install the Operations Manager agent, set the following registry key – [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules\Global\PowerShell] “ScriptLimit”=dword:0000000f. After you modify this setting, restart the Health Service (System Center Management).

However, after I installed the SCOM Agent, this registry entry was not present. In fact, the Registry Key only went as far as: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules. But, after walking through the installation of the Central Console on the Operations Manager (SCOM) Management Server (although the installation failed, more on that in a bit), only then did this Registry entry appear on the DPM server.

That aside, according to the error message, let’s check out the DPMCentralConsoleSetup.log file. Looking through the log file, we find this:

MSI (s) (6C:04) [21:14:27:148]: Product: Microsoft System Center 2012 – DPM Remote Administration — Microsoft Visual C++ 2008 Redistributable is not installed on this computer. You can download it from http://go.microsoft.com/fwlink/?LinkID=120135

That’s interesting. Especially when I specifically installed the Visual C++ 2008 Redistributable, since without it, you will encounter this error when first running the Central Console installer.

DPM Visual C++ Not Installed

However, if you navigate to the URL provided, you will end up at the download page for the Microsoft Visual C++ 2008 Redistributable Package (x64). Note the x64 part.

But what is interesting is, if I install the x86 version of the Visual C++ 2008 Redistributable, this error no longer appears and I can continue with the installation. However, it’s not until the end of the attempted installation that the previously mentioned error occurs, and the log file states that the Microsoft Visual C++ 2008 Redistributable  is not installed.

So, I downloaded the x64 version of the C++ Redistributable, installed it, then attempted the DPM Central Console installation again. The result?

DPM Central Console Installation Complete

And if we launch the Operations Manager (SCOM) console, we will now see the monitoring for System Center 2012 R2 Data Protection Manager. Notice that we can get details on specific workloads (i.e. Exchange, Hyper-V, SharePoint, SQL Server), along with state data on the disks, protection groups, and tape drives/libraries.

SCOM DPM Monitoring



As always, if this post helped you in any way, and you would like to show your appreciation, please rate it and comment on it. Also, feel free to contact me (via the About Me page) with requests for future articles.

As requested by one of my readers, the following is an article on integrating App-V with SCCM 2012 R2 along with Virtual Environments.

For reference, here are some resources on the subject:




The following steps are from the following TechNet article (http://technet.microsoft.com/en-us/library/jj591609.aspx), with the addition of screenshots by me.

How to Create App-V Virtual Environments in Configuration Manager

Microsoft Application Virtualization (App-V) virtual environments in Microsoft System Center 2012 Configuration Manager enable deployed virtual applications to share the same file system and registry on client computers. This means that unlike standard virtual applications, these applications can share data with each other. Virtual environments are created or modified on client computers when the application is installed or when clients next evaluate their installed applications. You can order these applications so that when multiple applications try to modify a file system or registry value, the application with the highest order takes priority.

To create an App-V virtual environment

In the Configuration Manager console, click Software Library.

SCCM - Software Library

In the Software Library workspace, expand Application Management and then click App-V Virtual Environments.

SCCM - Software Library - AppV Virtual Environments

In the Home tab, in the Create group, click Create Virtual Environment.

SCCM - Create Virtual Environment

In the Create Virtual Environment dialog box, specify the following information:

Name: Specify a unique name for the virtual environment with a maximum of 128 characters.

Description: Optionally specify a description for the virtual environment.

SCCM - Create Virtual Environment (Dialog)

Click Add to add a new deployment type to the virtual environment. You must add at least one deployment type.

In the Add Applications dialog box, specify a Group name of up to 128 characters that you will use to refer to this group of applications that you add to the virtual environment.

SCCM - Add Applications (Dialog)

Click Add, select the App-V 5 applications and deployment types that you want to add to the group and then click OK.

SCCM - Specify Application (Dialog)

In the Add Applications dialog box, you can click Increase Order or Decrease Order to specify which application will take priority if multiple applications attempt to modify file system or registry settings in the same virtual environment.

Click OK to return to the Create Virtual Environment dialog box.

When you have finished adding groups, click OK to create the virtual environment. The new virtual environment is displayed in the App-V Virtual Environments node of the Configuration Manager console. You can monitor the status of your virtual environments by using the report App-V Virtual Environment Status.

NOTE: The virtual environment will be added or modified on client computers when the application is installed or when the client next evaluates installed applications.

As always, if this post helped you in any way, and you would like to show your appreciation, please rate it and comment on it. Also, feel free to contact me (via the About Me page) with requests for future articles.

In our previous post, we completed the Installation of the SCSM 2012 Dashboards by Signature Consultancy. In this post we will walk through the process of Publishing the Dashboards in SharePoint.

Portal Publishing – Signature SCSM dashboard Publishing Procedures

IMPORTANT: These steps should be performed in SharePoint. You need to have SharePoint administrative privileges to do the configuration.


Start by first accessing the SharePoint Central Administration site.

SCSM Dashboards - 01 - SharePoint Central Administration

From the menu, select Site Actions, and click New Site.

SCSM Dashboards - 02 - Site Actions - New Site

In the Create dialog, under All Categories select “Blank & Custom“, and then select “Blank Site“. For the site Title type “SCSM Dashboard“, and for URL Name type “SCSMDashboard“, then click Create.

SCSM Dashboards - 03NEW - Site Actions - New Site - Create

Once the new website is created, from the menu, select Site Actions > More Options.

SCSM Dashboards - 04 - More Options

In the Create dialog, under All Types, select Page, select Web Part Page, then click Create.

SCSM Dashboards - 04 - Page (Web Part)

On the New Web Page Part screen, under Name type “IncidentManagement“. Under Choose A Layout Template select “Header, Footer, 3 Columns“.

NOTE: If you don’t already have a Document Library to contain the new page in, you will need to create one (which I will document in the next steps).

SCSM Dashboards - 06 - New Web Part Page

On the New Document Library screen, type a Name and then click Create.

SCSM Dashboards - 07 - Document Library

Back on the New Web Part Page screen, click Create.

You should now be on the Design view of the New Web Part Page. Under the Header section, click “Add A Web Part“.

SCSM Dashboards - 08 - New Web Part Page - Design

Under the Categories section, select Media and Content. Under the Web Parts section, select Page Viewer, then click Add.

SCSM Dashboards - 09 - Add Web Part

After the Page Viewer Web Part has been added to the page, click on the “Open The tool Pane” link to customize/configure it.

SCSM Dashboards - 10 - Open The Tool Pane

Under the Page Viewer configuration, under ‘Link‘, paste the full URL link to the Incident Management Report, then click OK.

NOTE: Under the ‘Appearance‘ and ‘Layout‘ areas you can change the specifications to meet your resolution and appearance needs.

As an example, in my lab environment this is: http://scsm-dw/Reports_SCSMDW/Pages/Report.aspx?ItemPath=%2fSCSM+Dashboard%2fIncidents+Management.

SCSM Dashboards - 11 - Page Viewer Link

Repeat the steps followed thus far to add new pages, one for each report (i.e. Activity Management, Change Management, and Problem Management).

Back on the SCSM Dashboard Portal Page, from the Site Actions menu, select Site Settings.

SCSM Dashboards - 13 - Site Actions - Site Settings

Under the Site Settings area, within the Look And Feel section, click on the Top Link Bar link.

SCSM Dashboards - 14 - Site Settings - Look And Feel (Top Link Bar)

On the Site Settings > Top Link Bar screen, click the New Navigation Link.

SCSM Dashboards - 15 - Site Settings - Top Link Bar - New Navigation Link

On the New Navigation Link screen, under the ‘Type The Web Address‘ specify the full URL Link per Report. For the ‘Type The Description‘ field, type the name of the report, then click OK.

NOTE: This is NOT the URL to the .RDL report file that we uploaded to the Data Warehouse Report Server. But rather, the web page that we created under “New Web Part Page” for each process (i.e. Activity Management, Change Management, Incident Management, and Problem Management).

For example, in my lab my URL for Incident Management is as follows: http://scsm-ssp:40917/SCSMDashboard/SCSMDashboardLibrary/IncidentManagement.aspx

SCSM Dashboards - 16 - New Navigation Link - Add

Now that we have an individual page linked to each .RDL report file, when you click on the link in the top menu, the report will load/be generated.

NOTE: In my lab example, I didn’t have any Incident Tickets to be reported on.

SCSM Dashboards - 17 - Incidents Management Report - Sample


As always, if this post helped you in any way, and you would like to show your appreciation, please rate it and comment on it. Also, feel free to contact me with requests for future articles.

Tag Cloud


Get every new post delivered to your Inbox.

Join 62 other followers

%d bloggers like this: