it does not support upgrade to a newer WADK… Later I realised that this was because it expects WADK not to be already installed, i.e. My existing MDT bundle creator was on the BigFix server itself, but it did not show up as Relevant. If this step fails, you must import an MDT Bundle with a later version of PE10Ĭompleted parameter “ImageReleaseID” = " I created a VM for Win10 (1809) and customised it to my liking, then tried to capture it an soon found out that PE10 was outdated:Ĭompleted // Verify the release ID of the image being captured is supported by PE10 version. In this environment, everything worked perfectly when only Win7 was involved. The BSODs appear after the first reboot, after loading boot.wim and running sysprep, when capturing images, and after boot.wim has been loaded and booted, when deploying an image. After running around in circles, I started from “Square One” again and decided to document what makes me so confused. During the last 4-5 days I’ve become more and more confused to as what is happening. Now, the need to create Win10 images has come and that is when my BSOD hell started. This has worked flawlessly so far, working with Win7 images. During my daily work I’m dependant on using BigFix on VMware Workstation 12 for creating, capturing and (test-)deploying OS-images before exporting them to my customer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |