![]() * I used ImgBurn to recreate a bootable ISO, but apparently the ISO is only usable for legacy BIOS machines. Not a blocking issue, but there's not always enough free space and we need to cleanup/extend the system drive before being able to continue. ![]() Because the image is bigger we need more free disk space on the servers where we want to do an in-place upgrade. And running dism with a /StartComponentCleanup parameter seems to fail because of pending actions. * The install.wim file grows a lot, from the original 4.4GB to 7.2GB after adding all patches. ![]() To speed up in-place upgrades I'm adding all patches since the ISO's release, simply with dism because it's free and not that complicated to do.ΔΆ issues though, why I might consider asking my boss for an NTLite license: ![]() A few months ago I started creating my own custom Windows Server 2012 R2 & 2016 ISO's. ![]()
0 Comments
Leave a Reply. |