PENDING Task Sequence Issues - Installing Windows 10

[levi.shaul]

Hello everyone! I am new to this forum, but I've used the tutorials here before and I wasn't able to find this issue elsewhere...

I have a few TS created and one specifically is used to image / re-image computers. I am using a custom WIM file that I created through Hyper-V and DISM for this TS. The issue doesn't seem to happen too often, but it does every 3-5 computers we image. What's happening is that the WIM is definitely being used for the install as my custom settings are still there, but after the process is completed the computer has Windows 10 Pro on it instead of Enterprise.

I'm fairly new to SCCM and I'm sure it's something very simple... but any help is appreciated!

 

[Prajwal Desai]

Whatever you configure to install, the same gets installed. When you say a custom wim file, do you mean it is a a WIM file that you obtained after capturing a OS ?.

 

[levi.shaul]

Whatever you configure to install, the same gets installed. When you say a custom wim file, do you mean it is a a WIM file that you obtained after capturing a OS ?.

Yes, I created the WIM file after configuring an 1803 VM.

I following the steps in the following link to do this:
https://finalthought.org/2018/01/11...ws-10-version-1709-media-iso-wim-flash-drive/

I know it doesn't make sense and it probably shouldn't be happening, but when we run the TS over PXE it will install the Enterprise edition most times, and the Pro edition other times. I know they are technically the same build and can easily be changed with the product key, but we'd prefer not to share that key with everyone who's imaging.