Atea Global Services is pleased to announce the release of Jumpstart Hydration 1703


  • Why is it called Hydration 1703?
    • We are adopting Microsoft’s versioning system for continuous delivery.
    • We released this version in March 2017


  • What’s new in Hydration 1703?
    • Windows Server 2016 Compatible
    • SCCM 1606
    • MDT Build 8443
    • Windows ADK for Windows 10 version 1607
    • SQL Server 2016 SP1
    • Client Deployment Complete (CDC) 3.0
    • Jumpstart Web Service 2.7
    • OSD Task Sequence ready for SCCM 1610
    • Images included:
      • Windows 10 Enterprise 1607 x64
    • Hydration Wizard improvements:
      • Bug fixes based on feedback from consultants.
      • The wizard now sets sharing permissions if you use the wizard to create the Hydration share.
      • The auto logon account credentials are now saved from time to time.
    • Hydration Bug fixes:
      • Stability and quality improvements
      • Reporting Services should now work OOB
      • OSD Scripts based on UUID instead of MAC should work better than before
      • PXE boot image download speed is much faster now


  • Why does it install SCCM 1606 instead of 1610?
    • o It is not supported, even though it’s possible, to do a full media installation of SCCM 1610.
    • o However, we do recommend that you immediately upgrade to 1610 from within the console.


  • What are some known issues?
    • Command Support (F8) does not work on the boot image even though it’s checked.
      To fix this, uncheck and apply. Select not to update distribution points. Check the box again, click apply and update the DP.
    • ‘Use this boundary group for Site Assignment’ is not checked by default.
    • PowerShell Cmdlets for ConfigMgr is not the latest version due to a bug in Move-CMObject.
      This is solved in SCCM 1610 and will be upgraded automatically if you upgrade to SCCM 1610.


  • What can I do if I’m having problems with the Hydration 1703?
    • Watch the release webinar available on the ftp and make sure that you understand how to use it.
    • Contact product support describing your issue. We will make sure that it works for you.


A big thank you to everyone who has contributed to his release!