Your browser (Internet Explorer 6) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.
X
Aside

Hydration Kit for ConfigMgr 2012 SP1 (with Windows Server 2012 / SQL Server 2012)

Johan Arwidmark released his latest version of the hydration scripts for ConfigMgr 2012 SP1. 

View the instructions and download here.

Aside

The Hydration Kit for ConfigMgr 2012 RC2 is available for download

 

Hydration means a fully automated build of  a complete Lab environment for Hyper-V or VMware. Here is a download for deploying a complete ConfigMgr 2012 RC2 infrastructure: One Domain Controller and one ConfigMgr 2012 RC2 member server – Including pre-requisites like .Net Framework, SQL 2008 R2 SP1 CU4 and IIS – All fully automated.

The Hydration Kit for ConfigMgr 2012 RC2 is available for download
Fri, 20 Jan 2012 13:13:00 GMT

Aside

The Hydration Kit for ConfigMgr 2012 RC1 is available for download

Johan has posted a new hydration kit for 2012 ConfigMgr RC1.

Deployment Research > Blog – The Hydration Kit for ConfigMgr 2012 RC1 is available for download

Here is a download for deploying a complete ConfigMgr 2012 RC1 infrastructure in either Hyper-V or VMware: One Domain Controller and one ConfigMgr 2012 RC1 member server – Including pre-requisites like .Net Framework, SQL 2008 and IIS – all fully automated.


Once configured, the total build time for the full ConfigMgr 2012 RC1 lab environment is about 1.5 hours (on my laptop). 

Aside

Microsoft Deployment Toolkit–Hydrating ConfigMgr Secondary Sites with MDT Lite-Touch

The following solution(s) are provided as-is without any warranty, confers no rights and is not supported by the Author(s). Use at your own risk.

Installing and configuring Configuration Manager Secondary Sites is often a manual and time consuming task. If you have 50 or more sites that can be a significant amount of time spent installing and configuring Secondary Sites. The Hydration approach attempts to resolve that issue by providing an automated way to setup and configure Secondary Sites.

The following Hydration solution can be run on an existing Server 2003 or Server 2008 R2 Operating System and will configure the necessary pre-requisites and install the Configuration Manager Secondary Site.

Assumptions

This document assumes the following:

· You have Microsoft Deployment Toolkit 2010 Update 1 installed

· SQL is configured to allow Named Pipes

· You have already created a SQL$ share

· You have the knowledge required to work within the MDT Deployment Workbench

Supported Operating Systems

The Hydration process has been tested on Server 2003 R2 SP1/SP2 and Server 2008 R2 SP1.

Hydration Files

The files are contained in a “HydrationShare.zip” archive. Once these files are extracted, you will need to modify a few of the script files and add the required source files. This section details those required changes.

The files are provided as a self-contained DeploymentShare. You can simply extract this archive out and open the folder with the Deployment Workbench.

Sources files are required for the following items under the Applications directory in the HydrationShare.

Table 1: Required Source Files

Folder

Description

\ConfigMgr 2007 R3\Source

R3 installation files

\ConfigMgr 2007 R3\Hotfix

R3 Pre-req hotfix 977384

\ConfigMgr 2007 SP2 Secondary\PreReqs

ConfigMgr downloaded preq-reqs’s

\ConfigMgr 2007 SP2 Secondary\Source

ConfigMgr installation files

\ConfigMgr 2007 Toolkit V2\Source

ConfigMgr Toolkit MSI

\ConfigMgr Server 2003 IIS\i386

I386 directory from Server 2003 media

Installation

Extract out the HydrationShare

Extract the HydrationShare.zip archive to the location you want the HydrationShare to reside.

Share the HydrationShare

Once the files are extracted out, you need to share out the HydrationShare. A Hidden share is recommended.

clip_image001

Open the HydrationShare

1) Open the Deployment Workbench

2) Right-click on Deployment Shares and select Open Deployment Shareclip_image002

3) Select the path for the extracted HydrationShare filesclip_image004

4) Select Next

5) Select Next

6) Select Finish

Creating the MDT Database

This Hydration solution relies on a “SCRIPTSITECODE” variable. This solution was developed around this information being populated in the MDT database. It is possible to configure and set this variable through other methods, but this guide will not address those.

1) Open the MDT workbench and expand the HydrationShare.

2) Select Advanced Configuration-Database

3) Right-Click on Database and select New Database

4) Input the name of the SQL server and make sure the Network Library is selected to Named Pipes, then select Next

clip_image006

5) Input MDT2010 for the Database Name and select Next

clip_image008

6) Input SQL$ for the SQL Share, then select Nextclip_image010

7) Select Next

8) Select Finish

Extending the MDT database

Provided with the Hydration files are 2 SQL files for extending the MDT database with the SCRIPTSITECODE value and refreshing the views.

Open the “create scriptsitecode.sql” in SQL Management Studio.

Ensure that you are pointing to the MDT database.

clip_image012

Once you are pointed to MDT Database. You can Execute the query.

You should see “Command(s) completed successfully”

clip_image013

Next open the “refresh MDT views.sql” and make sure you are again pointed to correct database.

clip_image015

You should see “Command(s) completed successfully”

clip_image013[1]

If you open up the MDT workbench, go into Advance Configuration – Database- Computers, you will now see a new property called ScriptSiteCode listed on the Settings tab.

clip_image017

Bulk Importing Records Into The MDT Database

A PowerShell script and CSV file are provided for the bulk import of computers into the MDT database. These computers are the servers we want to configure as Secondary Sites.

CSV

The CSV file contains the Description, MacAddress, and ScriptSiteCode values we want to import into the Database.

clip_image018

We use the MacAddress to identify the server and configure the appropriate SiteCode for the ConfigMgr installation. The SiteCode is stored in the ScriptSiteCode variable. The description is just a friendly name so we can identify the server in the database.

PowerShell Script

The provided PowerShell script will do a bulk import of the CSV file into the MDT database. The PowerShell script imports a MDT Module, connects to the MDT database and imports the information from the CSV file.

Edit the PowerShell script to make sure the paths are correct to the source files.

clip_image020

Edit the PowerShell script to make sure the correct SQLServer and Database are specified.

clip_image022

After running the import, you will see the records in the Database based on the information in the CSV.

clip_image024

clip_image026

Configuring the HydrationShare

Once you have opened the HydrationShare with the Deployment Workbench and created the MDT database, there are a few changes that need to be made for the HydrationShare to successfully work.

Under the main HydrationShare properties, make sure the share name is correct and the local path is correct for the location you have put the HydrationShare.

clip_image028

Under the Rules tab, make sure your [CSettings] section has the correct SQLServer and Database name.

clip_image030

Ensure your bootstrap.ini has the correct DeployRoot value.

clip_image032

Under the Rules tab, configure the AdminPassword value to match the local administrator password of the servers you will run the Task Sequence on. This allows the Task Sequence to automatically log in and continue after the required reboots. This is required for the auto-logon to work correctly.

clip_image034

After making the required changes, right click on the HydrationShare and select Update Deployment Share.

clip_image035

Select Next.

clip_image037

Select Next.

clip_image039

Select Finish.

clip_image041

Required Script Modifications

(OPTIONAL) InstallConfigMgr2007SP2.wsf

There is a section of code in this script that allows you to specify existing source files to use, if we can find those, we will use those to install ConfigMgr, otherwise we’ll use the files from the script source files directory.

The following code would need to be changed in the script to match the location you might have local source files. It is located at line 93 in the script.

sFile = "F:\folderpath\smssetup\bin\i386\setup.exe"

ConfigureSvr2003.wsf

There is also logic in the 2003 IIS script that checks for a local copy of the i386 directory. We look for the i386 directory at the root of the C: drive. If we don’t find it then we copy it down from the source files. In addition we set a few registry keys to let Windows know where the source files are located. If you wanted to change this location, you would need to modify the following lines of code.

Line 57 – Check for local i386

sFile = "C:\i386\setup.ex_"

Lines 70-72 – Update registry to point to C:\i386

oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SourcePath", "C:\", "REG_SZ"

oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePackSourcePath", "C:\", "REG_SZ"

oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SourcePath", "C:\", "REG_SZ"

CreateConfigMgrSenders.wsf

The sender creation script is coded to the primary site. This will need to be modified to point to your primary site.

Lines 51-52

primSiteCode = "001"

primSite = "2008-configmgr"

Using The HydrationShare Task Sequence

Pre-requisites

Server 2003:

· None

Server 2008 R2:

· UAC is disabled

· Server Manager is not configured to start (R3 will fail if it detects any open MMC)

clip_image042

· Script is launched with administrative rights (careful of “Run” credentials)

Starting the Task Sequence

The Task Sequence can be started by launching the Lite-Touch process from the Run box.

Use the following command:

“Cscript.exe \\servername\hydrationshare$\scripts\litetouch.wsf

clip_image043

Once started, you will see the Task Sequence selection screen, select Next to continue.

clip_image045

On the credentials screen, provided an account that has appropriate credentials to connect to the HydrationShare. (Read Acces)

clip_image047

After clicking Next, the process will start. (Example screen from 2008 R2)

clip_image049

Download the HydrationShare here.

Aside

Configuration Manager–Hydrating Secondary Sites with ConfigMgr

The following solution(s) are provided as-is without any warranty, confers no rights and is not supported by the Author(s). Use at your own risk.

Installing and configuring Configuration Manager Secondary Sites is often a manual and time consuming task. If you have 50 or more sites that can be a significant amount of time spent installing and configuring Secondary Sites. The Hydration approach attempts to resolve that issue by providing an automated way to setup and configure Secondary Sites.

The following Hydration solution can be presented in 2 forms. It can be presented as a Post Operating System Task Sequence that will configure either Server 2003 or Server 2008 R2 systems for being a Secondary Site. The 2nd method is to integrate the steps into a Task Sequence that also deploys a Server 2003 or Server 2008 R2 image along with configuring the server to be a ConfigMgr Secondary Site.

Assumptions

This document assumes the following:

· You have a working and properly configured Configuration Manager 2007 SP2/R3 Primary Site

· You have Microsoft Deployment Toolkit 2010 Update 1 installed

· You have integrated MDT with ConfigMgr

· You have an existing MDT toolkit package

· SQL is configured to allow Named Pipes

· You have already created at least one DeploymentShare in MDT

· You have already created a SQL$ share

· You have the knowledge of how to create the required ConfigMgr packages

Supported Operating Systems

The Hydration process has been tested on Server 2003 R2 SP1/SP2 and Server 2008 R2 SP1.

Hydration Files

The files are contained in a “ConfigMgr_Install.zip” archive. Once these files are extracted, you will need to modify a few of the script files and add the required source files. This section details those required changes.

The following tables details the included file/folder structure.

Table 1: Folder Structure

Folder

Description

\SQL Files

SQL files to extend MDT database and refresh views

\Import_Computer

PowerShell and CSV for bulk import of ConfigMgr Secondary Site servers

\Templates

Task Sequence template and CustomSettings.ini template

\Configure WebDAV

Script to configure WebDAV for Server 2008 R2

\ConfigMgr Server 2003 IIS

Script to configure IIS for Server 2003

\ConfigMgr Create Senders

Script to create Primary site to Child site sender

\ConfigMgr 2007 Toolkit V2

ConfigMgr Toolkit (trace32)

\ConfigMgr 2007 SP2 Secondary

Script and source files for installing ConfigMgr secondary site

\ConfigMgr 2007 R3

Script and source files for installing ConfigMgr R3 and necessary pre-requisite hotfix

Source Files

Sources files are required for the following items.

Table 2: Required Source Files

Folder

Description

\ConfigMgr 2007 R3\Source

R3 installation files

\ConfigMgr 2007 R3\Hotfix

R3 Pre-req hotfix 977384

\ConfigMgr 2007 SP2 Secondary\PreReqs

ConfigMgr downloaded preq-reqs’s

\ConfigMgr 2007 SP2 Secondary\Source

ConfigMgr installation files

\ConfigMgr 2007 Toolkit V2\Source

ConfigMgr Toolkit MSI

\ConfigMgr Server 2003 IIS\i386

I386 directory from 2003 media

Installation

Creating the MDT Database

This Hydration solution relies on a “SCRIPTSITECODE” variable. This solution was developed around this information being populated in the MDT database. It is possible to configure and set this variable through other methods, but this guide will not address those.

1) Open the MDT workbench and expand your DeploymentShare

2) Select Advanced Configuration-Database

3) Right-Click on Database and select New Database

4) Input the name of the SQL server and make sure the Network Library is selected to Named Pipes, then select Next

clip_image002

5) Input MDT2010 for the Database Name and select Next

clip_image004

6) Input SQL$ for the SQL Share, then select Nextclip_image006

7) Select Next

8) Select Finish

Extending the MDT database

Provided with the Hydration files are 2 SQL files for extending the MDT database with the SCRIPTSITECODE value and refreshing the views.

Open the “create scriptsitecode.sql” in SQL Management Studio.

Ensure that you are pointing to the MDT database.

clip_image008

Once you are pointed to MDT Database. You can Execute the query.

You should see “Command(s) completed successfully”

clip_image009

Next open the “refresh MDT views.sql” and make sure you are again pointed to correct database.

clip_image011

You should see “Command(s) completed successfully”

clip_image009[1]

If you open up the MDT workbench, go into Advance Configuration – Database- Computers, you will now see a new property called ScriptSiteCode listed on the Settings tab.

clip_image013

Bulk Importing Records Into The MDT Database

A PowerShell script and CSV file are provided for the bulk import of computers into the MDT database. These computers are the servers we want to configure as Secondary Sites.

CSV

The CSV file contains the Description, MacAddress, and ScriptSiteCode values we want to import into the Database.

clip_image014

We use the MacAddress to identify the server and configure the appropriate SiteCode for the ConfigMgr installation. The SiteCode is stored in the ScriptSiteCode variable. The description is just a friendly name so we can identify the server in the database.

PowerShell Script

The provided PowerShell script will do a bulk import of the CSV file into the MDT database. The PowerShell script imports a MDT Module, connects to the MDT database and imports the information from the CSV file.

Edit the PowerShell script to make sure the paths are correct to the source files.

clip_image016

Edit the PowerShell script to make sure the correct SQLServer and Database are specified.

clip_image018

After running the import, you will see the records in the Database based on the information in the CSV.

clip_image020

clip_image022

Configuration Manager Packages

The following folders from the Hydration files will need be to created as Packages in ConfigMgr.

clip_image023

These packages will be used by the Task Sequence template. No Programs are required for the packages, simply create a Package that references the source files so we can make them available to the Task Sequence.

clip_image024

NOTE: The ConfigMgr Toolkit can simply be imported as a MSI.

Task Sequence Template

A Task Sequence XML is provided in the \Templates folder in the Hydration files.

clip_image025

This template contains all the necessary steps to configure either a 2003 or 2008 R2 server for being a Secondary Site. In addition to the packages containing the Hydration files, we need to use MDT Toolkit Package and a Settings Package.

The required steps in the template need to be configured to point to the ConfigMgr packages you have created.

clip_image024[1]

CustomSettings.ini

A customsetings.ini for use with Task Sequence template has been provided in the \Templates folder.

clip_image026

The SQLServer and Database values will need to be changed to match your environment.

clip_image027

Ensure that the Gather step in the template is pointing to your Settings package.

clip_image028

Required Script Modifications

InstallConfigMgr2007SP2.wsf

There is a section of code in this script that allows you to specify existing source files to use, if we can find those, we will use those to install ConfigMgr, otherwise we’ll use the files from the script source files directory.

The following code would need to be changed in the script to match the location you might have local source files. It is located at line 93 in the script.

sFile = "F:\folderpath\smssetup\bin\i386\setup.exe"

ConfigureSvr2003.wsf

There is also logic in the 2003 IIS script that checks for a local copy of the i386 directory. We look for the i386 directory at the root of the C: drive. If we don’t find it then we copy it down from the source files. In addition we set a few registry keys to let Windows know where the source files are located. If you wanted to change this location, you would need to modify the following lines of code.

Line 57 – Check for local i386

sFile = "C:\i386\setup.ex_"

Lines 70-72 – Update registry to point to C:\i386

oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SourcePath", "C:\", "REG_SZ"

oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ServicePackSourcePath", "C:\", "REG_SZ"

oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SourcePath", "C:\", "REG_SZ"

CreateConfigMgrSenders.wsf

The sender creation script is coded to the primary site. This will need to be modified to point to your primary site.

Lines 51-52

primSiteCode = "001"

primSite = "2008-configmgr"

Using with an OSD Task Sequence

The provided TS template in \templates can also be used with an OSD TS to create a Secondary Site from bare-metal. The template can simply be copied into an existing OSD TS.

clip_image029

 

Download the script files here.

Aside

YAHK – Yet Another Hydration Kit – This one for ConfigMgr 2012 Beta 2

Johan Arwidmark has yet another fantastic post. This time he’s created a hydration kit for ConfigMgr 2012 Beta 2. 

Read the full post here.

Here is a download for deploying a complete ConfigMgr 2012 SP2 Beta 2 infrastructure – Two domain controllers and one ConfigMgr 2012 SP2 Beta 2 member server – Including all pre-requisites like .Net Framework, SQL 2008 and IIS – All fully automated.

Aside

Hydration – Automating builds in your datacenter

Deployment extraordinaire Johan Arwidmark has created a nice blog post on creating an environment to hydrate your server and lab builds.  

Check out his excellent blog post here, and be sure to watch the included video on how to setup and configure the solutions.