Wednesday, January 18, 2012

Deploying System Center 2012

System Center 2012 Release Candidate
Microsoft is pleased to announce the availability of System Center 2012 Release Candidate. System Center 2012 provides comprehensive management from the desktop to the datacenter.
System Center 2012 helps you manage your IT environments across traditional datacenters, private and public clouds, client computers, and devices. Using these integrated and automated management capabilities, you can become a trusted service provider for your business. System Center 2012 Release Candidate empowers you with a common management toolset for your private and public cloud applications and services. System Center helps you confidently deliver IT as a Service for your business.


You run the Unified Installer to deploy System Center 2012 components.

The Unified Installer is only intended for distributing System Center 2012 Components for evaluation, testing or to setup a Proof of Concept.
You must install only one System Center component per server. Unified Installer will run only on Windows 7 SP1 or Windows Server 2008 R2 SP1.

You Choose what you want to Install.
Don't Install App Controller and Virtual Machine Manager on the same Server!

You need to extract the downloaded files into folders.
Allright, you will probably run into some missing software. So a good tips is to monitor the log file for the Unified Installer. Located here: %userprofile%\appdata\local\Microsoft System Center 2012\Unified Installer\Logs\
Depending on your choice you have to download some Prerequsite software.
I choose Configmgr and Orchestrator.
I have provided some links below for some of the software.

Microsoft .Net Framework 4 Extended Download:

Microsoft SQL Server 2008 R2 Service Pack1 Download:
UnZip so that it is in exe format.

Microsoft SQL Server 2008 R2 Cumulative Update 4 Download:
UnZip so that it is in exe format.

I'm remote installing to servers.
The Orchestrator Server need to have 2GB memory minimum.

I've also tuned firewall and UAC.

Then you need to get WinRM working.
This was the tricky part.
I installed my Orchestrator on a Server that was also a DC, so I had to configure the right Policys to get it working.
With these settings:
Important to get the 2 Allow Delegating Fresh Credentials settings correct.


On the Target machine I put it in a seperate OU and blocked Policyes, then used Local Policys to adjust the WinRM according to this

More info:


And the Installer is running...

No comments:

Post a Comment