locked
Windows 10 October 2018 Update (v1809) now available - what about MDT? Is it compatible? RRS feed

  • Question

  • I downloaded my MSDN iso of v1809 a few hours ago and also noticed the new ADK is available. 

    Is MDT 8450 able to work with Windows 10 v1809/ADK v1809?

    Thanks,

    B


    Wednesday, October 3, 2018 3:02 AM

All replies

  • Not sure yet. But take a look at this. The separated windows PE from ADK

    https://docs.microsoft.com/en-us/windows-hardware/get-started/what-s-new-in-kits-and-tools

     
    Wednesday, October 3, 2018 8:11 PM
  • It's billed as an addon now - but still should be able to be installed during the ADK install:

    https://deploymentresearch.com/Research/Post/1675/Installing-Windows-ADK-10-v1809-and-WinPE-Addon-Unattended

    I also sent an email to Johan and he said that MDT 8450 should work just fine with v1809 as long as the new ADK (v1809) is in place

    Cheers,

    B

    Wednesday, October 3, 2018 8:42 PM
  • With MDT 8450, ADK 1809 and Windows 10 1809, After the OS deployment it's not going to application installation phase, it's simple shows windows login page. 

    I am deploying the captured image, VM was upgraded from 1803 to 1809 and then captured. 

    Any advice to troubleshoot this? 

    Thursday, October 4, 2018 9:56 AM
  • Do you need to update deployment share after install of new ADK and PE?
    Thursday, October 4, 2018 1:46 PM
  • Do you need to update deployment share after install of new ADK and PE?

    I always do.

    B

    Thursday, October 4, 2018 2:20 PM
  • You need to update your share, regenerate the boot images and replace your Litetouch-Wims  in WDS!

    Toni



    • Edited by tonibert Friday, October 5, 2018 9:08 AM
    Friday, October 5, 2018 9:06 AM
  • I've been unable to get this to deploy properly, using the .iso that was on the volume license center.  It was missing the platform when you add it to mdt, which prevented task sequences associated with it from showing up.  After manually adding the proper platform afterwards the task sequence fails at some pointed during 'install operating system' with 0x80004005.  

    Upon checking the volume license now for an updated .iso they seem to have removed it entirely, can't download version 1809 from the volume license center anymore right now.  Hoping that means they are fixing something with it for whenever it reappears for download...

    Tuesday, October 9, 2018 6:48 PM
  • I've been unable to get this to deploy properly, using the .iso that was on the volume license center.  It was missing the platform when you add it to mdt, which prevented task sequences associated with it from showing up.  After manually adding the proper platform afterwards the task sequence fails at some pointed during 'install operating system' with 0x80004005.  

    Upon checking the volume license now for an updated .iso they seem to have removed it entirely, can't download version 1809 from the volume license center anymore right now.  Hoping that means they are fixing something with it for whenever it reappears for download...

    v1809 has been pulled completely for other more serious reasons than just MDT activities. The general consensus is to delete all existing ISOs that you downloaded and wait for new media.

    There are some very big issues with v1809 and I suspect the entire release is being reviewed from the top down - which will result in new media in the coming weeks.

    B

    Tuesday, October 9, 2018 7:15 PM
  • While we wait for Microsoft to re-release the 1809 downloads, does anyone know what happened to the Deployment Workbench? Is Version: 6.3.8443.1000 the current or old one? I had to uninstall the old ADK to get the new one on, but maybe parts of the old Deployment Kit stayed behind?

    Anyone know?

    TIA, David


    Tech Specialist

    Tuesday, October 16, 2018 3:37 PM
  • David,

    MDT 8450 is the current version. Deployment Workbench is a separate download and is not part of the ADK. 

    B

    Tuesday, October 16, 2018 4:29 PM
  • Thank you Bruce! Do you think there will be an updated version of the Workbench, or is it less dependent on the Windows version?

    David


    Tech Specialist

    Tuesday, October 16, 2018 5:02 PM
  • Thank you Bruce! Do you think there will be an updated version of the Workbench, or is it less dependent on the Windows version?

    David


    Tech Specialist

    David,

    To my knowledge - MDT (Workbench) has never been traditionally tied to any specific Windows - example is that we have used 8450 since last December with at least 3 versions of Windows 10.

    Not sure if we need anything for v1809 as of yet - MDT 8450 is working fine for me - just this week I did v1809 ENT and v1809 LTSC test deployments and all was well.

    ADK is a different story. You must use the ADK that matches each specific Windows release in order to use MDT to build images and task sequences and so on. Example: you cannot use the v1703 ADK to deploy v1809 images etc.

    B

    Tuesday, October 16, 2018 5:51 PM
  • Not sure if we need anything for v1809 as of yet - MDT 8450 is working fine for me - just this week I did v1809 ENT and v1809 LTSC test deployments and all was well.

    ADK is a different story. You must use the ADK that matches each specific Windows release in order to use MDT to build images and task sequences and so on. Example: you cannot use the v1703 ADK to deploy v1809 images etc.

    Two questions.

    1) I need to deploy both Windows 10 v1809 and v1709, but I can only install one ADK.  I should install ADK 1809, yes?  Should be backward compatible, yes?

    2) Do I need to install the ADKWinPE add-on for ADK 1809?  I noticed that with ADK v1709, MDT always builds the WIM/ISO files using the Windows 10 Ent v1709 Operating System I imported and not the WinPE from the Program Files\ADK folder.

    Thanks for help.


    -Tony

    Wednesday, October 17, 2018 11:18 PM
  • Not sure if we need anything for v1809 as of yet - MDT 8450 is working fine for me - just this week I did v1809 ENT and v1809 LTSC test deployments and all was well.

    ADK is a different story. You must use the ADK that matches each specific Windows release in order to use MDT to build images and task sequences and so on. Example: you cannot use the v1703 ADK to deploy v1809 images etc.

    Two questions.

    1) I need to deploy both Windows 10 v1809 and v1709, but I can only install one ADK.  I should install ADK 1809, yes?  Should be backward compatible, yes?

    2) Do I need to install the ADKWinPE add-on for ADK 1809?  I noticed that with ADK v1709, MDT always builds the WIM/ISO files using the Windows 10 Ent v1709 Operating System I imported and not the WinPE from the Program Files\ADK folder.

    Thanks for help.


    -Tony

    1. Yes. Install only one and install v1809

    2. Yes. Without the ADK Addon - not much will happen when building images for 1809 without it.

    B

    Thursday, October 18, 2018 11:46 AM
  • deployment of win10 1809 is successful only without adding packages otherwise it ends with error 0x80004005.


    • Edited by audigy Friday, October 26, 2018 7:36 AM
    • Proposed as answer by Dan Flynn (BU) Saturday, January 19, 2019 1:10 AM
    Friday, October 26, 2018 7:33 AM