The Hydration Kit for ConfigMgr 2012 R2 is available for download

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 that builds a complete Configuration Manager 2012 R2 infrastructure, running on Windows Server 2012 R2 and SQL Server 2012 SP1, in either Hyper-V or VMware. The kit is built upon MDT 2013.

Update 2013-11-17: Added optional Windows 7 SP1, Windows 8.1, MDT 2013, and Orchestrator 2012 R2 to the kit.

Download the Hydration Kit for ConfigMgr 2012 R2 (222 kb).

Overview

Shorthand, to build the lab there are three steps you need to do:

  • Download the necessary software
  • Prepare the Hydration Environment
  • Deploy the virtual machines

Detailed instructions are further down this page… see the Step-by-Step Guide Guide section.

 image
The Deployment Wizard displaying the available task sequences.

TS
 The CM01 task sequence, building a complete ConfigMgr 2012 R2 site server.

 DW
The readymade applications in the hydration kit.

Step-by-Step Guide

Step 1 – Download the necessary software

  • On the machine (client or server) that you use to manage Hyper-V or VMware, create the C:Downloads folder.
  • Download the following software:
    • The Hydration Kit sample files (download)
    • BGInfo
    • MDT 2013
    • Windows ADK 8.1 (make sure you download the re-release that was available after October 17).
    • SQL Server 2012 with SP1
    • Windows Server 2012 R2
    • Configuration Manager 2012 R2 + PreReqs
  • Optional Software (Only needed if you want to deploy the optional Windows 7, Windows 8.1, MDT, and Orchestrator sequences)
    • Windows 7 SP1 x64
    • Windows 8.1 x64
    • Orchestrator 2012 R2
    • SQL Server 2012 Express with SP1
    • Visual C++ 2005 SP1 runtimes
    • Visual C++ 2008 SP1 runtimes
    • Visual C++ 2010 SP1 runtimes
    • Visual C++ 2012 runtimes
    • Microsoft .NET Framework 4.0
    • Report Viewer 2008 SP1
    • SQL Server 2012 SP1 Express with Tools

Note #1: To download ADK 8.1 run adksetup.exe /layout "C:\Downloads\ADK 8.1"

Note #2: To download the ConfigMgr 2012 R2 pre-requisites, run the SMSSETUPBINX64Setupdl.exe application from the ConfigMgr installation files.

 
Running the Setupdl.exe to download the ConfigMgr 2012 R2 PreReqs.

Step 2 – Prepare the Hydration Environment

Create the hydration deployment share

  1. On the Windows machine that you use to manage Hyper-V or VMware, install Windows ADK 8.1 (adksetup.exe) selecting only the following components:

    Deployment Tools
    Windows Preinstallation Environment (Windows PE)

    ADKSetup
    The Windows ADK 8.1 Setup.

  2. Install MDT 2013 (MicrosoftDeploymentToolkit2013_x64.msi) with the default settings.
  3. Extract the HydrationCM2012R2.zip sample file to C:.
  4. You should now have the following folder containing a few subfolders and PowerShell scripts.

     C:\HydrationCM2012R2\Source

  5. In an elevated (run as Administrator) PowerShell command prompt, configure Execution Policy in PowerShell by typing the following command:

    Set-ExecutionPolicy Unrestricted –Force Note: If you are running Windows Server 2012 R2 on your machine you don’t need to set the policy, it’s set by default. 

  6. In the PowerShell command prompt, create the hydration deployment share by running the following command

     C:\HydrationCM2012R2\Source\CreateHydrationDeploymentShare.ps1 PoSH
    The result after running the CreateHydrationDeploymentShare.ps1 script.

Populate the hydration deployment share with the downloaded files

  1. Copy the BGInfo file (bginfo.exe) to the following folder:

     C:\HydrationCM2012R2\DS\Applications\Install – BGInfo\Source

  2. Copy the Windows ADK 8.1 installation files to the following folder:

     C:\HydrationCM2012R2\DS\Applications\Install – ADK\Source

            ADKNewFolder
    The ADK folder (including the Patches folder from the re-release of Windows ADK 8.1).

  3. Copy the SQL Server 2012 with SP1 installation files (the content of the ISO, not the actual ISO) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – SQL Server 2012 SP1\Source

  4. Copy the ConfigMgr 2012 R2 installation files (extract the download) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – ConfigMgr 2012 R2\Source

  5. Copy the ConfigMgr 2012 R2 PreReqs files to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – ConfigMgr 2012 R2PreReqs

  6. Copy the ConfigMgr 2012 R2 EXTADSCH.exe file (SMSSETUP\BIN\X64) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Configure – Extend AD for ConfigMgr 2012\Source

  7. Copy the Windows Server 2012 R2 installation files (the content of the ISO, not the actual ISO) to the following folder:

    C:\HydrationCM2012R2\DS\Operating Systems\WS2012R2

Populate the hydration deployment share with the optional downloaded files

Note: These steps are only needed if you want to deploy the optional Windows 7 SP1, Windows 8.1, MDT, and Orchestrator 2012 R2 sequences. If you don’t want these, skip to the next section.

  1. Copy the Microsoft Visual C++ 2005 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:

    C:\HydrationCM2012R2\D\SApplications\Install – Microsoft Visual C++ 2005 SP1 – x86-x64\Source

  2. Copy the Microsoft Visual C++ 2008 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – Microsoft Visual C++ 2008 SP1 – x86-x64\Source

  3. Copy the Microsoft Visual C++ 2010 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – Microsoft Visual C++ 2010 SP1 – x86-x64\Source

  4. Copy the Microsoft Visual C++ 2012 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – Microsoft Visual C++ 2012 – x86-x64\Source

  5. Copy the Microsoft .NET Framework 4.0 (dotNetFx40_Full_x86_x64.exe) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – NET FrameWork 4.0\Source

  6. Copy the Orchestrator 2012 R2 setup files to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – Orchestrator 2012 R2\Source

  7. Copy the Report Viewer 2008 SP1 setup file (ReportViewer.exe) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – Report Viewer 2008 SP1\Source

  8. Copy the SQL Server 2012 SP1 Express with Tools setup file (SQLEXPRWT_x64_ENU.exe) to the following folder:

    C:\HydrationCM2012R2\DS\Applications\Install – SQL Server 2012 SP1 Express\Source

  9. Copy the Windows 7 SP1 x64 installation files (the content of the ISO, not the actual ISO) to the following folder:

    C:\HydrationCM2012R2\DS\Operating System\sW7SP1X64

  10. Copy the Windows 8.1 x64 installation files (the content of the ISO, not the actual ISO) to the following folder:

    C:\HydrationCM2012R2\DS\Operating Systems\W81X64

Create the hydration ISO (MDT 2013 offline media item)

  1. Using Deployment Workbench (available on the Start screen), expand Deployment Shares, and expand Hydration CM2012 R2.
  2. Review the various nodes. The Applications, Operating Systems and Task Sequences nodes should all have some content in them.

 image
The Hydration deployment share, listing the task sequences.

  1. Expand the Advanced Configuration node, and then select the Media node.
  2. In the right pane, right-click the MEDIA001 item, and select Update Media Content.

Note: The media update will take a while to run, a perfect time for a coffee break…

After the media update you will have a big ISO (HydrationCM2012R2.iso ) in the C:\HydrationCM2012R2\ISO folder. With all optional software, the HydrationCM2012R2.iso should be about 20 GB in size, with only the files for ConfigMgr 2012 R2, about 12 GB.

image 
The HydrationCM2012R2.iso

Step 3 – Deploy the virtual machines

Note: All accounts, including Administrator, have a password of P@ssw0rd.

Deploying DC01

  1. Using Hyper-V Manager or VMware Sphere, create a virtual machine with the following settings:
  • Name: DC01
  • Hard drive: 100 GB (dynamic disk)
  • Memory: 1 GB
  • Network: Your lab network
  • Image file (ISO): C:\HydrationCM2012R2\ISO\HydrationCM2012R2.iso
  1. Start the DC01 virtual machine. After booting from HydrationCM2012R2.iso , and after WinPE has loaded, select the DC01 task sequence.
  2. Wait until the setup is complete and you see the Hydration Complete message in the final summary.
  3. Leave DC01 running while deploying the other virtual machine (CM01).

Deploying CM01

  1. Using Hyper-V Manager or VMware Sphere, create a virtual machine with the following settings:
  • Name: CM01
  • Hard drive: 300 GB (dynamic disk)
  • Memory: 6 GB (6 GB minimum, 16 GB RAM recommended)
  • Network: Your lab network
  • Image file (ISO): C:\HydrationCM2012R2\ISO\HydrationCM2012R2.iso
  1. Start the CM01 virtual machine. After booting from HydrationCM2012R2.iso , and after WinPE has loaded, select the CM01 task sequence.
  2. Wait until the setup is complete and you see the Hydration Complete message in the final summary.

Additional Configuration Notes:

Note: Again, by default, all accounts, including Administrator, have a password of P@ssw0rd.

If you need to change server names, IP addresses, domain names, installation, passwords, etc. in the environment, the main configuration is stored in the four .ini files in the C:\HydrationCM2012R2\ISO\Content\Deploy\Control folder.

 image
The configuration files for the Hydration Kit.

For SQL and ConfigMgr settings you need to update the following files in the C:\HydrationCM2012R2\DS\Applications folder:

  • Install – ConfigMgr 2012ConfigMgr2012Unattend.ini
  • Install – SQL Server 2012ConfigurationFileCM2012.ini

If you need to change the various service accounts, you need to to modify the Configure-CreateADStructure.wsf script in the C:\HydrationCM2012R2\DS\Applications\Configure – Create AD Structure folder.

If you change the Administrator password, and/or domain name, you also need to update the Authorize DHCP credentials in the DC01 task sequence.

DC01

/ Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
33 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Admin
Admin
9 years ago

Pretty much so, but you only need to overwrite values that are not connfigured for last value wins (defined in ztigather.xml), and values that are not set by the main CustomSettings.ini file.

/ Johan

dwchan69
dwchan69
9 years ago

Hum, I may have misunderstood the priority works in MDT. As I can define OSDComputerName at number of places for example

1. %DeploymentShare%controlcustomsettings.ini
2. MDT database
3. %DeploymentShare%controlcustomsettings_Special.ini that get call up within the "Special" task sequence.

I always though that by just simply parsing the customsettings_Special.ini with the gather operation inside a Task Sequence will load that variable in memory. Are you saying that it is a 2 steps process?
First, I need to tell the task sequence to parse the extra cs.ini
Second, I need to overwrite EVERY variables that I plan to override by the task sequence?

Admin
Admin
9 years ago

The Gather operation will not overwrite properties not flagged for overwrite=true. That's why I use a custom value for the computer name for example (the HydrationOSDComputerName property).

I then have the task sequence set OSDComputerName=%HydrationOSDComputerName%, because hardcoded values in the sequence will "win".

You can also have a script that sets those values.

/ Johan

dwchan69
dwchan69
9 years ago

Generally speaking, you will put your join domain info on %deploymentshare%controlcustomsettings.ini. JoinDomain=test.COMDomainAdmin=AdministratorDomainAdminDomain=testDomainAdminPassword=P@ssw0rdMachineObjectOU="OU=Servers,DC=test,DC=COM" As I do not want to limited the hydration kit to a single domain, I have follow suite and move some of my mdt setting to a specialize cs.ini that is tight back to the task sequence. So if I remove the normal join domain info from the default customsettings.ini JoinDomain=test.COMDomainAdmin=AdministratorDomainAdminDomain=testDomainAdminPassword=P@ssw0rdMachineObjectOU="OU=Servers,DC=test,DC=COM" and move them to "customsettings_pocsrv01.ini (ini for any server build) [Settings]Priority=DefaultProperties=JoinDomain,DomainAdmin,DomainAdminDomain,DomainAdminPassword,MachineObjectOU [Default]JoinDomain=BENSON.COMDomainAdmin=AdministratorDomainAdminDomain=BENSONDomainAdminPassword=P@ssw0rdMachineObjectOU="OU=Servers,DC=BENSON,DC=COM" And the customsettings_POOSRV01.ini is being call by the task sequence. However, for what ever reason, not all of the MDT variable are being read in… Read more »

Admin
Admin
9 years ago

The old hydration kit for CM2007 was built on MDT 2010, and the sequences needs to be modified to work with MDT 2013. I do have a MDT 2013 task sequence that deploys CM2007, send me an email and I can send you a copy.

/ Johan

galicea
galicea
9 years ago

Hello, Firstly, thank you for the awesome work on this. I have since been able to use it perfectly. However, I have attempted to re-create the same level of success using the Hydration Kit for SCCM 2007. The host which my hypervisor (Hyper-V) sits on is using MDT 2013. I am using the TS's and folder content from your Hydration Kit for 2007. My issue seems to begin when I boot the VM guests (DC01) into WinPE off of the Media created via the Hydration PoSH scripts. It seems I am stuck in an infinite loop. There are no errors… Read more »

Admin
Admin
9 years ago

They fixed a few in R2, the rest you have to remove via registry entries. Check the HKLMSOFTWAREMicrosoftServerManagerRoles keys.

/ Johan

thob
thob
9 years ago

For sure, I am not the first one to ask this: enabling/configuring roles (as you do) creates useless notifications in the ServerManagerGUI (e.g. DHCP post deployment wizard). Is there any way to remove this via script? In this case you can't even remove it with the GUI, you have to click through the wizard, as you all know.
T.

Admin
Admin
9 years ago

Send me an email, and I can help you offline. You find the contact info in the About page.

/ Johan

OldManWyler
OldManWyler
9 years ago

Hello Johan,This is an awesome kit. Thank you. I do have a problem though… I was able to run the Hydration kit "AS IS" with no issues. But what i did was changed the domain name and went through all of the .ini files as per your instructions above. I ran the DC01 with no problems and the CM01 with no issues up until it gets to the install Config Manager R2. it gives the cscript.exe prompt and states "about to run command "E:DeployApplicationsInstall – ConfigMr 2012 R2SourceSMSSETUPBINX64setup.exe" /Script "E:DeployApplicationsInstall – ConfigMr 2012 R2ConfigMgr2012Unattend.ini" /NoUserInput In the ConfigMgr2012Unatend.ini file i… Read more »

Admin
Admin
9 years ago

Hi Manny,

Use Dynamic disks (as I have written in the post) and the lab will only consume what is actually used. If you don't follow the recommended volume sizes you need to modify the task sequences. Again, please use dynamic disks, using fixed disks for lab or PoC is just a waste of disk space.

For example the 100 GB dynamic disk for DC01 consumes about 9 GB of real disk, and the 300 GB volume needed for ConfigMgr 2012 R2 (CM01) is using about 30 GB of real disk space.

/ Johan

MannyDeo
MannyDeo
9 years ago

Hi Johan We have started deploying the hydration kit on VMWare, only issue is we have limited storage space, please can you advise where we can change the partition sizes of the machines. (i.e. on DC we have only 50 GB assigned, does not deploy, I tested on Oracle Virtual Box and needed at least a drive with 75 GB, with some changes , we were able to get extra 35 GB on the VMware and DC deployed then fine). We are having same issue with CM01 (i.e. we only have got 80 GB assigned drive, this failed , when… Read more »

Admin
Admin
9 years ago

After changing the .ini files you need to update the ISO again. If PC0001 fails to join the domain, check the netsetup.log (and of course verify that DC01 is running when deploying PC0001). If you need additional help, send me an email and we can take it offline.

/ Johan

davcob2
davcob2
9 years ago

Hello,

I have 2 issues. When I run the hydration, my OR01 nor PC0001 are deploying.

Has anyone run into issues when changing the .ini files in the control folder for a custom environment? I've attempted to change the domain name and the admin password and the machines don't deploy.

davcob2
davcob2
9 years ago

Hello,

I have 2 issues. When I run the hydration, my OR01 nor PC0001 are deploying.

Has anyone run into issues when changing the .ini files in the control folder for a custom environment? I've attempted to change the domain name and the admin password and the machines don't deploy.

Admin
Admin
9 years ago

Hi Orion,

You need to have MDT 2013 and Windows ADK 8.1 installed on the machine,

Also, to avoid the running script questions, run this first Set-ExecutionPolicy Unrestricted -Force

/ Johan

orion
orion
9 years ago

hi all, I am new to hydration kit, but running into one issue when I ran C:HydrationCM2012R2SourceCreateHydrationDeploymentShare.ps1 I am getting error message and its not be able to create share.===============================================================================Security warningRun only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm yourcomputer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warningmessage. Do you want to run C:HydrationCM2012R2SourceCreateHydrationDeploymentShare.ps1?[D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"): r Directory: C:HydrationCM2012R2 Mode LastWriteTime Length Name—- ————- —— —-d—- 2/9/2014 1:10 AM… Read more »

Callistus
Callistus
9 years ago

Hi Johan,
First of all Awsome work!
Second of all AWSOME BOOK!
Scripting to deploy a whole setup with DC's, other servers and windows Clients with lite touch are almost childs play 😉 Havent tried the Zero Touch yet, and I know it will be interesting to get things working in my own tweaked environment.
Any plans of creating similar hydration kits for Win2012R2 and Win8.1?

Keep up the great work!

Callistus D. Chelliah

dragon5150
dragon5150
9 years ago

this whole process is pretty awesome!
Not only do I fully built setup but I can see the scripting behind how to do it and setup it up in task sequences.
Thank you so much!

Admin
Admin
9 years ago

Send me an email, and I can probably help… You find the contact info in the about page

/ Johan

Yan
Yan
9 years ago

Thanks Johan, I modified the files as recommanded but when I boot the ISO; WinPE boots ok but the Task Sequence Wizard does not start and a command prompt is openned to X:windowssystem32>.

I tried finding logs to troubleshoot but the only one that seems on the machine is winpeshl.log and there is no errors in it.
Should I modify the xml files to change the values "viamonstra" to info that reflects our oganisation?
ts.xml

Admin
Admin
9 years ago

Well, don't install a new domain controller if you don't need it for other things… If you already have an AD, you can just deploy CM01 (after changing the configuration files for your domain).

Anyway, here is AD configuration for a second domain controller in a domain:

; Active Directory Configuration
ReplicaOrNewDomain=Replica
ReplicaDomainDNSName=corp.viamonstra.com
DomainNetBiosName=VIAMONSTRA
ForestLevel=4
DomainLevel=4
AutoConfigDNS=Yes
ConfirmGC=Yes
CriticalReplicationOnly=No
ADDSUserName=Administrator
ADDSUserDomain=VIAMONSTRA
ADDSPassword=P@ssw0rd
DatabasePath=D:NTDS
LogPath=D:NTDS
SysVolPath=D:SYSVOL
SafeModeAdminPassword=P@ssw0rd
SiteName=NewYork

/ Johan

Yan
Yan
9 years ago

Thank you for these tools, I've used the SP1 hydration kit in a lab and was tasked to put in in production so I was wondering if it was possible to use the hydration kit R2 to join an existing domain?We have to add a new domain controller 2012 R2 to be W8 ready, our current ADDS level is 2008 R2 and we have 175 PCs and 40 Servers. So 2 birds with one stone… I've read about the ini files that will need to be changed to reflect our domain, subnet, etc… But what about getting the new domain… Read more »

Admin
Admin
9 years ago

Probably, contact me offline and I can help. Click the about link in the menu for contact info

/ Johan

janhoedt
janhoedt
9 years ago

Thanks for the feedback!
I configured this hydration to run from a share instead of bootable media. This way I can easier troubleshoot/adapt when needed wurhout generating iso.
Dc01 works fine but cm01 only installs Windows then stops without any error. Windows is loaded, part of the domain but that s it, in c-drive there is a bootstrap.vbs also. No idea what goes wring.
Could you advise?
J.

brianfgonzalez
brianfgonzalez
9 years ago

FYI, I had to manually create the Media DS entry when testing mine. I pointed it to the "C:HydrationCM2012R2ISO" folder and then was able to build the Media .ISO files with no issue.

steveburkett
steveburkett
9 years ago

To login to the SQL Management Studio, make sure you're logged in as the Domain Administrator account (VIAMONSTRAAdministrator) rather then the local Windows Administrator (CM01Administrator) else you get an access denied error from SQL Server.

bjornar@crayon.com
bjornar@crayon.com
9 years ago

Hi Johan,

Thx! working like a dream!

bjornar@crayon.com
bjornar@crayon.com
9 years ago

Hi Johan,

Thx! working like a dream!

Admin
Admin
9 years ago

Hi Andy,

I have updated the info, and screenshot, to reflect the new Windows ADK 8.1 re-release.

/ Johan

Admin
Admin
9 years ago

As long as the correct SQL installation files are in the correct folder of the kit, SQL Management Studio is part of the hydration. To troubleshoot why it's not installed, check the Install-SQL2012SP1forCM2012R2.log file as well as the SQL setup log files (C:Program FilesMicrosoft SQL Server110Setup BootstrapLog)./ Johan

rowbotha
rowbotha
9 years ago

Hi Johan,

What can i say…awesome. Working like a treat 🙂

Just as an FYI, you'll need to make sure you include the NEW 'Patches' folder from the re-released ADK 8.1 to the hydration deployment share before creating the HydrationCM2012R2.iso

/Andy

janhoedt
janhoedt
9 years ago

Hi Johan,

Great work! I'm trying it out right now!
One thing though, I'd love to built in SQL management studio to figure out if the database is really there (tried it on the 2012 RTM Hydration kit with Windows 2008 but couldn't login and never made it work, never knew what exactly was wrong since I couldn't verify the database).
Can you advise on that?

Thanks!
J.


>