You are here:   Research
  |  Login

Welcome to my blog, quickest way to find articles is usually to search for them.

Minimize
Search in All Title Contents
 
     

Hydration Kit For Windows Server 2016 and ConfigMgr Current / Technical Preview Branch

Dec 14 2016

This Kit builds a complete ConfigMgr v1606/1610 with Windows Server 2016 and SQL Server 2016 SP1 infrastructure, and some (optional) supporting servers. This kit is tested on both Hyper-V and VMware virtual platforms, but should really work on any virtualization platform that can boot from an ISO. The kit offers a complete setup of both a primary site server running ConfigMgr Current Branch v1606 (server CM01), as well as a primary site server running ConfigMgr Technical Preview Branch v1610 (server CM02). You also find guidance on upgrading these platform to the latest build.

Update Dec 19, 2016: Fixed a product key bug, and added MDT 8443 and SQL Server 2016 SP1 support

Download Link: Hydration Kit For Windows Server 2016 and ConfigMgr Current / Technical Preview Branch

Note #1 - Customizations: This hydration kit install all servers in the corp.viamonstra.com domain, on the 192.168.1.0/24 network. If you rather use your own domain, IP addresses etc. check out the Next Step - Customizing the Hydration Kit section in the end of this post for instructions on how to customize this kit. Also, for a complete IP plan of the ViaMonstra network, check this link: http://viamonstra.com/?page_id=25

Note #2 - Internal network and Internet Access: Since one of the virtual machines (DC01) is also a DHCP Server, its highly recommend to deploy all the virtual machines on an internal virtual network, and then use the NAT feature in either Hyper-V or VMware to give the virtual machines internet access. For super-easy Internet access, while still having the VMs on an isolated network, read this shiny post from Ami Casto (@MDTPro): http://deploymentresearch.com/Research/Post/558/Setting-Up-New-Networking-Features-in-Server-2016 .

Note #3 – Advanced networking: For more complex networks (multiple sites etc.), you may want to use a virtual router. More info here: http://deploymentresearch.com/Research/Post/285/Using-a-virtual-router-for-your-lab-and-test-environment

Hydration Kit Archive (older hydration kits)

Are you looking for any of the previous hydration kits? Look no further, they are right here:

 

Hydration Kit For Windows Server 2016 and ConfigMgr Current / Technical Preview Branch

So, again, this Kit builds a complete ConfigMgr v1606/1610 site server with Windows Server 2016 and SQL Server 2016 SP1 infrastructure, and some (optional) supporting servers

Servers

This kit allows you to automatically deploy the below list of servers. The only server you really need to build first is DC01, since that’s the domain controller, and the CM01 server will join the domain. Turns out joining a domain is tricky without a domain controller :)

Main servers

  • DC01. Windows Server 2016, DC, DHCP and DNS
  • CM01. Windows Server 2016, SQL Server 2016 SP1, ConfigMgr Current Branch v1606 (and upgrade to v1610)

Optional supporting servers for ConfigMgr Technical Preview Branch, and MDT Lite Touch (reference image builds)

  • CM02. Windows Server 2016, SQL Server 2016 SP1, ConfigMgr Current Branch Technical Preview 1610 (and upgrade to v1611)
  • MDT01. Windows Server 2016, SQL Server 2016 SP1 Express
  • WSUS01. Windows Server 2016, SQL Server 2016 SP1 Express

 

Overview

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

  1. Download the necessary software
  2. Prepare the Hydration Environment
  3. Deploy the virtual machines

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

TSList 
The Deployment Wizard displaying the available task sequences.

 

 

image 
The CM01 task sequence, building a complete ConfigMgr Current Branch v1606 site server with SQL Server 2016 SP1.

 

Step-by-Step Guide 

Step 1 - Download the software

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

For the main servers, you need to download the following software:

  • The Hydration Kit sample files (download)
     
  • BGInfo
     
  • MDT 8443
     
  • A reference image of Windows Server 2016 Standard, fully patched, and .NET Framework 3.5 added to it. If you don’t have one, follow this guide to create one: http://deploymentresearch.com/Research/Post/578/Building-the-perfect-Windows-Server-2016-reference-image

    Note: Yes, you should really use a reference image instead of just the default (unpatched) media :)
     
    • SQL Server 2016 Standard with SP1 x64      
    • SQL Server Management Studio (separate download, no longer included in SQL Server 2016)
       
      • ConfigMgr v1606 + PreReqs

        Note: To download the ConfigMgr pre-requisites, run the SMSSETUP\BIN\X64\Setupdl.exe application from the ConfigMgr installation files.
         
      • Windows ADK 10 v1607

        Note: To download the complete standalone Windows ADK 10 setup, run adksetup.exe /layout "C:\Setup\Windows ADK 10 v1607
         
                    

        image
        The Windows ADK 10 folder, after download the standalone setup.

         

         
        Running the Setupdl.exe to download the ConfigMgr Current Branch PreReqs.

        For the optional servers, you need to download the following software:

               
          • SQL Server 2016 SP1 Express (use the SQLServer2016-SSEI-Expr.exe web installer to download SQLEXPR_x64_ENU.exe media)
             
            • ConfigMgr v1610 Technical Preview + PreReqs

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

             

            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 10 v1607 (adksetup.exe) selecting only the following components:
               

              Deployment Tools
              Windows Preinstallation Environment (Windows PE)
              Imaging and Configuration Designer (ICD)
              Configuration Designer
              User State Migration Tool (USMT)

              Note:
              The last three are not used by the hydration kit, but are still quite useful to have, so I usually install them too.  

                         
                      
              ADK2
              The Windows ADK 10 v1607 Setup running on Windows Server 2016 (if running on Windows Server 2012 R2 you don’t see UE-V or App-V).
               

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

              C:\HydrationCMWS2016\Source

              image       
              The extracted hydration kit files.
                

            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 or Windows Server 2016 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:\HydrationCMWS2016\Source\CreateHydrationDeploymentShare.ps1       

             

            Populate the hydration deployment share with the main server setup files

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

              C:\HydrationCMWS2016\DS\Applications\Install - BGInfo\Source

            2. Copy your Windows Server 2016 reference image (have to be named REFWS2016-001.wim), to the following folder:

              C:\HydrationCMWS2016\DS\Operating Systems\WS2016
                     
              Note: Again, if you don’t have a reference image of Windows Server 2016 Standard, fully patched, with.NET Framework 3.5 added to it. Please follow this guide to create one: http://deploymentresearch.com/Research/Post/578/Building-the-perfect-Windows-Server-2016-reference-image            
               
                
              image
              The Windows Server 2016 Standard reference image copied to the deployment share.

               

               
            3. Copy the complete set of Windows ADK 10 v1607 installation files (3.4 GB) to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Install - Windows ADK 10\Source
               
            4. Copy the SQL Server 2016 with SP1 x64 installation files (the content of the ISO, not the actual ISO) to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Install - SQL Server 2016\Source
               
               

              image         
              The SQL Server 2016 with SP1 x64 installations files copied.
               

            5. Copy the SQL Server Management Studio installation file to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Install - SQL Server Management Studio

            6. Copy the ConfigMgr v1606 installation files (extract the download) to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Install - ConfigMgr\Source

            7. Copy the ConfigMgr v1606 PreReqs files to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Install - ConfigMgr\PreReqs        
            8.                
            9. Copy the ConfigMgr EXTADSCH.exe file (SMSSETUP\BIN\X64) to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Configure - Extend AD for ConfigMgr\Source
            10. Copy the MDT 8443 installation file (MicrosoftDeploymentToolkit_x64.msi) to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Install - MDT


             

            Populate the hydration deployment share with the optional files for CM02, MDT01 and WSUS01

            Note: These steps are only needed if you want to deploy CM02, MDT01 and WSUS01. If you don’t want this, skip to the next section.

            1. Copy the ConfigMgr Technical Preview v1610 installation files (extract the download) to the following folder:

              C:\HydrationCMWS2016\DS\Applications\Install - ConfigMgr Technical Preview\Source

              1. Copy the ConfigMgr Technical Preview v1610 PreReqs files to the following folder:

                C:\HydrationCMWS2016\DS\Applications\Install - ConfigMgr Technical Preview\PreReqs        
                1.          
              2. Copy the SQL Server 2016 SP1 Express setup file (SQLEXPR_x64_ENU.exe) to the following folder:

                C:\HydrationCMWS2016\DS\Applications\Install - SQL Server 2016 SP1 Express\Source

               

              Create the hydration ISO (MDT offline media item)

              1. Using Deployment Workbench (available on the Start screen), expand Deployment Shares, and expand Hydration ConfigMgr.
                 
              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 applications.

               

              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 (HydrationCMWS2016.iso ) in the C:\HydrationCMWS2016\ISO folder. The HydrationCMWS2016.iso should be about 14-15 GB in size.

              image 
              The HydrationCMWS2016.iso with both main and optional installation files.

               

              Step 3 - Deploy the virtual machines

              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:\HydrationCMWS2016\Source\Extra folder for two sample scripts. One for building Generation 1 VMS, and one for building Generation 2 VMs.

              Note: If using Hyper-V, do Not configure the virtual machines for dynamic memory. If you do, the installation will take forever. Dynamic memory can be set when installation (hydration) is completed.

               

              Deploying DC01

              Using Hyper-V Manager or VMware Workstation/Sphere, create a virtual machine with the following settings:

              • Name: DC01
              • Hard drive: 100 GB (dynamic disk)
              • Memory: 1 GB (static memory if using Hyper-V)
              • Network: Your lab network
              • Image file (ISO): C:\HydrationCMWS2016\ISO\HydrationCMWS2016.iso
              1. Start the DC01 virtual machine. After booting from HydrationCMWS2016.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 CM01 virtual machine.

              Deploying CM01

              Once the domain controller (DC01) is up and running, you can deploy the CM01 virtual machine. Don’t forget to leave DC01 running while deploying CM01 since it is joining the domain during deployment. Use the following settings for the CM01 virtual machine:

              • Hard drive: 300 GB (dynamic disk)
              • CPU: 2 vCPUs minimum, 4 vCPUs recommended
              • Memory: 6 GB RAM minimum, 16 GB recommended (static memory if using Hyper-V)

               

              Post configuration of CM01

              After deploying CM01, make sure the machine has access to Internet. Again either via Configure NAT in Hyper-V or VMware, or by setting up a virtual router.

              Then, in the Administration workspace, in the Updates and Servicing node. Click Check for Updates, and then install the latest current branch (currently v1610)

              image
              The Updates and Servicing node showing the ConfigMgr Current Branch v1610 update. 

                  Deploying CM02 (Optional)

                  Once the domain controller (DC01) is up and running, you can deploy the CM01 virtual machine. Don’t forget to leave DC01 running while deploying CM02 since it is joining the domain during deployment. Use the following settings for the CM02 virtual machine:

                  • Hard drive: 300 GB (dynamic disk)
                  • CPU: 2 vCPUs minimum, 4 vCPUs recommended
                    • Memory: 6 GB RAM minimum, 16 GB recommended (static memory if using Hyper-V)

                     

                    Post configuration of CM02

                    After deploying CM02, make sure the machine has access to Internet. Again either via Configure NAT in Hyper-V or VMware, or by setting up a virtual router.

                    Then, in the Administration workspace, in the Updates and Servicing node. Click Check for Updates, and then install the latest technical preview (currently v1611)

                    image
                    The Updates and Servicing node showing the ConfigMgr Technical Preview v1611 update. 

                     

                    Deploying MDT01 (Optional)

                    Once the domain controller (DC01) is up and running, you can deploy the optional MDT01 virtual machine. Don’t forget to leave DC01 running while deploying MDT01 since it is joining the domain during deployment. Use the following settings for the MDT01 virtual machine:

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

                     

                    Deploying WSUS01 (Optional)

                    Once the domain controller (DC01) is up and running, you can deploy the optional WSUS01 virtual machine. Don’t forget to leave DC01 running while deploying WSUS01 since it is joining the domain during deployment. Use the following settings for the WSUS01 virtual machine:

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

                     

                    Next Step - Customizing the Hydration Kit:

                    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:\HydrationCMWS2016\ISO\Content\Deploy\Control folder.

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

                    image 
                    The configuration files for the Hydration Kit.

                     

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

                    • C:\HydrationCMWS2016\DS\Applications\Install - ConfigMgr\ConfigMgrUnattend.ini
                    • C:\HydrationCMWS2016\DS\Applications\Install - SQL Server 2016\ConfigurationFileConfigurationManager.ini

                     

                    For ConfigMgr (CM02) you need to update the following files::

                    • C:\HydrationCMWS2016\DS\Applications\Install - ConfigMgr Technical Preview\ConfigMgrUnattend.ini
                    • C:\HydrationCMWS2016\DS\Applications\Install - SQL Server 2016\ConfigurationFileConfigurationManager.ini

                      If you need to change the various service accounts, you need to to modify the Configure-CreateADStructure.wsf script in the C:\HydrationCMWS2016\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_thumb1
                      The Authorize DHCP action in the DC01 task sequence.

                       

                      Written by Johan Arwidmark








                      Happy deployment, and thanks for reading!
                      / The Deployment Research team



                      Ami Casto

                      Johan Arwidmark

                      Blog Archive

                      Minimize