mikkydoos Posted October 11, 2018 Posted October 11, 2018 (edited) Hi all... Hair is being pulled out!... please help. I'm deploying a Win10 1607 Enterprise LTSB image. I have images captured with WDS which when deployed via WDS refuse to answer my .xml file. (These images have been created manually and not with installed, configured or captured with MDT.) The images are sysprepped with: sysprep.exe /shutdown /oobe /generalize / (and with or without) /unattend:%local path to unnattend.xml%. What am I doing wrong here: Boot image isn't being selected at PXE boot. No .xml configuration is being applied [ATTACH=CONFIG]50533[/ATTACH] Setup prompts for boot image selection, install image, disk configuration etc etc still !!!!!! Where am I going wrong? Big cheers in advance ----------------------------------------------------------------------------------------------------------------------------------- en-GB en-GB en-GB en-GB en-GB en-GB 1 500 Primary true 2 Primary true NTFS System 1 1 NTFS OS C 2 2 0 true OnError 0 2 OnError XXXXXXXXXXXXXXXXXXXXXXXXXX true MySchool MySchool mydomain.com XXXXXXXXXXX UserAdmin GMT Standard Time en-GB en-GB en-GB en-GB en-GB true true true true 3 XXXXXXXXXXXXXX true User User Administrators User ----------------------------------------------------------------------------------------------------------------------------------- Edited October 11, 2018 by mikkydoos
HobGoblin Posted October 11, 2018 Posted October 11, 2018 Answer file validates okay for me, is it because there are spaces in the file path of the answer file? Every image that I see online of the "Enable unattended installation" page has no spaces in there. 1
mikkydoos Posted October 12, 2018 Author Posted October 12, 2018 Cheers for checking the validation @HobGoblin. I'll check that. I have a feeling I read something along those lines.
mikkydoos Posted October 12, 2018 Author Posted October 12, 2018 (edited) Update: Replacing spaces with %20 seems to have got the image picking up the answer file. How infuriating!!!! My last issue is that upon deployment its still showing the disk configuration screen. I've been over and over the .xml and I'm 100% it's correct. Does it matter that I'm installing on a VM ?? Can't see why. Edited October 12, 2018 by mikkydoos
Duke5A Posted October 12, 2018 Posted October 12, 2018 Sounds like you're building and deploying images the same way I do. I've got a few different answer files. I've got two client unattended files (one for UEFI and one for BIOS) that only contain settings that pertain to WDS initial questions after PXE booting, and one more for the image itself. Here are the two I use for client booting: BIOS x64 true 1 Primary true NTFS Local Disk C 1 1 0 true 0 1 UEFI x64 false 1 EFI 400 true 2 Primary 0 true OnError 0 2 With the above the initial disk and partition questions are answered. The answer file that is specific to the image is applied to the image properties in WDS. Hope this helps... 1
mikkydoos Posted October 15, 2018 Author Posted October 15, 2018 (edited) Thanks for posting that @Duke5A. Yes, I have one .xml that takes care of the pre-install config then another for post install. I notice in your disk configuration, you don't specify the 'system' partition whereas my WSIM does. 1 500 Primary I'll try your config without. EDIT: Hhhhmm. Your config with the system partiton works, although it doesn't create the system partition that would be during a manual install. I dont know if that would be a problem when it came to later. How odd !?!?!? Edited October 15, 2018 by mikkydoos
mikkydoos Posted October 15, 2018 Author Posted October 15, 2018 Right this is really stumping me.. According to MS this should be the correct config for BIOS disk partitioning for Windows 10 and Server 2016: ------------------------------------------------------------------------------------------ false 1 500 Primary true 2 Primary true NTFS System Reserved 1 1 NTFS Windows C 2 2 false 0 true OnError ------------------------------------------------------------------------------------------ But I can only get this to not prompt the disk config screen--> not specifying the system reserved partition. ------------------------------------------------------------------------------------------ true 1 Primary true NTFS Local Disk C 1 1 0 true ------------------------------------------------------------------------------------- Wtf ??
Duke5A Posted October 15, 2018 Posted October 15, 2018 Thanks for posting that @Duke5A. Yes, I have one .xml that takes care of the pre-install config then another for post install. I notice in your disk configuration, you don't specify the 'system' partition whereas my WSIM does. 1 500 Primary I'll try your config without. EDIT: Hhhhmm. Your config with the system partiton works, although it doesn't create the system partition that would be during a manual install. I dont know if that would be a problem when it came to later. How odd !?!?!? That config for BIOS booting that lacks the system reserved partition has been what I've used for years now. Windows 7, 8 and 10. I only added it when I needed to make a UEFI configuration. The only other usage for it is Bit Locker from what I read, but I've never had any issues encrypting installs without it. 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