Of course it was the "ExtendOEMpartition=1" in sysprep.inf - I got all my config packages mixed up. Also the fact that the 320LT disk actually worked, got me confused.
Thanks for all your help in this forum, Warren - and please forget about this thread 😉
@Warren - This is ArmitageID here from the old Dell TechCenter side. My first post in the new system so not sure how my name will come across. In any case, I am having this SAME issue with many of our international machines. I received the 320GB kit and everything is working fine. These new machines in Oman have the 250GB version and are running into the BSOD. The error message is:
STOP: 0x000000ED (0x8A3D2C08, 0XC000014F, 0X00000000, 0X00000000)
I haven't looked for the ExtendOEMpartition=1 int he sysprep.inf file yet, I'll take a look.
My biggest question is why it works fine with the 320GB unit that was sent???
*Update 1* I checked my sysprep.inf file and it is there "ExtendOEMpartition=1". The Unattend.txt file has it in there as well, but it is commented out. Any advice?
The general guidance is to not use "ExtendOEMPartition=1" so I would suggest removing that from your Sysprep.inf to see if that addresses it. I don't have any ideas as to why the 320GB worked and the 250GB didn't.
@Warren If I change that variable then will it no longer be able to apply the OS to the entire disk? I format and partition the drive during imaging so I assume the entire disk would be available for use. I assume the solution is to set ExtendOEMPartition=0? I guess my question is does this variable even come into play when applying a WIM with MDT or is this more for people who use something like ghost?
I guess the root question I'm trying to ask here is if the image was built on a machine with a 40GB hard drive, setting ExtendOEMPartition=0 won't result in 280GB of the drive being on partitioned. I don't want to have to manually expand the drive latter down the road. Just looking for some clarification.
If you are formatting and partitioning the drive then the ExtendOEMPartition option isn't needed at all. I've never used it and from what I hear from other customers, it's just a roadblock for AFHDD's. Give it a try without it and let me know if you see anything detrimental to that configuration.