talksr Posted April 18, 2019 Posted April 18, 2019 Hello, Can anyone give me some ideas on why my MDT is not working when I am network booting and installing Windows 10? I have a Windows 10 1809 image in WDS which is working perfectly. In MDT, I have added the same image (tried importing it from WDS but it didn't work, so actually imported the image separately). I have it showing in Operating Systems, I have a Task Sequence set up for it also. I have imported Office 2016 x32 under Applications. Again, I have a Task Sequence set up for Office along with a config XML file. Where am I going wrong? This used to work perfectly before, you would F12 to boot to network, Windows would install and MDT would ask you to sign onto the domain and pick a station name. Now, all I am getting is a bog standard WDS install of Windows 10, where I am having to manually add in user accounts, put computer on domain etc. Any ideas would be great.
strawberry Posted April 18, 2019 Posted April 18, 2019 Have you imported the litetouchpe image into WDS so it can boot into MDT?. See add a boot image https://www.petri.com/deploy-windows-10-using-mdt-wds-part-2-install-wds-boot-pxe-client 1
RLR Posted April 18, 2019 Posted April 18, 2019 (edited) Not sure if you have this setup correctly. You create a windows PE Boot image in MDT which you then import into WDS. When PXE booting the computer, it will download the Windows PE image from WDS and then MDT will run a wizard (depending on your MDT setup) which you will need to fill in some steps. It is possible to have WDS install an image directly onto the machine but this won't use any of MDTs task sequences. Are you PXE booting the Windows PE boot image from MDT? This is generated when you update the deployment share and will be in your \\Depoymentshare\Boot folder. Edit: Also with the latest versions of MDT you need to download the Windows PE add-on additionally to MDT: https://docs.microsoft.com/en-gb/windows-hardware/get-started/adk-install#winADK Edited April 18, 2019 by RLR 1
talksr Posted April 18, 2019 Author Posted April 18, 2019 Have you imported the litetouchpe image into WDS so it can boot into MDT?. See add a boot image https://www.petri.com/deploy-windows-10-using-mdt-wds-part-2-install-wds-boot-pxe-client Thank you for that. Interesting. I had it there, I know I did, but it was disabled for some reason. Not sure what that was all about. Re-enabled and now it seems to be working. Will do a quick test image and see what happens. Does anyone know how you can set the Locale & Time settings? My language etc are all English UK, but getting US - English for keyboard settings and UTC-0800 Pacific Time as default time setting. They are changeable on the dropdown but it is a pain and I deliberately downloaded the Windows 10 International not English version.
strawberry Posted April 18, 2019 Posted April 18, 2019 https://scriptimus.wordpress.com/2011/04/16/mdt-2010-regional-settings/
talksr Posted April 18, 2019 Author Posted April 18, 2019 https://scriptimus.wordpress.com/2011/04/16/mdt-2010-regional-settings/ Ahah, thank you for this. Do you know where the CustomSettings.ini file is located? The helpful guide doesn't mention it? Other than that, the example on that page is exactly what I need so I can just copy and paste.
Rob_D Posted April 18, 2019 Posted April 18, 2019 Ahah, thank you for this. Do you know where the CustomSettings.ini file is located? The helpful guide doesn't mention it? Other than that, the example on that page is exactly what I need so I can just copy and paste. If I recall correctly you get to the ini by right clicking on the deployment share (in the MTDT workbench) and going to properties. It should be on first tab.
talksr Posted April 18, 2019 Author Posted April 18, 2019 If I recall correctly you get to the ini by right clicking on the deployment share (in the MTDT workbench) and going to properties. It should be on first tab. Hmm, ok. I right clicked MDT Deployment Share, went to properties and got this.. The only area with an ini files seems to be here, but it is Bootstrap.ini which is not the right one..
RLR Posted April 18, 2019 Posted April 18, 2019 If I recall correctly you get to the ini by right clicking on the deployment share (in the MTDT workbench) and going to properties. It should be on first tab. This, the tab is actually called Rules although it edits a file called customsettings.ini
talksr Posted April 18, 2019 Author Posted April 18, 2019 This, the tab is actually called Rules although it edits a file called customsettings.ini Oh, in that case it must be here: Is it just a case of me pasting in the following below the last line which reads: SkipBitLocker=NO SkipLocaleSelection=YES KeyboardLocale=0809:00000809 UserLocale=en-GB UILanguage=en-GB SkipTimeZone=YES TimeZoneName=GMT Standard Time 1
RLR Posted April 18, 2019 Posted April 18, 2019 It's probably worth editing the Bootstrap.ini to use the the en-GB also: SkipBDDWelcome=YES KeyboardLocale=en-GB The SkippBDDWelcome gets rid of the welcome screen which is an extra click. It's not needed. Remember, this is in the bootstrap.ini and not rules/customsettings.ini. 2
RLR Posted April 18, 2019 Posted April 18, 2019 Oh, in that case it must be here: Is it just a case of me pasting in the following below the last line which reads: SkipBitLocker=NO SkipLocaleSelection=YES KeyboardLocale=0809:00000809 UserLocale=en-GB UILanguage=en-GB SkipTimeZone=YES TimeZoneName=GMT Standard Time Yes, just copy and paste it into the rules tab. You can remove the spaces if you want. 2
talksr Posted April 18, 2019 Author Posted April 18, 2019 Thank you everyone, it works a treat. So much slicker now. Really happy with that. Thanks again! 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now