So I had to do 2 exports and afterwards merge them again with ImageX (from WADK).ĭoable, but yet again 2 extra steps, 2 different tools. C:\Program Files\NTLite\Updates is empty. I would expect to see the ones from 2023-04. ![]() I load the WIM, I go to Updates, Add, Latest Online Updates - shows Wind圆4. But you can only export 1 index, and I want both the Standard and Datacenter editions in my ISO. Mounting just the install.wim from a Server 2016 ISO. Less efficient imo, but we can't afford breaking our servers either.ītw, Atenza, I did explore the export route earlier this week. First upgrade with a normal image, and right after push all patches. We're going to try and automate our in-place upgrades with an SCCM task sequence. Weird, cause I used the official ISO as a base and just added all patches released since. A colleague spotted that the first (big) version of my custom ISO has a major issue for in-place upgrades of servers having IIS enabled.Īpparently the IIS role is gone after the upgrade, and impossible to reinstall the role.ĭoing the same upgrade with the official MS ISO don't create this issue, so it's something caused by my ISO. ![]() NTLite might be an option, but I'm not sure yet if it'll address both issues.įor now this little project is put on hold. Then I'm sure nothing else has been slipped in I think I've seen people sharing such custom ISO's, but for security reasons I want to create my own. Physical servers with UEFI refuse to boot with it. I used ImgBurn to recreate a bootable ISO, but apparently the ISO is only usable for legacy BIOS machines.Use the hierarchy on the left to navigate to the following policy group: Local Computer Policy > User Configuration > Administrative Templates > Star Menu and Taskbar > Notifications. 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. The Local Group Policy Editor should be open now. And running dism with a /StartComponentCleanup parameter afterwards fails because of pending actions.īecause the image is bigger we need more free disk space on the servers where we want to do an in-place upgrade. In this article Registry settings See also Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2 Registry settings Table 3 describes the registry settings that Volume Activation supports. The install.wim grows quite a lot, from the original 4.4GB to 7.2GB after adding all patches. ![]() I've tried using dism to update the install.wim, but I have 2 issues with that: It would speed up in-place upgrades quite a bit. How can I best create my own custom Windows Server 2012 R2 and Windows Server 2016 ISO's?Īll I'd need are the official Microsoft ISO's (which I have) with all updates to date slipstreamed into them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |