By Johan Arwidmark / February 10, 2014

Here is a download that builds a complete System Center2012 R2 infrastructure, and a few supporting infrastructure servers, as either virtual machines (Hyper-V and VMware tested) or physical machines. The kit can also deploy Windows 7 SP1 and Windows 8.1 clients, and is built upon MDT 2013.

The Hydration Kit contents

The kit allows you to automatically deploy the below list of servers. The only server you really need to build is DC01, since that's the domain controller, and all other clients and servers are joining the domain. Turns out joining a domain is tricky without a domain controller 🙂

DC01 – Windows Server 2012 R2, DC, DHCP and DNS
CM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Configuration Manager
DPM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Data Protection Manager
MDT01 – Windows Server 2012 R2, WDS, SQL Server 2012 SP1 Express
MDT02 – Windows Server 2012 R2, File Server
OM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Operations Manager
OR01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Orchestrator
PC0001 – Windows 7 SP1 x64, domain Client
PC0002 – Windows 8.1 x64, domain Client
PC0003 – Windows 7 SP1 x64, domain Client
PC0004 – Windows 7 SP1 x64, domain Client
SM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Service Manager
VMM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Virtual Machine Manager

Download the Hydration Kit for System Center 2012 R2 (286 kb).

Update Feb 12, 2014: Fixed an issue causing the Create Data Partition action to fail. If you downloaded the kit prior to this date, please re-download the kit and copy the DataPartition.txt file to the C:HydrationSC2012R2DSScripts folder.

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

Note: You only need to download the software needed for the machines you actually build. Example: If you don't plan to deploy any Windows 7 SP1 clients, you don't need to add those setup files.

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

The Deployment Wizard displaying the available task sequences.

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

The readymade applications in the hydration kit.

Step-by-Step Guide

Step 1a – Download the mandatory software

On the machine (client or server) that you use to manage Hyper-V or VMware, create the C:Downloads folder.

Download the following mandatory 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 18).
Windows Server 2012 R2

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

Step 1b – Download the optional software

You only need to download software for the servers you are actually building. Example: To deploy a ConfigMgr 2012 R2 server, you only need to download SQL Server 2012 SP1 and ConfigMgr 2012 R2, and so forth for the other System Center 2012 R2 products. Again, the only server you really need to build is DC01, since that's the domain controller, and all other clients and servers are joining the domain.

To deploy the Windows 7 SP1 clients (PC0001, PC0003 and PC0004), you need:

Windows 7 SP1 x64
Visual C++ 2005 SP1 runtimes
Visual C++ 2008 SP1 runtimes
Visual C++ 2010 SP1 runtimes
Visual C++ 2012 runtimes
Microsoft .NET Framework 4.0

To deploy the Windows 8.1 x64 client (PC0002), you need:

Windows 8.1 x64
Visual C++ 2005 SP1 runtimes
Visual C++ 2008 SP1 runtimes
Visual C++ 2010 SP1 runtimes
Visual C++ 2012 runtimes

To deploy the System Center 2012 R2 Configuration Manager server (CM01), you need:

SQL Server 2012 Standard with SP1
System Center 2012 R2 Configuration Manager + PreReqs

Note #2: To download the ConfigMgr 2012 R2 pre-requisites, run the SMSSETUP\BIN\X64\Setupdl.exe application from the ConfigMgr installation files.

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

To deploy the System Center 2012 R2 Data Protection Manager server (DPM01), you need:

SQL Server 2012 Standard with SP1
System Center 2012 R2 Data Protection Manager

Note: To install the evaluation version of System Center 2012 R2 Data Protection Manager, which is default in this kit, you need to download the special evaluation media. The DPM team is unfortunately not very good on writing installers. This is the ONLY System Center 2012 R2 product that requires a separate media for evaluation, and even worse, the evaluation media is hardcoded against a SQL Server instance (MSDPM2012EVAL). Not that bright if you ask me.

To deploy the Microsoft Deployment Toolkit (MDT) 2013 server (MDT01), you need:

SQL Server 2012 SP1 Express with Tools
Report Viewer 2008 SP1 (for WSUS)

To deploy the System Center 2012 R2 Operations Manager server (OM01), you need:

SQL Server 2012 Standard with SP1
System Center 2012 R2 Operations Manager

To deploy the System Center 2012 R2 Orchestrator server (OR01), you need:

SQL Server 2012 Standard with SP1
System Center 2012 R2 Orchestrator

To deploy the System Center 2012 R2 Service Manager server (SM01), you need:

SQL Server 2012 Standard with SP1
System Center 2012 R2 Service Manager
Report Viewer 2008 SP1 (KB971119)

To deploy the System Center 2012 R2 Virtual Machine Manager server (VMM01), you need:

SQL Server 2012 Standard with SP1
System Center 2012 R2 Virtual Machine Manager

Step 2 – Prepare the Hydration Environment

Create the hydration deployment share

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)

The Windows ADK 8.1 Setup.
Install MDT 2013 (MicrosoftDeploymentToolkit2013_x64.msi) with the default settings.
Extract the HydrationSC2012R2.zip sample file to C:.
You should now have the following folder containing a few subfolders and PowerShell scripts.
C:\HydrationSC2012R2\Source
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.
In the PowerShell command prompt, create the hydration deployment share by running the following command
C:\HydrationSC2012R2\Source\CreateHydrationDeploymentShare.ps1

Copy the BGInfo file (bginfo.exe) to the following folder:
C:\HydrationSC2012R2\D\SApplications\Install – BGInfo\Source
Copy the Windows Server 2012 R2 installation files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationSC2012R2\DS\Operating Systems\WS2012R2

Note: These steps are only needed if you want to deploy the Windows 7 SP1 clients. If you don't want these, skip to the next section.

Copy the Microsoft Visual C++ 2005 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2005 SP1 – x86-x64\Source
Copy the Microsoft Visual C++ 2008 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2008 SP1 – x86-x64\Source
Copy the Microsoft Visual C++ 2010 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2010 SP1 – x86-x64\Source
Copy the Microsoft Visual C++ 2012 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2012 – x86-x64\Source
Copy the Microsoft .NET Framework 4.0 (dotNetFx40_Full_x86_x64.exe) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – NET Framework 4.0\Source

Note: These steps are the same as for the Windows 7 SP1 client, so if you've done that you can skip to the next section.

Copy the Microsoft Visual C++ 2005 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder: C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2005 SP1 – x86-x64\Source
Copy the Microsoft Visual C++ 2008 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder: C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2008 SP1 – x86-x64\Source
Copy the Microsoft Visual C++ 2010 SP1 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder: C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2010 SP1 – x86-x64\Source
Copy the Microsoft Visual C++ 2012 runtimes (vcredist_x64.exe and vcredist_x86.exe) to the following folder: C:\HydrationSC2012R2\DS\Applications\Install – Microsoft Visual C++ 2012 – x86-x64\Source
Copy the Microsoft .NET Framework 4.0 (dotNetFx40_Full_x86_x64.exe) to the following folder: C:\HydrationSC2012R2\DS\Applications\Install – NET Framework 4.0\Source

Note: These steps are only needed if you want to deploy System Center 2012 R2 Configuration Manager. If you don't want this, skip to the next section.

Copy the Windows ADK 8.1 installation files to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Windows ADK 8.1\Source
Copy the SQL Server 2012 with SP1 installation files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\Source
Copy the ConfigMgr 2012 R2 installation files (extract the download) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Configuration Manager\Source
Copy the ConfigMgr 2012 R2 PreReqs files to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Configuration Manager\PreReqs
Copy the ConfigMgr 2012 R2 EXTADSCH.exe file (SMSSETUP\BIN\X64) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Configure – Extend AD for ConfigMgr 2012\Source

Note: These steps are only needed if you want to deploy System Center 2012 R2 Data Protection Manager. If you don't want this, skip to the next section.

Copy the SQL Server 2012 with SP1 installation files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\Source
Copy the DPM 2012 R2 installation files (extract the download) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Data Protection Manager\Source

Note: These steps are only needed if you want to deploy the System Center 2012 R2 Operations Manager. If you don't want this, skip to the next section.

Copy the SQL Server 2012 with SP1 installation files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\Source
Copy the Operations Manager 2012 R2 setup files to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Operations Manager\Source

Note: These steps are only needed if you want to deploy the System Center 2012 R2 Orchestrator. If you don't want this, skip to the next section.

Copy the SQL Server 2012 with SP1 installation files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\Source
Copy the Orchestrator 2012 R2 setup files to the following folder:

C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Orchestrator\Source

Note: These steps are only needed if you want to deploy the System Center 2012 R2 Service Manager. If you don't want this, skip to the next section.

Copy the SQL Server 2012 with SP1 installation files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\Source
Copy the Service Manager2012 R2 setup files to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Service Manager\Source
Copy the Report Viewer 2008 SP1 setup file (ReportViewer.exe) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Report Viewer 2008 SP1\Source

Note: These steps are only needed if you want to deploy the System Center 2012 R2 Virtual Machine Manager. If you don't want this, skip to the next section.

Copy the Windows ADK 8.1 installation files to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Windows ADK 8.1\Source
Copy the SQL Server 2012 with SP1 installation files (the content of the ISO, not the actual ISO) to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\Source
Copy the Virtual Machine Manager 2012 R2 setup files to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Virtual Machine Manager\Source

Note: These steps are only needed if you want to deploy Microsoft Deployment Toolkit 2013. If you don't want this, skip to the next section.

Copy the Windows ADK 8.1 installation files to the following folder:
C:\HydrationSC2012R2\DS\Applications\Install – Windows ADK 8.1\Source
Copy the SQL Server 2012 SP1 Express with Tools setup file (SQLEXPRWT_x64_ENU.exe) to the following folder:

C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1 Express\Source
Copy the Report Viewer 2008 SP1 setup file (ReportViewer.exe) to the following folder:
C:\HydrationSC2012R2\D\SApplications\Install – Report Viewer 2008 SP1\Source

Create the hydration ISO (MDT 2013 offline media item)

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

The Hydration deployment share, listing the task sequences.

Expand the Advanced Configuration node, and then select the Media node.
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 (HydrationSC2012R2.iso ) in the C:\HydrationSC2012R2\ISO folder. With all optional software, the HydrationSC2012R2.iso should be about 24 GB in size, with only the files for ConfigMgr 2012 R2, about 12 GB.

The HydrationSC2012R2.iso

Step 3 – Deploy the virtual machines

Note: All accounts, including Administrator, have a password of P@ssw0rd. If you want a PowerShell script that creates these VMs for Hyper-V, check the C:HydrationSC2012R2SourceExtra folder for two sample scripts. One for building Gen 1 VMS, and one for building Gen 2 VMs.

Sample PowerShell script for creating the virtual machines.

Deploying DC01

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:\HydrationSC2012R2\ISO\HydrationSC2012R2.iso

Start the DC01 virtual machine. After booting from HydrationSC2012R2.iso , and after WinPE has loaded, select the DC01 task sequence.
Wait until the setup is complete and you see the Hydration Complete message in the final summary.
Leave DC01 running while deploying the other virtual machines.

Deploying the other machines

Once the domain controller (DC01) is up and running, you can deploy the other virtual machines. Don't forget to leave DC01 running while deploying the other machines since they are joining the domain during deployment. Use the following settings for the other virtual machines.

CM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Configuration Manager

Hard drive: 300 GB (dynamic disk)
Memory: 6 GB RAM minimum, 16 GB recommended

DPM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Data Protection Manager

Hard drive: 300 GB (dynamic disk)
Memory: 4 GB RAM minimum, 8 GB recommended

MDT01 – Windows Server 2012 R2, WDS, SQL Server 2012 SP1 Express

Hard drive: 300 GB (dynamic disk)
Memory: 2 GB RAM minimum, 4 GB recommended

MDT02 – Windows Server 2012 R2, File Server

Hard drive: 300 GB (dynamic disk)
Memory: 2 GB RAM minimum, 4 GB recommended

OM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Operations Manager

Hard drive: 300 GB (dynamic disk)
Memory: 4 GB RAM minimum, 8 GB recommended

OR01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Orchestrator

Hard drive: 300 GB (dynamic disk)
Memory: 4 GB RAM minimum, 8 GB recommended

PC0001 – Windows 7 SP1 x64, domain Client

Hard drive: 300 GB (dynamic disk)
Memory: 1 GB RAM minimum, 2 GB recommended

PC0002 – Windows 8.1 x64, domain Client

Hard drive: 300 GB (dynamic disk)
Memory: 1 GB RAM minimum, 2 GB recommended

PC0003 – Windows 7 SP1 x64, domain Client

Hard drive: 300 GB (dynamic disk)
Memory: 1 GB RAM minimum, 2 GB recommended

PC0004 – Windows 7 SP1 x64, domain Client

Hard drive: 300 GB (dynamic disk)
Memory: 1 GB RAM minimum, 2 GB recommended

SM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Service Manager

Hard drive: 300 GB (dynamic disk)
Memory: 4 GB RAM minimum, 8 GB recommended

VMM01 – Windows Server 2012 R2, SQL Server 2012 SP1, System Center 2012 R2 Virtual Machine Manager

Hard drive: 300 GB (dynamic disk)
Memory: 4 GB RAM minimum, 8 GB recommended

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 various .ini files in the C:\HydrationSC2012R2\ISO\Content\Deploy\Control folder.

The configuration files for the Hydration Kit.

For ConfigMgr 2012 R2 (CM01) you need to update the following files::

C:\HydrationSC2012R2\DS\Applications\Install – System Center 2012 R2 Configuration Manager\ConfigMgr2012Unattend.ini
C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\ConfigurationFileConfigurationManager2012R2.ini

For Operations Manager 2012 R2 (OM01) you need to update the following files:

C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\ConfigurationFileOperationsManager2012R2.ini
C:\HydrationSC2012R2\ISO\Content\Deploy\Control\CustomSettings_OM01.ini

For Orchestrator 2012 R2 (OR01) you need to update the following files:

C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\ConfigurationFileOrchestrator2012R2.ini
C:\HydrationSC2012R2\ISO\Content\Deploy\Control\CustomSettings_OR01.ini

For DPM 2012 R2 (DPM01) you need to update the following files:

C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\ConfigurationFileDataProtectionManager2012R2EVAL.ini
C:\HydrationSC2012R2\ISO\Content\Deploy\Control\CustomSettings_DPM01.ini

For Service Manager 2012 R2 (SM01) you need to update the following files:

C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\ConfigurationFileServiceManager2012R2.ini
C:\HydrationSC2012R2\ISO\Content\Deploy\Control\CustomSettings_SM01.ini

For VMM 2012 R2 (VMM01) you need to update the following files:

C:\HydrationSC2012R2\DS\Applications\Install – SQL Server 2012 SP1\ConfigurationFileVirtualMachineManager2012R2.ini
C:\HydrationSC2012R2\ISO\Content\Deploy\Control\CustomSettings_VMM01.ini

If you need to change the various service accounts, you need to to modify the Configure-CreateADStructure.wsf script in the C:\HydrationSC2012R2\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.

/ Johan

5 1 vote

Article Rating

87 Comments

Newest

Oldest Most Voted

Inline Feedbacks

View all comments

Axl-R

8 years ago

Amazing job ! thanks for sharing it all working perfectly thank you !

Admin

See the "Additional Configuration Notes:" section in the article for tips about customization.

Roue

hi,

Top!

is it possible to change the Administrator password, network settings, Domain etc? if yes, where do i change it?

thanks

I have only seen that happen when the NIC in the VM for some reason did not work (VMware only).

Send me an email and I can help you troubleshoot offline.

klarion

I'm having this same issue as user MayurP had. For some reasong the ZTIAuthorizeDHCP fails when installing DC01. Credentials are ok and I can manully authorize the DHCP. Any ideas?

Executing command line: %TOOLROOT%bddrun.exe /runas cscript.exe "%SCRIPTROOT%ZTIAuthorizeDHCP.wsf"

The execution of the group (Install DHCP) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Authorize DHCP. Execution of task sequence failed.
Incorrect function. (Error: 00000001; Source: Windows)

Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:nts_sms_fresmsclienttasksequencetsmanagertsmanager.cpp,767)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

Hi MundoSCOM and Dennis, send me an email and I can help offline. Contact info is in the about page.

Dennis

In continuation to my last comment. I managed to get the ADK 8.1 to start installation by re-downloading the PreReq files for CM2012. Now the Task Sequence stops at "Running action: Install – Windows ADK 8.1" and a User Credentials prompt comes up. I have entered in User Name: Administrator , Password: P@ssw0rd and Domain: corp.viamonstra.com but keep getting the error "Invalid credentials: The network path was not found."

MundoSCOM

Johan: Thanks so much for this. It looks great. I'm installing just the OM01 part and adding it to my existing lab domain. I've modified the CustomSettings_OM01.ini (with my domain details), the ConfigurationFileOperationsManager2012R2.ini (Installing SP2 so I replaced TOOLS for BIDS) the CustomSettings.ini and Configure-SetAdministratorAutologoninDomain.wsf. the reason for the last modification is that it uses the JoinDomain from CustomSettings_OM01.ini but has the username hardcoded to 'Administrator' therefore failing to login after first reboot. It also uses the AdminPassword from CustomSettings.ini which forced me to change it as well to match my domain. The auto-logon now works,, joined to the domain… Read more »

First of all, thank you for all your work in creating and supporting this Kit I am currently using it with no configuration changes to deploy a test environment with an DC, CM and PC vm's. The DC and PC vm's install perfectly fine but the CM is not installing Config Manager at all as per the task sequence. Checking the configmgrsetup.txt in the CM VM's I find an error line of : "ERROR: Faied to find the latest ADK version. Please install it first. $$" I have confirmed adksetup is in the correct source folder and even checked over… Read more »

Hi joseluiscc, send me an email, and I can help you offline. Email info is on the About page.

joseluiscc

Hi everybody, everything works great but I'm unable to boot from HydrationSC2012R2.iso…just a BSOD with 0xc000021a….

Congratulations Johan

Proverka

I automate the deployment of SQL, ADK, CM, through Config Manager, but I need to automate the installation of the domain through the MDT. but suddenly found it! it's just fantastic!!!! Also works with SQL SP2 ! thanks a lot!

Nothing I have seen, but send me an email and I can help you offline. You find the contact info on the about page.

mayurpatel

After I posted my above question I decided to rebuild DC01 in my setup a couple of times and try to troubleshoot from the logs. I can confirm the reason the CA features are not installing is because there are some errors encountered by the DHCP Task Sequence and below are the errors. I am curious to know if others have come across similar issues when building DC01? I have not modified anything in the scripts. Executing command line: %TOOLROOT%bddrun.exe /runas cscript.exe "%SCRIPTROOT%ZTIAuthorizeDHCP.wsf" The execution of the group (Install DHCP) has failed and the execution has been aborted. An action… Read more »

I have just started to get familiar with the newer Hydration Kit that you have created. A Big thanks to you! Being of basic knowledge and experience when it comes to the MDT tool, I have managed to get the kit imported and deployed my first virtual machine (DC01) on my lab vSphere ESXi host. Took a little bit of figuring around – For some reason the import script did not copy the CustomSettings_XX files into the Control folder and each time I the install process started but failed. In the end I managed to go through the TS and… Read more »

cm-pysc

I'd heard talk about this for a while, but never had chance to use it…..now I have – very impressed, thank you for all the hard work that has clearly gone in to this!

The fix for PXE bug is also included in CU1 (and CU2) for ConfigMgr 2012 R2,

Change names is quite well explained in the "Additional Configuration Notes" section.

funky

thanks for the hard work on this. the system is brilliant and will certainly help me in my test lab.

Can you point in the direction of all the scripts required to change the domain name? I see there is a Configure AD script. Anything else?

jaminben

This is probably the best thing I've ever seen for setting up a test environment quickly and easily… love it.

However (there's always a however), if like me you wanted to test out some SCCM PXE deployment setups and WDS wouldn't start check the link below for the fix.

support.microsoft.com/kb/2712387

Once again… THANK YOU

Check the Install-Orchestrator2012R2.wsf script, I'm reading properties set in the OR01.ini file in that script. The TS environment object is an excellent way to pass parameters to scripts from your rules file (.ini-files).

dwchan69

Looks like I got it working finally. But I do have one question. Instance of setting the SQL SA password within the wsf, probably it will be safer to pull this into from the MDT database or customsettings.ini. Database probably is out as I will need to edit new database tables.

sFile = oUtility.ScriptDir & "sourcesetup.exe"
sIniFile = oUtility.ScriptDir & "ConfigurationFile.ini"
sSAPWD = "saP@ssw0rd"

What would be the proper syntax to pull the SQL SA password from a custom value I define in the main customsettings.ini ?

I see the oLogging line, which file does this output to? Keep in mind, I have all the log set to my mdt server as the local minnt get wipe by the time I get to it.

There is a oLogging line just before that will echo the command into the script log file.

The SQL log will also tell you what command line the script tried to run.

Yes I did. I basically change the database location from E to C, as I only need one drive to test and include securitymode="SQL". I also try your script and it is still failing. I run the command manually without issue. What is the easiest way for me to get an output of the actual command it try to execute? Could it be a path or permission issue? on a same note, what user account does MDT use to install application using wsf? As I did conclude that it is trying to install this as domainadmin. Does it has to… Read more »

Looks about right, did you change the authentication mode to mixed?

SECURITYMODE="SQL"

You can also specify the SAPWD value in the configurationfile.

Quick question, I need to modified the packaged task sequence for SQL, as I need to change the SQL install string to include /SAPWD="saP@ssw0rd". From setup.exe /Configurationfile="configurationfile.ini "tosetup.exe /configurationfile="configurationfile.ini" /SAPWD="saP@ssw0rd" Here is my modification (with include an assign variable 'sSAPWD' to the function) but it is bombing out . Function ZTIProcess() Dim sFile Dim sIniFile oLogging.CreateEntry "Install SQL Server 2012 SP1: Starting SQL Server 2012 SP1 installation", LogTypeInfo ' Install SQL Server 2012 sFile = oUtility.ScriptDir & "sourcesetup.exe" sIniFile = oUtility.ScriptDir & "ConfigurationFile.ini" sSAPWD = "saP@ssw0rd" If not oFSO.FileExists(sFile) then oLogging.CreateEntry "Install SQL Server 2012 SP1: " & sFile &… Read more »

Good catch, and yes, if you change the default AD settings, they must be correct 🙂 To raise forest functional level, the domain functional level must be at that corresponding forest functional level or higher.

Thanks for pointing me to the log location. It turns out to be a domainlevel setting issue,

Doesn't work
forestlevel=5
domainlevel=4

change to

forestlevel=5
domainlevel=5

Even though dcpromo is deprecated as an interactive command line in Windows Server 2012 (replaced by server manager, which in turn uses powershell for its dcpromo stuff) dcpromo still supported in unattend mode which the ZTIconfigure-ADDS.wsf script is using. To troubleshoot dcpromo, check the logs in C:Windowsdebug (DCPROMO.LOG, dcpromoui.log and dcpromoui.001.log). Most times DC01 fails it's because a missing network adapter in the vm guest, or an incorrect disk configuration, not matching the settings in the DC01.ini rules/answer file. If you still have issues, send me an email and I can follow-up offline. You find my contact info in the… Read more »

I am having issue with DC01 task sequence. I am trying to setup a W2K12 R2 DC, but the ZTIconfigure-ADDS.wsf seem to use dcpromo which is not support on W2K12. What is the resolution or am I missing something here?

Since the task sequnces in the hydration kit are computer based, you should use computer based rules, and not roles.

Oops, sorry for the re-post. Can you recommend which database rules I should use for this? (e.g. computer or roles)

Is it possible (e.g. add entries to the MDT database) so that MDT wizard can pick and choose which Task Sequence it will use (versus the current manual selection) based on either the virtual machine name or MAC address?

Sure, I used to have it that way, before discovering people were having a hard time creating VMs with the same mac addresses I was using 🙂

Simply add the machines by mac address into the database, and specify the SkipTaskSequenceID=YES as well as the TaskSequenceID value.

This is amazingly useful, but I do have one quick question. Is it possible to configure the MDT database so that it will deploy predetermine X number of VM and assign them to specific Task Sequence. For example, right now, I still have to create the VMs (for say), mount the litetouch ISO, boot, and pick my task sequence manually. I can easily automate the VMs creation, ISO mount, power it on, and have it skip the Task Sequence selection. But what I do not know if it is possible that the MDT wizard can determine which Task Sequence to… Read more »

Verify that HTA (mshta.exe) is present in the X:WindowsSystem32 folder after booting. I have seen antivirus software blocking the injection of HTA into the boot image.

kevinwheeler

Oh, I'm deploying it in an Vsphere Vcenter 5.5 environment

I'm trying to use the hydrationSC2012R2 ISO to build DC01, but it just sits at the Solution Accelerators page with the cmd prompt. Am I doing something wrong? Thanks.

I answered your other post, no need to cross-post 🙂

galicea

Hello, I have been able to use the Hydration kit for SCCM 2012 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 to note, other than the… Read more »

9 years ago

Send me an email, and I can help offline (see the About page for contact info)

wingernew3

I redownloaded the Configuration Manager ISO and redownloaded the PreReqs. The SHA1 hash on the iso agrees with the one published on the web site. Neither had any effect. I still get the same error. I am using the Configmanager ISO from technet. mu_system_center_2012_r2_configuration_manager_x86_and_x64_dvd_2926949.iso Do you think this might be something to do with the version of CM? ERROR(13): Failed to iterate cab file.~ $$ERROR(13): Failed to expand the look up table files to the folder: E:Program FilesMicrosoft Configuration ManagerAI.~ $$ERROR: Failed to import Asset Intelligence data into the site database.~ $$~Setup cannot create the required database tables. Contact your… Read more »

I got the same issue once when the ConfigMgr 2012 R2 setup files were corrupt. Either the pre-req files or the core setup files, I just replaced both and the setup run through fine again.

Update. I switched to the 64bit full slipstream version of the sql server 2012 iso and get the exact same errors. That makes me believe that its not the sql install at all. Now I'm really stumped. Any help or even a new direction to troubleshoot would be appreciated. Thany You.

I love this hydration kit. It's bloody great. I have been able to build the hydration share and the client computers but am stuck on the Configuration Manager computer. I cant seem to get passed the SQL server install. I am getting the following error message in the Setup log. ERROR(13): Failed to iterate cab file.~ $$ERROR(13): Failed to expand the look up table files to the folder: E:Program FilesMicrosoft Configuration ManagerAI.~ $$ERROR: Failed to import Asset Intelligence data into the site database.~ $$~Setup cannot create the required database tables. Contact your SQL administrator. $$ I thought it might be… Read more »

The Hydration Kit for System Center 2012 R2 is available for download

The Hydration Kit contents

Overview

Step-by-Step Guide

Step 1a – Download the mandatory software

Step 1b – Download the optional software

To deploy the Windows 7 SP1 clients (PC0001, PC0003 and PC0004), you need:

To deploy the Windows 8.1 x64 client (PC0002), you need:

To deploy the System Center 2012 R2 Configuration Manager server (CM01), you need:

To deploy the System Center 2012 R2 Data Protection Manager server (DPM01), you need:

To deploy the Microsoft Deployment Toolkit (MDT) 2013 server (MDT01), you need:

To deploy the System Center 2012 R2 Operations Manager server (OM01), you need:

To deploy the System Center 2012 R2 Orchestrator server (OR01), you need:

To deploy the System Center 2012 R2 Service Manager server (SM01), you need:

To deploy the System Center 2012 R2 Virtual Machine Manager server (VMM01), you need:

Step 2 – Prepare the Hydration Environment

Populate the hydration deployment share with the mandatory files

Populate the hydration deployment share with the files for the Windows 7 SP1 Clients

Populate the hydration deployment share with the files for the Windows 8.1 Client

Populate the hydration deployment share with the files for System Center 2012 R2 Configuration Manager

Populate the hydration deployment share with the files for System Center 2012 R2 Data Protection Manager

Populate the hydration deployment share with the files for System Center 2012 R2 Operations Manager

Populate the hydration deployment share with the files for System Center 2012 R2 Orchestrator

Populate the hydration deployment share with the files for System Center 2012 R2 Service Manager

Populate the hydration deployment share with the files for System Center 2012 R2 Virtual Machine Manager

Populate the hydration deployment share with the files for Microsoft Deployment Toolkit 2013

Create the hydration ISO (MDT 2013 offline media item)

Step 3 – Deploy the virtual machines

Additional Configuration Notes:

Johan Arwidmark