Building a lab environment with System Center Unified Installer – Part 2

May 8, 2012 at 4:00 am in Uncategorized by timdk

In the first part of the series we have outlined the requirements and the topology for the lab environment. Now we will start preparing the environment in which the System Center Unified Installer will be run.

Server Preparations

Except for the DC1 all virtual servers are configured with the following specs:
– 2 x CPU
– 2 Gb RAM
– 40 GB Hdd (SYSTEM)
– 1 NIC connected to the virtual switch (private)

Note: do not configure these systems with less then 2 CPU’s and 2 Gb of memory or the Unified Installer configuration wizard will not allow you to continue with the installation.

The DC1 server is configured as follows:
– 1 x CPU
– 512 Mb RAM
– 40 Gb Hdd (SYSTEM)
– 1 NIC connected to the virtual switch (private)

Base configuration for all 4 machines:
– Windows Server 2008 R2 with Service Pack 1
– Networking configured (see topology figure in part 1 for details)
– .Net Framework 3.5.1 feature is enabled

Domain Setup

The DC1 server is promoted to become a domain controller for the Sandbox.Lab domain. DNS is installed and configured at the same time. For future purposes DHCP is also installed on the DC1 server.

Additionally an Organizational Unit called Servers\SC2012 was created. This is where the following computer objects will be placed: OR1, CM1 and OM1.

As this is a lab environment I decided to turn off the Windows Firewall on the machines. For this I implemented a GPO called “SC2012 srv config”. The FW configuration is done as follows: go to Windows Settings > Security Settings > Windows Firewall, then open properties and on the domain profile tab set firewall state to "Off".

Preparing the installer PC

The Installer PC will be the actual Orchestrator machine in the lab environment.

To make it possible for the remote boot strap process to complete successfully, some local policies need to be modified:

  • Computer Configuration / Administrative Templates / System / Credential Delegation / Allow Delegating Fresh Credentials
  • Computer Configuration / Administrative Templates / System / Credential Delegation / Allow Delegating Fresh Credentials with NTLM-only Server Authentication

The detailed procedure on how to do this is available here.

Preparing the target PC’s

Keep in mind that the Orchestrator machine in our scenario is not only the Installer PC, at the same time it is also a target PC.

Also here some local policies will need to be modified, for this we will update the “SC2012 Srv Config” GPO that was created earlier:

  • Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow automatic configuration of listeners
  • Computer Configuration / Administrative Templates / Windows Components / Windows Remote Management (WinRM) / WinRM Service / Allow CredSSP authentication
  • Computer Configuration / Administrative Templates / Windows Components / Windows Remote Shell / Allow Remote Shell Access
  • Computer Configuration / Administrative Templates / Windows Components / Windows Remote Shell / Specify maximum amount of memory in MB per Shell

The detailed procedure on how to implement is available here.

Additionally you will need to run the following commands on each machine:

  • 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"}

This concludes the preparations – at this point I would recommend to take a snapshot of the entire virtual environment.

Preparing the installation sources

Once the basic infrastructure is ready we need to prepare the installation sources. We will need all System Center 2012 product binaries and all binaries for any prerequisites needed to complete the installation of those products. Additionally we will need the binaries for SQL Server 2008 R2 binaries plus Service Pack 1 and CU4.

At MMS 2012 the attendees were handed out a USB stick with all the required sources to deploy a lab environment. So we were lucky enough not having to download and prepare all sources. This is how the layout of the USB stick looks like. It gives an idea on how you could structure the binaries as you download them:

This is the root of the drive, you will only need the marked folders:
image

These are the contents of the prerequisites folder, the names are self-explaining:
image

And these are the contents of the SystemCenter2012 folder. For our lab scenario only the marked ones are required:
image

Make sure that all binaries are available on the installer PC, in our lab this will be the OR1 machine which will be running System Center Orchestrator.

That’s it for now.

In the final part of these series we will walk through the Unified Installer installation process.

Tweet about this on TwitterShare on LinkedInEmail this to someonePrint this pageShare on Google+Digg thisShare on RedditShare on Facebook