Thanks, Kari. Much appreciated. I think I'm all good now. I may try some of the other capabilities such as installing apps, but that's a project for another day.
For now, I'm going to focus on getting a permanent MDT system setup for deployments.
Thanks again!
Tweet
— Twitter API (@user) View on Twitter
IMPORTANT!
Windows 10 deployments using the Microsoft Deployment Toolkit (MDT) build 8456 fail when used with the Windows Assessment and Deployment Kit (ADK) for Windows 10, version 2004.
The BIOS firmware type is incorrectly identified as UEFI resulting in failures when refreshing an existing computer with a new version of Windows.
More information and update to resolve this issue: https://support.microsoft.com/en-us/...oyment-toolkit
Kari
Microsoft has now released a fix for this issue:
https://support.microsoft.com/en-us/...oyment-toolkit
EDIT: I must be blind. The original message already states that a fix is available with the same link. My apologies for the oversight.
Kari, many thanks for the excellent tutorial. I'm totally new to MDT and the tutorial was very thorough. If I automated an installation using simply WSIM rather than going via the MDT route, then I'd need to create an autounattend.xml answer file to deal with the settings for the early WinPE and offlineservicing stages of installation. In MDT however, we only deal with an unattend.xml file which as I understand it is for the later configuration stages only. Do you know what MDT is doing behind the scenes for the early WinPE / offlineseevicing stages? Is it creating an autounattend.xml file? Thanks in advance!
@Kari, I have an MDT deployment issue that I'm hoping you may have an answer for.
On most of my systems, Windows is installed on Disk 0. However, I have one system that enumerates SATA disks before NVMe disks. As a result, the correct disk for installation on this system is disk 2.
When I create unattended installation media I simply omit the disk to which Windows should be installed. This pauses the installation and allows me to choose what disk I want to install onto. I know that I could specify disk 2, but I prefer to allow user input so that I can use the same installation image for systems needing installation on disk 0 as well as my system where disk 2 is the right choice.
Do you know if there is a way to accomplish the same thing with MDT? When I look at the task sequence in MDT I see that the option called "Select the location where you want to apply this operating system" is set to "Logical drive letter stored in a variable".
Do you know if it is somehow possible to get the installation to pause to have the user select the installation location much as I can do with unattended setup?
Kari will give you a much better answer then I can. I've only built MDT LTI deployments. But from reading, I'm also aware of MDT User Driven Interface (UDI) which allows you to build custom screens to prompt for user input for a Task Sequence. However, MDT UDI can only be used if you're running SCCM. If you're running SCCM you might find these interesting reads as a place to start till Kari gives you the definitive answer :)
Drop-down menu for Task Sequence Variables?
Customizing UDI Wizard with UDI Designer Using SCCM | ConfigMgr
Thanks, ComputerGeek. I appreciate the information.
Exactly as @ComputerGeek said. First, you need to setup Windows Server as domain controller. When done, setup SCCM in domain controller. Only then can you use MDT UDI.
- Windows Server 180 day trial download: https://www.microsoft.com/en-us/eval...ws-server-2019
- SCCM 180 day trial download: https://www.microsoft.com/en-us/eval...em-center-2019
I've written a tutorial on setting up a domain controller: Windows Server 2016 - Setup Local Domain Controller
A step-by-step guide on setting up SCCM: https://social.technet.microsoft.com....%20See%20More.
Kari
Thanks, Kari. I was trying to avoid having to use Windows Server or SCCM as I don't have access to either any longer.
Well, at least I have an answer. Back to unattended setup I go!
Thanks again for the response.
EDIT: I know you linked to eval copies, but I wanted something more permanent. I also don't want to go through the hassle of setting up a domain in my home environment
Quote