System Center Journey

System Center 2019 – What’s new

Microsoft just launched Windows Server 2019 and Windows Admin Center, which also raised the interest in System Center 2019. At Microsoft Ignite, Microsoft was talking about what is new in System Center 2019, the future of System Center, and how it fits in with Windows Admin Center and other management tools.

Microsoft Cloud and Datacenter Management Story

Microsoft Cloud and Datacenter Management Overview

With Microsoft now offering a range of products to manage your Cloud and Datacenter environments, the question comes up “which is the best solution?”. It is not only depending on the size of your company, it also depends on which services you are using and what your job role is. Coming from the Azure site, you have Azure Security and Management, which allows you not only to manage your Azure resources but also integrates and extends with your on-premises environment. System Center is aimed to manage datacenter environments at scale, and Windows Admin Center helps you to dig deeper to manage individual servers or single cluster management. Both Windows Admin Center and System Center 2019, can be used side by side and both are integrated into Microsoft Azure.

System Center Windows Admin Center better together

System Center vs Windows Admin Center

I often get the question, does Windows Admin Center replace System Center? The answer to this is no, System Center is aimed to do management at a datacenter scale, while Windows Admin Center is giving you deep management access to a single server or clusters. In small environments you might end up using Windows Admin Center only, but in larger datacenter deployments, you are likely to use a combination of System Center and Windows Admin Center.

System Center 2019 Suite Improvements

System Center 2019 Focus

The System Center 2019 release focuses on three main areas. First of all, it adds more capabilities to the existing components and features which were requested by customers. Secondly, it brings integration for the next version of Windows Server, Windows Server 2019 and brings new Windows Server features to life in System Center. Last but not least, System Center 2019 adds more Hybrid Cloud integrations with Microsoft Azure.

SCU Savision Flyer

Are ITIL and System Center BFFs? – System Center Universe Europe

A couple of weeks ago I could finally announce the sessions about Hyper-V, Nano Server and Azure Site Recovery Manager I will present at System Center Universe Europe in Basel, together with some great speakers like Michel Lüscher (Microsoft), Carsten Rachfahl (Microsoft MVP) and Kristian Nese (Microsoft MVP). I am proud to announce that I will be part of another session hosted by Savision and Jonas Lenntun, CEO and Solution Architect at Approved Consulting. Together with other great minds, Kristian Nese, Kevin Greene, Robert Hedblom, I will answer the question “Savision: Are ITIL and System Center BFFs?”.

In the modern world where organizations are facing new challenges to be more competitive, they are looking for better ways to improve the quality and efficiency of their IT Service delivery using the ITIL framework. Gain valuable insights and best practices on how you can adopt the ITIL framework to Microsoft System Center and OMS from real world experiences together with Savision, Jonas Lenntun, CEO and Solution Architect at Approved Consulting, and Microsoft MVPs: Robert Hedblom, Kristian Nese, Kevin Greene and Thomas Maurer.

Book the session now into your session planer, and if you are not already registered for System Center Universe Europe in Basel, go for it!

System Center Logo

Update Rollup 3 for System Center 2012 R2 available

Today Microsoft released Update Rollup 3 for System Center 2012 R2. With the release Microsoft did not only fix some bugs they also added some features. Especially Data Protection Manager (DPM) and Virtual Machine Manager got some new features and fixes which will help especially in large scale Cloud and Virtualization deployments.

Data Protection Manager


  • Scalable VM backup
    This update rollup improves the reliability at scale for Virtual Machine (VM) backups on Hyper-V and Windows Server 2012 R2 infrastructures. This feature is supported on both Cluster Shared Volumes (CSV) and scale-out file server (SOFS) storage configurations for VM.
  • Backup and consistency check windowImportant This feature is supported only for disk protection for VM data sources.This feature, configured through Windows PowerShell, enables specific time windows to restrict backup and consistency check (CC) jobs. This window can be applied per protection group and will limit all jobs for that protection to the specified time window.After the backup job has ended, all in-progress jobs can continue. Any queued jobs outside the backup and consistency jobs will be automatically canceled.This feature affects only scheduled jobs and does not affect specific jobs that are triggered by the user.Windows PowerShell script examples

    are available on Microsoft TechNet. These examples show how to use PowerShell cmdlets to create the backup and consistency window.


    • This feature is not supported for tape or cloud protection jobs.
    • This feature is not supported for non-VM data sources.
    • Setting these windows is the same as running a Modify Protection Group workflow.
  • Support for synthetic fiber channel-to-tapeThis update rollup introduces support for the synthetic fiber channel-to-tape process. Follow the tape certification process

    for third-party tape devices when you use Data Protection Manager 2012 R2 and Windows Server 2012 R2.



  • A backup of a mirrored SQL instance fails if the principal SQL instance that was first backed up is now the mirror.
  • DPM console crashes while a recatalog or “mark as free” operation is performed on an imported tape.
  • The MSDPM service crashes when protected data sources have long names.
  • The DPMRA service crashes during replica creation when the database name on one of the SQL instances matches or is a substring of a SQL instance name that is hosted on the protected server.

More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Data Protection Manager

Virtual Machine Manager


  • This update includes a Linux guest agent upgrade to support the following new operating systems:
    • Ubuntu Linux 14.04 (32-bit)
    • Ubuntu Linux 14.04 (64-bit)
  • This update also includes the following:
    • Host DHCP extension driver upgrade
    • Several performance improvements
    • Several Management Pack package improvements



  • Total storage for a User role is reported incorrectly. For example, the User role can use only half of the allowed quota.
  • A host cluster update fails intermittently because of a locked job.
  • Virtual machine (VM) refreshers do not update highly available virtual machines (HAVMs) after failover to another node.
  • A cluster IP address for a guest cluster configuration in a Hyper-V Network Virtualization (HNV) environment is not updated correctly by using HNV policies during failover. For more information about this issue, see the following article in the Microsoft Knowledge Base:


    The cluster IP address in an HNV environment is updated incorrectly during failover

  • Server Message Block (SMB) shares may not be usable by high availability (HA) workloads if they are also connected to stand-alone hosts.
  • Storage objects discovery does not occur on a Virtual Machine Manager server if the discovery item is too big.
  • A Virtual Machine Manager job that assigns network service backend connectivity fails.
  • Enable maintenance mode fails when you evacuate failed-state VMs.
  • The Virtual Machine Manager service cannot be restarted because of database corruption.
  • The ZH-TW language incorrectly appears in the tooltip of the VM Network icon.
  • Library refresher rewrites the alternative data stream on every file during every update.
  • For iSCSI hardware storage-based array, when the MaskingPortsPerView property option is set to “multi-port per view,” the target endpoint is not obtained as the port address.
  • The virtual hard disk (VHD) is left in the source folder after storage migration is completed.
  • The addition of a bandwidth limitation to an existing virtual private network (VPN) connection is not added to the generated script.
  • A VM that is attached to an HNV VM network loses connectivity when it is live migrated to another node in the failover cluster that is not currently hosting other VMs that belong to the same VM network.
  • VM network shared access is lost after a service restart or an update interval.
  • The Remove-SCFileShare command fails for a network-attached storage SMI-S provider.
  • Setting the template time zone to UTC (GMT +0:00) is incorrectly displayed as “Magadan Standard Time.”
  • The System Center 2012 R2 Virtual Machine Manager crashes when you add groups that contain the at sign (@) character in User roles.
  • VM deployment fails in a VMWare environment when you have virtual hard disk (.vmdk) files of the same size in your template.
  • Deployment of an application host on HAVMM fails and generates a 22570 error.
  • Live migration of an HAVM cross cluster creates a duplicate VM role in the target cluster.
  • An error occurs when you apply physical adapter network settings to a teamed adapter.
  • A VMM agent crashes continuously when the HvStats_HyperVHypervisorLogicalProcessor query returns a null value.
  • A host refresh does not update the VMHostGroup value of a VMWARE cluster after the cluster is moved from VCENTER.
  • VMM reports an incorrect Disk Allocation size for dynamic VHDs that are mapped to a virtual machine.
  • A VMM service template script application does not work for a self-service role.
  • VM creation fails if Virtual Machine Manager undergoes failover during the creation process.
  • The Access Status value of a file share is incorrect in the user interface.
  • The Virtual Machine Manager service crashes because of an invalid ClusterFlags value.
  • VMs cannot be deployed from a service template to a cloud across multiple host clusters (multiple datacenters).

More information can be found on the Microsoft Page for: Update rollup 3 for System Center 2012 R2 Virtual Machine Manager

Orchestrator and Service Management Automation


  • When a runbook calls other runbooks, Service Management Automation (SMA) concatenates all the participating runbooks into a single script and then passes the script to the PowerShell Workflow engine for compilation. The resulting script may contain multiple signature blocks, and SMA receives a compilation error from the Powershell Workflow.
  • When child runbooks contain a signature block, the child runbooks cannot be compiled into inline runbooks. If there is more than one signature block, the resulting runbook will be corrupted.
  • Cmdlets should request information from the server, up to a limit on the number of records that are returned, and then request the next “page” of records, until all records are retrieved.
  • When a Windows PowerShell user uses the Set-SmaCertificate cmdlet, the user cannot receive private key information when he or she uses the Get-AutomationCertificate activity.
  • The Automation menu stops working in Administrator Portal, and you may notice that the Orchestrator ODATA API controller cannot return Modules data. Additionally, you receive the following error message:
    Message: The file exists.
    TypeName: System.IO.IOException
  • Service Management Automation (SMA) resources are paged. The cmdlets have to evaluate the response from the web service for the presence of a continuation token and then make a sequence of ListNext web requests if a continuation token is present.
  • SMA may not return the latest job ID for the runbook. The Invoke-ConfiguratorRunbook activity will have the job ID when it calls the Start-SMARunbook cmdlet, and the job ID should be returned to the caller. This occurs because SMA does not return the most recent job for a runbook. This issue occurs occur in a multiple-run scenario. If the configurator passes the first run, this issue has no effect.
  • The Orchestrator Runbook Service (RunbookService.exe) may crash, and you receive the following error message:
    Application: RunbookService.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ServiceModel.CommunicationException
  • If a runbook is large enough to exceed the default Windows Communication Foundation (WCF) channel size, an exception occurs. This issue causes the job to be stuck in the “New” state.
  • When Update Rollup 2 is uninstalled, the connection properties to the instance of Microsoft SQL Server are cleared.



More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Orchestrator

Service Manager


  • The Microsoft Systems Center 2012 Operations Manager configuration item (CI) connector does not retrieve disk mount point information for the Service Manager database.
  • When a service request is created from a request offering in the console and when every user prompt is of the Simple List prompt type, the console shows options from all simple lists in each user prompt.
  • When you try to close a customized change request, you cannot close the change request, the task throws an error, and the close is not actioned.
  • MPSync job failures that are logged to the event log do not contain enough information to allow for a quick diagnosis of the problem.
  • All Service Manager workflows may stall when any invalid XML characters (control characters) are used in a work item property.
  • Using the “Set First Response or Comment” task in a service request creates a “Private” flag that cannot be used for evaluation in a notification action log or a user comment update. This behavior occurs because the private flag is undefined.
  • If the configuration management database (CMDB) is down (that is, if it is offline or unable to connect because of network issues) at the time that the Health service is restarted and if the CMDB continues to be offline for a long time, the Health service may enter an unrecoverable state even if the database comes online again later.
  • Configuration Manager Connector synchronization may stop after Update Rollup 2 for Service Manager 2012 SP1 or Update Rollup 6 for Service Manager 2012 R2 is applied. This issue occurs when the connector tries to synchronize malformed or incomplete software version information from the Configuration Manager database.

More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Service Manager

Operations Manager


  • A deadlock condition occurs when a database is connected after an outage. You may experience this issue may when one or more HealthServices services in the environment are listed as Unavailable after a database goes offline and then comes back online.
  • The Desktop console crashes after exception TargetInvocationException occurs when the TilesContainer is updated. You may experience this issue after you leave the console open on a Dashboard view for a long time.
  • The Password expiration monitor is fixed for logged events. To make troubleshooting easier, this fix adds more detail to Event IDs 7019 and 7020 when they occur.
  • The Health service bounces because of high memory usage in the instance MonitoringHost: leak MOMModules!CMOMClusterResource::InitializeInstance. This issue may be seen as high memory usage if you examine monitoringhost.exe in Performance Monitor. Or, the Health service may restart every couple of days , depending on the load on the server.
  • The Health service crashes in Windows HTTP Services (WinHTTP) if the RunAs account is not read correctly.
  • Windows PowerShell stops working with System.Management.Automation.PSSnapInReader.ReadEnginePSSnapIns. You may see this issue as Event ID 22400 together with a description of “Failed to run the Powershell script.”
  • The PropertyValue column in the contextual details widget is unreadable in smaller widget sizes because the PropertyName column uses too much space.
  • The update threshold for monitor “Health Service Handle Count Threshold” is reset to 30,000. You can see this issue in the environment, and the Health Service Handle Count Threshold monitor is listed in the critical state.
  • An acknowledgement (ACK) is delayed by write collisions in MS queue when lots of data is sent from 1,000 agents.
  • The execution of the Export-SCOMEffectiveMonitoringConfiguration cmdlet fails with the error “Subquery returned more than 1 value.”
  • The MOMScriptAPI.ReturnItems method can be slow because a process race condition may occur when many items are returned, and the method may take two seconds between items. Scripts may run slowly in the System Center Operations Manager environment.
  • When you are in the console and click Authoring, click Management Pack, click Objects, and then click Attributes to perform a Find operation, the Find operations seems unexpectedly slow. Additionally, the Momcache.mdb file grows very large.
  • A delta synchronization times out on SQL operations with Event ID 29181.
  • Operations Manager grooms out the alert history before an alert is closed.
  • The time-zone settings are not added to a subscription when non-English display languages are set. Additionally, time stamps on alert notifications are inaccurate for the time zone.
  • Web Browser widget requires the protocol (http or https) to be included in the URL.
  • You cannot access MonitoringHost’s TemporaryStoragePath within the PowerShell Module.
  • The TopNEntitiesByPerfGet stored procedure may cause an Operations Manager dashboard performance issue. This issue may occur when a dashboard is run together with multiple widgets. Additionally, you may receive the following error message after a time-out occurs:
    [Error] :DataProviderCommandMethod.Invoke{dataprovidercommandmethod_cs370}( 000000000371AA78 )
    An unknown exception was caught during invocation and will be re-wrapped in a DataAccessException. System.TimeoutException: The operation has timed out.
    at Microsoft.EnterpriseManagement.Monitoring.DataProviders.RetryCommandExecutionStrategy.Invoke(IDataProviderCommandMethodInvoker invoker)
    at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethod.Invoke(CoreDataGateway gateWay, DataCommand command)

More information can be found on the Microsoft Page for: Update Rollup 3 for System Center 2012 R2 Operations Manager

System Center 2012 SP1 Update Rollup 1 Available

System Center Logo

After Microsoft released System Center 2012 SP1 the first update rollup is available which fixes some issues for some of the System Center components. With the System Center 2012 SP1 Update Rollup 1 (KB2785682) fixes also some issues with System Center 2012 – Virtual Machine Manager (SCVMM) and App Controller (SCAC).

You can get more information about what is fixed on the Description of Update Rollup 1 for System Center 2012 Service Pack 1 page.

Thanks to Michel Lüscher (Consultant at Microsoft Switzerland) for the link.



System Center 2012 SP1 RTM download available on TechNet and MSDN

System Center Logo

Finally System Center 2012 SP1 is available on TechNet and MSDN. This has been a release we all have been waiting for, since we could get Windows Server 2012 and Windows 8.

Service Pack 1 for System Center 2012 is not just a maintenance release, it also includes a lot of new features for all products and especially for Virtualization:

  • Virtual Machine Manager adds support for Windows Server 2012 Hyper-V, Network Virtualization, Advanced Networking Configurations, SMB Storage, Plugins and a lot more.
  • Data Protection Manager adds support for online backup to Windows Azure and also support for Windows Server 2012.
  • App Controller adds support for Windows Azure and Hoster VMs

And of course a lot more, so checkout the downloads on TechNet and MSDN.

System Center 2012 SP1 TAP Airlift @ here we go

System Center Logo

Some weeks ago I got the okay for the System Center 2012 SP1 TAP Airlift event in Redmond. Together with my fellows from itnetx gmbh, Marcel Zehner (MVP for System Center Cloud and Datacenter Management) and Stefan Roth (System Center Operations Manager Expert) and Michel Lüscher from Microsoft Switzerland. In the next hours we will catch our flight to Seattle and I am already exited to meet some great people and talk about the next releases of System Center.

What’s new in System Center 2012 Service Pack 1 Beta

System Center Logo

Some days ago Microsoft released the Beta of System Center 2012 Service Pack 1. With the Service Pack 1 beta Microsoft added a lot of improvements and features to the System Center 2012 suite. However not everything is included in the beta. Here is a list of new features in System Center 2012 Service Pack 1 Beta:

  • Virtual Machine Manager
    • Improved Support for Network Virtualization
    • Extend the VMM console with Add-ins
    • Support for Windows Standards-Based Storage Management Service, thin provisioning of logical units and discovery of SAS storage
    • Ability to convert VHD to VHDX, use VHDX as base Operating System image
  • Configuration Manager
    • Deployment and management of Windows 8 and Windows Server 2012
    • Distribution point for Windows Azure to help reduce infrastructure costs
    • Automation of administrative tasks through PowerShell support
    • Management of Mac OS X clients and Linux and UNIX servers
    • Real-time administrative actions for Endpoint Protection related tasks
  • Data Protection Manager
    • Improved backup performance of Hyper-V over CSV 2.0
    • Protection for Hyper-V over remote SMB share
    • Protection for Windows Server 2012 de-duplicated volumes
    • Uninterrupted protection for VM live migration
  • App Controller
    • Service Provider Foundation API to create and operate Virtual Machines
    • Support for Azure VM; migrate VHDs from VMM to Windows Azure, manage from on-premise System Center
  • Operations Manager
    • Support for IIS 8
    • Monitoring of WCF, MVC and .NET NT services
    • Azure SDK support
  • Orchestrator
    • Support for Integration Packs, including 3rd party
    • Manage VMM self-service User Roles
    • Manage multiple VMM ‘stamps’ (scale units), aggregate results from multiple stamps
    • Integration with App Controller to consume Hosted clouds
  • Service Manager
    • Apply price sheets to VMM clouds
    • Create chargeback reports
    • Pivot by cost center, VMM clouds, Pricesheets
  • Server App-V
    • Support for applications that create scheduled tasks during packaging
    • Create virtual application packages from applications installed remotely on native server

I will provide more impressions on products I could already work with, such as SCVMM, SCAC and SCDPM, as soon as I find some time.

System Center 2012 Unified Installer – Step by Step – Part 3

Microsoft System Center Logo
In the first two posts we did all the preperation for the System Center 2012 Unified Installer. Now in this post we are going finally to run the Unified Installer.


  1. Start the System Center Unified Installer
    System Center Unified Installer Setup
  2. The System Center Unified Installer is not made for production so read the warning and click okay.
    System Center Unified Installer Warning
  3. Choose the System Center components you want to install.
    System Center Unified Installer parts
  4. Set the component media Location for each System Center product
    System Center Unified Installer component location
  5. Accept the License Terms for Configuration Manager and the Prerequisite License Terms
    Coniguration Manager License Terms
    Prerequisite License Terms
  6. Choose the Prerequisite Meida Locations
    Prerequisite Media Location
  7. Specify the Installation Location
    Installation Destination Location
  8. Select the System Center Target servers
    System Center Servers
  9. Select System Center Service Accounts
    System Center Service Accounts
  10. provide some additional Setup information
    Coponent Specific Questions
  11. Check the summary and click install
    System Center Unified Installer Install
  12. Now the System Center Unified Installer will Setup the first Server with System Center Orchestrator
    System Center Orchestrator
  13. After Orchestrator is deployed, it will Launch some Orchestrator runbooks to install the other System Center parts.
    System Center Setup
  14. After all products are installed, SCUI will do a cleanup
    System Center Unified Installer Cleanup
  15. And about 3 hours later you are done
    System Center Unified Installer Summary

I think this is very cool and can you save a lot of time if you are doing a Proof of Concept or a Lab deployment of the System Center products.

System Center 2012 Unified Installer – Step by Step – Part 2

Microsoft System Center Logo

In my first post about the System Center 2012 Unified Installer I wrote about the prerequisites you need, to do a System Center 2012 deployment with the Unified Installer. In the second part I will write how you have to prepare the Installer and the Target servers.

It’s still important: Neither the System Center Unified Installer nor this guide is made to deploy the System Center Suite in production. It is only for lab or demo environments.

In my case I created two OUs to deploy my small lab. One for the Installer Computer and one for all the System Center servers. And I created some GPOs to save some time.

SC2012 InstallerSC2012 ServersSC2012 Servers GPO


Preparing the Installer Computer for System Center 2012 – Unified Installer

  1. First I installed a Server with Windows Server 2008 R2 SP1 as the installer Computer and installed all the patches which came with Windows Updates.
  2. Now you have to do some configuration of WinRM. You can do this via Group Policy or CMD commands.
    Computer Configuration / Administrative Templates / System / Credential Delegation / Allow Delegating Fresh Credentials (Enabled with the value: “WSMAN/*” and Concatenate OS defaults with input above selected)
    Computer Configuration / Administrative Templates / System / Credential Delegation / Allow Delegating Fresh Credentials with NTLM-only Server Authentication (Enabled with the value: “WSMAN/*” and Concatenate OS defaults with input above selected)
    Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WRM) / WinRm Client / Allow CredSSP authentication (Enabled)
    Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WRM) / WinRm Client / Trusted Hosts (Enabled with a * in the TrustedHostsList option)
    SC2012 Installer GPO
  3. You could also run the following comands
    winrm set winrm/config/client/auth @{CredSSP="True"}
    winrm set winrm/config/client @{TrustedHosts="*"}
    winrm qc
  4. Now you you have to open some Firewall ports, you can do this also via Group Policy or in the local Windows Firewall settings.
    Create a new Inbound role for the following ports:
    TCP 81
    TCP 1433
    UDP 1434
    ICMP v4
    Because it is a demo or lab Environment you could also disable the Firewall

On the User’s Guide for System Center 2012 – Unified Installer you can get more Information how you can prepare the Installer Computer.

Preparing a Target Servers for System Center 2012 Components

  1. First I installed a Server with Windows Server 2008 R2 SP1 as the installer Computer and installed all the patches which came with Windows Updates.
  2. Like for the Installer Computer we also have to create some GPOs for the Target Servers.
    Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow automatic configuration of listeners (Enabled and the for the values of IPv4 filter and IPv6 filter type *)
    Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow CredSSP authentication (Enabled)
    Computer Configuration / Administrative Templates / Windows Components / Windows Remote Shell / Allow Remote Shell Access (Enabled)
    Computer Configuration / Administrative Templates / Windows Components / Windows Remote Shell / Specify maximum amount of memory in MB per Shell (Enabled and set MaxMemoryPerShellMB to 2048)
    SC2012 SC Servers GPOYou could also run the following commands on the target servers.

    winrm qc -q
    winrm set winrm/config/service/auth @{CredSSP="True"}
    winrm set winrm/config/winrs @{AllowRemoteShellAccess="True"}
    winrm set winrm/config/winrs @{MaxMemoryPerShellMB="2048"}

Create Installer User and Service Users

SC2012 Service Accounts


I also created a Service Users for every System Center product, you could also just use the same user account for all products.

  • svc-sc2012-scvmm
  • svc-sc2012-scac
  • svc-sc2012-sco
  • svc-sc2012-scom
  • svc-sc2012-sccm
  • svc-sc2012-scsm
  • svc-sc2012-scdpm

SC2012 Installer Account


And I created a Installer User which has local Administrator rights on every machine. You also have to login to your Installer Computer and run the System Center Unified Installer with this account.

  • sc2012-installer

This was the last preperation post, in the next post the “Fun” Begins and we can fire up the System Center 2012 – Unified Installer

System Center 2012 Unified Installer – Step by Step – Part 1

Microsoft System Center Logo

With System Center 2012 Microsoft released another tool called System Center Unified Installer. The System Center Unified Installer is design to do an automated installation of all the System Center 2012 products in Demo or Lab environments. It is not designed to install System Center 2012 in productive environments, because most of the time you have to work on the existing infrastructure and you change things on productive systems which you should do manually and check if they work as expected.

But it is a good tool to deploy System Center for demos, testing and proof of concepts. Because it can install all System Center 2012 components in less than three hours fully automated. Still you have to do some preparation of the environment and your target servers.

System Center Unified Installer Process


In this series of posts I will show you how you can deploy System Center with the System Center Unified Installer with less effort as possible.

In part one of this blog series the focus will be the pre-requirements and the sources for a deployment with System Center Unified Installer.

  1. Download the System Center 2012 Suite. If you don’t have a license yet you can download the Private Cloud Evaluation Software.
  2. Download the following Prerequisites
    Prerequisite For
    Microsoft .NET Framework 4 SCAC
    Report Viewer Redistributable 2008 SCOM
    Report Viewer Redistributable 2010 SCOM
    Microsoft SQL Server 2008 R2 SCAC
    Microsoft SQL Server 2008 R2 Native Client SCVMM
    Windows Automated Installation Kit SCVMM
    Microsoft Analysis Management Objects SCSM
    Microsoft SQL Server 2008 R2 Command Line Utilities SCVMM
    SP1 for Microsoft SQL Server 2008 R2 SCCM
    Cumulative Update Package 4 for Microsoft SQL Server 2008 R2 SP1 SCCM
  3. Now as the last step you have to unpack System Center 2012 and the prerequisites to your installer Computer. I created a Source Folder with the subfolders SC2012 for all the System Center Products and a subfolder Prereq for all the Prerequisites.
    System Center Unified Installer 2012System Center Unified Installer 2012System Center Unified Installer 2012So of the downloads you have to uncompressed using the command <filename>.exe /x:C:\Source\Prereq\<software>
    For example:
    – SQL Server 2008 R2
    – SQL Server 2008 R2 Service Pack 1
    – SQL Server 2008 R2 SP1 CU4
    – System Center App Controller

Now this was step one of the preperation. In the next part I will write about how you have to setup the Installer and the Target servers.

Links for the Unified Installer: