Quantcast
Channel: Setup Deployment forum
Viewing all articles
Browse latest Browse all 2818

Windows Server 2019 image customization via dism results in a corrupted image with missing Edition Flag after adding product MAK keys

$
0
0

Hi all,

I am using the current latest installation media and the latest available ADK Tools: 

SW_DVD9_Win_Server_STD_CORE_2019_64Bit_English_DC_STD_MLF_X21-96581.ISO

The install.wim is then copied onto the local devel system and modified as shown below:

dism /export-image /sourceimagefile:install.wim /sourceindex:2 /destinationimagefile:install.standard.wim

dism /mount-wim /wimfile:install.standard.wim /index:1 /mountdir:mnt

dism /image:mnt /set-productkey:<volume license MAK B/C Key>

dism /unmount-wim /mountdir:win\mnt /commit

If I am going to check the edition state from the image after the export and in front of applying the product key everything seems to be ok and the dism /get-currentedition command returns e.g. SERVERSTANDARD as expected. After the key is applied the command just returns an empty string. A editionless image can't be applied by winpe and thus any attempt of installing such an image fails.

Exactly the same procedure works fine for windows server 2016. Is there anyone who successfully customized a windows server 2019 image or has some further knowledge about possible differences which need to be considered while building windows server 2019 images?

As far as I know this kind of behaviour is either known for a corrupt installation image or a wrong product key. Unfortunately this doesn't seem to be the case here: As long as I don't add the product key, image customization works fine and results in installable images. If I am going to apply the exact same product key after the installation of such an image also the activation works fine. So I guess there is everything OK regarding this which makes me running out of ideas regarding possible reasons for this behaviour...

Thank you for your time!


Viewing all articles
Browse latest Browse all 2818

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>