During the past couple of months I have been working with ConfigMgr 2012 RC2 in many ways. Now on in the past couple of days I decide to install the product with a SQL Server 2008 R2 in cluster. One of my problems was that I don’t own any storage unit or SAN where I can create some LUN(Logical Unit Number) to be shared on my cluster servers. So here is what I did to solve my problem of the SAN
- Hyper-V on Windows Server 2008 R2
- Create 1 VM with Windows Server 2008 R2 and set it up as Domain Controller
- Create 1 VM for Storage
- Steps to Create a Virtual Machine on Hyper-V
- Memory = 2048
- CPU = 1
- IDE Hard Drive = SANC.VHD Size = 210.00 GB
- Add 1 SCSI Controller
- Add 1 HD = SanStorage.vhd Size = 200GB
- OS to Install
- Windows Storage Server 2008 R2
Once your virtual machine finishes the installation you most install Microsoft iSCSI Software Target 3.3.
Create the drive needed on the Storage OS where you going to Create the VHDs
Configure the iSCSI Target and Storage
Create the Virtual Disk: Under “devices” in the iSCSI Target MMC, Create the VHDs that will be used for the cluster environment:
Disk Created for this LAB:
- 5GB VHD for Quorum
- 5GB VHD for MSDTC
- 75GB VHD for SQL Data
- 50GB VHD for SQL Logs
Create the iSCSI Target: Above the “devices” node as show on Figure 1.0 in the node “iSCSI Targets” Right click this node and choose “New iSCSI Target” to start the wizard.
Add the storage devices to your target. Right click your new target and add the storage created.
Later on when you finish installing and configuring your cluster nodes you will need to install and configure iSCSI initiator.
Figure 1.0 iSCSI Targer on Windows Storage Server 2008 R2
Now that have been complete the install of the Storage in Windows Storage Server 2008 R2 you need to configure the NIC Card with the correct ip address for this lab the SAN IP Address is = 192.168.2.2, now let’s complete the installation of the Cluster nodes so we can add these new storage to them.
- Windows Server 2008 R2
- VM Configuration: You will need to configure this 2 times 1 for each cluster node.
- 2048 Memory
- 1 VHD with 40 GB for C Drive
- 4 Virtual processors
When the Operating System finishes installing, join the 2 nodes to the Domain
- Install iSCSI Initiator
- Discover the storage server by entering the IP Address or DNS Name and click Quick Connect
- Go to the Volumes and Devices section and it should display the LUNS. At this point the storage will show on Disk Management.
Remember do this on each node.
Install the Failover cluster Feature on each node
Now let’s install SQL Server 2008 R2 on each node.
Before installing SQL Server 2008 R2 make sure that .net 3.5 framework is installed on each node and they are up to date on software updates.
- Installing a SQL Server 2008 R2 Failover Cluster
- Download SQL Server 2008 R2 Service Pack 1
- Apply Service Pack 1 on the SQL Server 2008 R2 Cluster
- Download SQL Server 2008 R2 SP1 CU4
To Install the SQL Server 2008 R2 SP1 CU4 you most follow the same process as the Apply Service Pack 1 on the SQL Server 2008 R2 cluster. This is to apply Hotfixes on each passive node first before applying them into the Active node.
Now let’s double check what we have done so far
- Install and Configure Domain Controller
- Install Windows Storage Server 2008 R2 with iSCSI Target in a Virtual Machine
- Install and Configure 2 Nodes with Windows Server 2008 R2
- Install and Configure SQL Server 2008 R2
- Apply Service Pack 1 for SQL Server 2008 R2
- Apply Cumulative update 4 for SQL Server 2008 R2 SP1
We are ready to Install System Center 2012 Configuration Manager with the SQL Cluster
- .Net 4 Download
- System Center 2012 Configuration Manager RC2 Download
- Windows Server Update Service Role Installed
- Application Server Role Installed
- Webserver Role Installed
- Web-WMI Feature Enable, WebDAV Enable
- Background Intelligence Transfer Feature Installed
- Remote Differential Compression Feature Installed
- Branch Cache Feature Installed
- Schema Extended for Configuration Manager 2012 More Details here
- Log on to AD using Schema Master and run <ConfigMgrSourceFiles>\SMSSETUP\BIN\i386\extadsch.exe
- Open the ExtADSch.log to validate the schema has been extended.
- Create the System Management container. On the System OU in AD
- Set security permissions on the System Management container for this and all child objects
- Configure SQL Server Minimum Memory and Maximum Memory. Details
- Ports Need by ConfigMgr 2012 for this installation we are turning off Firewall but if you don’t want to turn it off please make rules for port 4022 and 1433.
- Validate that ConfigMgr Server is part of the local administrators group on each node
For Central Site Server and Primary Site is recommended a Minimum Memory Allocated of 8GB and for Secondary Site 4GB.
To validate that you have all the necessary configurations implemented you can run the Prerequisite checker.
prereqchk.exe that is located at <ConfigMgrSourceFiles>\SMSSETUP\BIN\X64
Now let’s start installing System Center 2012 Configuration Manager
Let’s run the Splash.hta located at <ConfigMgrSourceFiles>
When this splash come up click on Install
When the Microsoft System Center 2012 Configuration Manager Setup Wizard comes up click on Next
Then let’s click on Install a Configuration Manager Primary Site and click next
Figure 1.1 Install a configuration manager primary site
Click on Install this product as evaluation. You will have the ability to test this product for 180 days since is on RC2 stage this should be fine for us to test it in our labs.
Click Accept this license terms and click Next
On the next screen accept all license statements and click Next
Figure 1.2 Download the prerequisite to a location
On the Figure 1.2 specify a folder to download the prerequisite from internet if you have already downloaded this click on use previously downloaded files. Click Next and the process will begin to download the prerequisites or will validate them depending on what option you have selected.
Once finish the prerequisite section you will continue the setup wizard and will be on the Server Language Selection.
Figure 1.4 Server Language Selections
On the Figure 1.4 you see what are the current language that are supported on this version let’s leave it as default and click Next.
On the client supported languages click next and leave is as default for now, if there any special language that you need go ahead and select them and click Next.
Now you must be on the Site and Installation Settings:
Site Code = STD
Site Name = Contoso HQ Primary Site
Installation Folder = Default or where you want to install the product
Ensure that the Install Configuration Manager Console is selected and click Next
Figure 1.5 Stand Alone or join to CAS
In the figure 1.5 you see that you can join this server into a current hierarchy, this means you can enter the Central administration site and this server will be joined into their hierarchy. Since we are doing a stand-alone installation go ahead and select install the primary site as stand-alone site.
Click Next and you will be warned that you have select to install this site server as stand-alone and you won’t be able to join it to the central administration time if you need it later. If you want to continue lets click yes if you don’t click NO. I advise you to review this specific setting correctly and if your hierarchy will need a CAS go ahead and install the CAS first before installing the primary site server role. Click on Yes on this case to continue.
Figure 1.6 Database Information
Once you get into the Database information as show on Figure 1.6 you need to enter the details of the SQL Cluster we have configure here
Service Broker port is not in use by another SQL Instance, therefor if you use a Shared SQL Server Cluster you most ensure that the SSB Port is changed for other databases or change the SSB port for Configuration Manager to use something else.
Once finish entering the database information click Next
This will complete the input configuration and will now go and check for final prerequisite checker.
Figure 1.7 Prerequisite Check
To fix the issue of the SQL Memory you need to follow the steps outlined here to remediate the Minimum allocated and maximum memory for SQL Server.
Now click on Begin Install and wait for the installation to be completed.
You can also view the log file ConfigMgrSetup.log or click on View Log.
If you need more details about the ConfigMgr 2012 you can use the TechNet Library.