I originally created a 2022 Worstation Client (20348.1) with desktop for my laptop following the instructions here by switching the SKU. Does this no longer apply for installing drivers or unsupported sw in server using the above scripts?
I haven't tested it on a real machine yet, but I believe the software should work fine. In this script, we don't change the SKU; instead, we modify records to support Workstation. We'll have to test and verify.
Hi Thanks for this work, I really appreciate it. Now I need a hint how to merge those OEM and anattend tasks into the install.wim-file, because I usually patch the Install-files of an Iso via wintoHdd onto a VHDX in Windows. This method seems to use just whats in the install.wim. Any advice ? Thanks in advance
For now mainly Your OEM and the tweaks. Btw, I just made a run with server 2025, and patched the install.wim to a VHDX, booted, and stuck at a admin login-screen which wanted a password I don't know... The DVD-folder I got had no Setup.exe in it, how is this ment to be installed then ? I guess, I missed something, didn't I ?
Since the image is reduced, setup.exe is located in the sources folder. The script also applies a tweak to make this work. I personally use an autounattend.xml file for my installations. Try using the attached autounattend.xml. Place it inside the DVD folder and create your ISO.
I believe you're talking about autounattend.xml. It creates the "User" administrator. Use this one, where this was removed, and test it out. Edit. Tested, it only creates the Administrator user. It's not the best option. There's another option, where the user must edit and replace the username with their nickname. This one works well.
Yes, you read me correctly, that's exactly what I meant - thank you! Personally, I use autounattend.xml in which I specify only the PC name, and set the user name during the OS installation. I would like autounattend.xml to allow to enter both user name and PC name during OS installation.
Im having an issue where the insall of OS with modern calc works flawlessly in a VM, for some reason on a real PC the post installation of modern calc is not working? What would cause this condition?
Do you have the autounattend.xml file where we can enter the username during the operating system installation? This is for Windows 10. If so, please share.
Since I don't use Modern Calculator, I can't say right away, but could you add an image with the error that is caused?
No error just modern calc does not appear to be in installed programs? If I search for calc.exe nothing is found?