NOTE: This Hydration kit has been updated, you probably want to use this one instead:
The Hydration Kit for System Center 2012 R2 is available for download
https://deploymentresearch.com/Research/tabid/62/EntryId/149/The-Hydration-Kit-for-System-Center-2012-R2-is-available-for-download.aspx
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.
Update: August 20, 2011 – There is also an additional extension available to this hydration kit: Extensions to the ConfigMgr 2012 Beta 2 Hydration Kit – Created by Ment van der Plas
Hydration Instructions
First, download the ConfigMgr 2012 Beta 2 Hydration Kit
Step 1 – Download the necessary software
On your Hyper-V host, create the C:\Downloads folder and download the following software:
- ConfigMgr 2012 Beta 2
- ConfigMgr 2007 Toolkit V2
- PowerShell Management Library for Hyper
http://pshyperv.codeplex.com/releases/view/38769 - SQL Server 2008 Enterprise x64
SQL Server 2008 SP1 Update x64
- SQL Server 2008 SP1 CU 10 Update x64
- Windows Server 2008 R2 Enterprise
Step 2 – Prepare the Hydration environment
- Configure Execution Policy in PowerShell, by typing the following in a PowerShell prompt: Set-ExecutionPolicy Unrestricted
- Extract the HydrationCM2012.zip file to C:\HydrationCM2012
- Create the Hydration Deployment Share by running the 1_CreateHydrationDeployment.ps1 script
- Copy the following folders C:\HydrationCM2012\Hydration\Source to C:\Hydration, replace any existing files.
- Applications
- Control
- Operating Systems
- Scripts
- Copy the ConfigMgr 2007 Toolkit V2 installation files (ConfigMgrTools.msi) to the C:\Hydration\Applications\ConfigMgr 2007 Toolkit V2\Source folder.
- Extract the ConfigMgr 2012 installation files to the C:\Hydration\Applications\Install ConfigMgr 2012 Beta 2\Source folder
- Run the C:\Hydration\Applications\Install ConfigMgr 2012 Beta 2\Source\SMSSETUP\BIN\X64\Setupdl.exe file, and in the path,
browse to C:\Hydration\Applications\Install ConfigMgr 2012 Beta 2Pr\eReqs and click Download - Copy the C:\Hydration\Applications\Install ConfigMgr 2012 Beta 2\Source\SMSSETUP\BIN\X64\EXTADSCH.exe to
C:\Hydration\Applications\Configure – Extend AD for ConfigMgr 2012\Source - Copy the SQL Server 2008 x64 installation files to the C:\Hydration\Applications\Install SQL Server 2008 SP1\Source folder
- Copy the SQL Server 2008 SP1 Update x64 installation file (SQLServer2008SP1-KB968369-x64-ENU.exe) to the
C:\Hydration\Applications\Install SQL Server 2008 SP1\Source folder - Copy the SQL Server 2008 SP1 CU 10 x64 installation file (SQLServer2008-KB2279604-x64.exe) to the
C:\Hydration\Applications\Install SQL 2008 SP1 CU 10\Source folder - Copy the .NET Framework 4.0 installation file (dotNetFx40_Full_x86_x64.exe) to the
C:\Hydration\Applications\Install NET Framework 4.0\Source folder - Copy the Windows Server 2008 R2 Enterprise files to C:\Hydration\Operating Systems\Windows Server 2008 R2 x64
- Create the HydrationServers media item by running the 2_CreateHydrationMediaItem.ps1 script
- Copy the C:\HydrationCM2012\Media001\Control folder to C:\Hydration\Servers\Content\Deploy, replace existing files
- Update the HydrationServers media item by running the 3_UpdateHydrationServersMedia.ps1 script
Step 3 – Create and deploy the virtual machines
- Install the PowerShell Management Library for Hyper-V by running the install.cmd script, ignore any errors about .NET Framework
- Verify that the files are not having any alternative data streams, if they do, remove it (using explorer or streams from Sysinternals)
- Create the virtual machines by running the 4_CreateVirtualMachines.ps1 script from a PowerShell command prompt
- Using Hyper-V Manager
- Start the DC01 virtual machine, and wait until the setup is complete
- Start the DC02 virtual machine, and wait until the setup is complete
- On DC01, verify that AD replication works with DC02
- Start the CM01 virtual machine, and wait until the setup is complete
Happy hydration / Johan
The Hydration Kit for ConfigMgr 2012 RC1 is available for download https://deploymentresearch.com/Blog/tabid/62/EntryId/48/The-Hydration-Kit-for-ConfigMgr-2012-RC1-is-available-for-download.aspx
/ Johan
Hi Johan,
I can help you with the troubleshooting of the Script. You can send the bits to my email address. This should be visible in our backend of your website.
Thorsten
Microsoft changed the setup between Beta 2 and RC1 so you need an updated version of the script, and also the SQL requirements are changed, so that is changed too. I have a working RC1 version of the hydration kit I'm testing and hope to publish shortly. If you want to help me with the testing, please let me know, and I can provide you with the bits.
/ Johan
Hi Johan,
thanks for the toolset. But the Install Script for the RC of the SCCM 2012 does not work. If I start the setupwpf.exe with the ini file I get a error "setup script contains syntax error".
Do you tested the Hydration Kit with the SCCM 2012 RC?
Thanks
Hmm it seems like it still works but I get a dos prompt while it installs:
Microsoft Deployment Toolkit version: 6.0.1763.0
The task sequencer log is located at C:UsersADMINI~1AppDataLocal
ogSMSTS.LOG. For task sequence failures, please consult this log.
Install .Net Framework 4.0: Starting .Net Framework 4.0 installation
how can I hide this?
Also do you know how to hide the Weclome to Window deployment window (processing bootstrap rules) that occurs in MDT 2012 beta?
Thanks
Hmm it seems like it still works but I get a dos prompt while it installs:
Microsoft Deployment Toolkit version: 6.0.1763.0
The task sequencer log is located at C:UsersADMINI~1AppDataLocal
ogSMSTS.LOG. For task sequence failures, please consult this log.
Install .Net Framework 4.0: Starting .Net Framework 4.0 installation
how can I hide this?
Also do you know how to hide the Weclome to Window deployment window (processing bootstrap rules) that occurs in MDT 2012 beta?
Thanks
Hmm it seems like it still works but I get a dos prompt while it installs:
Microsoft Deployment Toolkit version: 6.0.1763.0
The task sequencer log is located at C:UsersADMINI~1AppDataLocal
ogSMSTS.LOG. For task sequence failures, please consult this log.
Install .Net Framework 4.0: Starting .Net Framework 4.0 installation
how can I hide this?
Also do you know how to hide the Weclome to Window deployment window (processing bootstrap rules) that occurs in MDT 2012 beta?
Thanks
Hmm it seems like it still works but I get a dos prompt while it installs:
Microsoft Deployment Toolkit version: 6.0.1763.0
The task sequencer log is located at C:UsersADMINI~1AppDataLocal
ogSMSTS.LOG. For task sequence failures, please consult this log.
Install .Net Framework 4.0: Starting .Net Framework 4.0 installation
how can I hide this?
Also do you know how to hide the Weclome to Window deployment window (processing bootstrap rules) that occurs in MDT 2012 beta?
Thanks
Hi Johan,
I've used the Install-NetFramework40.wsf to install .net in my deployment environment (MDT 2010 update 1), unfortunately it stopped working when I went and updated to MDT 2012 Beta 1, guess since ZTIUtility.vbs has changed. have you had a look at the MDT beta and maybe you could update the script?
Thanks!
Yes, all configuration is done on the hyper-v host
/ Johan
Hi Johan,
im a newbie and struggling with this implementation.
are there any prerequesitises to be installed on the host machine, roles or features?
i think my issues are around powershell, my host is a Server 2008 std R2 (64bit) fully updated.
thanks any help would be appreciated.
Thanks for the feedback, I have now updated the ConfigMgr2012Unattend.ini file in the download.
/ Johan
Great stuff Johan, it worked great for me.
I did had to update the ConfigMgr2012Unattend.ini (in the HydrationApplicationsInstall ConfigMgr 2012 Beta 2 folder) and set the PrerequisitePath to "PrerequisitePath=C:MININTPreReqs".
By default it was set to d:tmpdl (or something like that) and it gave an error during the ConfigMgr setup stating it couldn't locate the PreReqs.
Other than that it worked like a charm!
Thanks,
Ment
downloading 2.0 now. appreciate the heads up, and as far as your 600 Gig SSD drive goes, thanks for making me jealous 😉
Thanks for tips on updating the Powershell script.
As for you idea about the Hydration kit, Microsoft have already done that. Download the Proof of Concept Jumpstart Kit v2.0 from Microsoft downloads. POC 2.0 (as well as previous versions) includes a small UI to set the config like server name, ipaddress, domain name etc.
You can also create a parent vhd to keep the hydration size small, will reduce space by about 20 GB. I just bought a 600 GB SSD instead 🙂
Thanks for putting this together. Similar to the old PoC Hydration Kit, how difficult would the effort be / is there any interest to customize this solution for a more flexible deployment environment? Joining an existing domain, allowing the consultant / end deployment user the option to set passwords, domain names, and most importantly, deployment share locations, just a few quick ideas that would make this even more useful. I had to do some serious diskspace scraping to get this current version to work on Hypervisors with 60 Gig SSD OS drives; there is just not enough space to play… Read more »
It was more than ten easy steps 🙂
Thanks Johan, This will be very usefull.