I was doing some homework on Win11PE while reading quite a bit of Server 2022 as well, basically a forum thread should have appeared back in October 2021
paste EI.cfg and PID.txt in sources folder from iso ( use poweriso or ultraiso to modify iso ! )
the system is automatically activated without networks required
Stuff like that could be found by anyone easily, while the instructions were already posted on one of those official forums hosted by Microsoft since 2020
On standard Windows 10 install media, look for the file \sources\product.ini. It contains many generic Product Keys used by the various Windows 10 Editions that are available. Most installs will show one of these same generic Product Keys if you use a utility, such as Nirsoft's ProduKey, to reveal the current Product Key for your Windows 10.
Key Management Services (KMS) client activation and product keys
1. Extract the packages Microsoft-Windows-Server-DesktopUX-Package and Microsoft-Windows-Server-DesktopUX-WOW64-Package from SKUs like ServerDatacenter or ServerStandard that includes GUI.
I spent literally months to figure it out, you really can spend few minutes of your time reading what I already wrote
1 Copy the sku certs from pro
2 do slmgr /rilc
3 do slmgr /ipk <pro serial>
reboot
do whatever you need to install drivers and / or unsupported sw in server
4 slmgr /ipk <server serial>
reboot (you are back on server )
optional if you want to stay on pro and activate it, replace the branding folder as well
that's all
Edit: 11/9/2022
I baptized this method as "SKUwitch" to avoid confusions with other "quick switches" methods
Edit: 20/08/2023
The above method *as is* doesn't fully work anymore on recent 25xxx builds (thanks to the user @Moony who discovered and reported the problem).
Not sure which is the first affected build, but I think any 252xx and following builds are affected.
As usual, once you know the solution the fix requires just 2 seconds, finding that solution required a couple of days.
In short, in addition to the instructions above you need to delete all *SIX* certs under the issuance folder, and replace them with the *FOUR* from an older builds (I used the ones from 25192, but I think other older releases should do the job as well).
Obviously do that before the slmgr /rilc step.
The method works also on the new infamous 259** builds (current at time of writing is 25931, tested on 25921)
When Windows Update issue occured, it means that there is update for C:\Windows\Branding. Revert Branding to Server's and it'll be OK to update. After update, revert to Client's Branding.
PS:
Server's Branding has to be re-backuped for each update. (Branding is hardly ever updated, just in case.)
Certs are located in "C:\Windows\System32\spp\tokens\skus"
Find a W10 client/pro ISO, open .wim with 7zip, or take files from a live installation.
Go to "C:\Windows\System32\spp\tokens\skus" and copy/paste "Professional" folder to same location on Server.
Then slmgr /rilc
Simply put, the whole point here should be getting that Azure Stack HCI installed and activated first. Once that's already taken care of, we'll proceed to extract two desktop packages from the "Server with Desktop Experience" flavor of Windows Server 2022 while adding both of them to Azure Stack HCI accordingly. Finally we're taking whatever certificates we need from any client versions such as Windows 10 or 11, and then copy to a specific folder as mentioned in the detailed instructions linked above.
It's kinda fun to notice that even one of those Intel network adapter drivers could be installed without having to mess around
You are absolutely right acer-5100. I was using Win11 ProWS instead of Win11 Pro. Made all the difference in the world. Got Nero, Kasperssky Internet security installed and running. Also installed the actual Intel i211 network adapter driver.
Personally I'm not interested in any client / server (i.e. conventional) versions of Windows anymore since the size would be HUGE when compared to what we're able to accomplish with Win11PE these days, please don't ask me for any guidance and feel free to post your questions on those forums instead.
If we're interested in slimming the whole thing down a little bit, these tools might be designed for those client versions of Windows in the first place but it wouldn't hurt to give them a try on Azure Stack HCI
CBSEnum is a tool to view and manage Windows Component-Based Servicing packages.
Component-Based Servicing is a technology since Windows Vista which most resembles Linux-style package managers. It builds upon WinSxS (Side by side assemblies) to allow installation, deinstallation and updating of numerous Windows components independently.
It presents a moderately componentized view into Windows and allows uninstalling parts of system which outside of Windows Embedded were previously seen as monolithic.
In Windows, this technology is hidden from general public. There's a command-line tool dism.exe to manage CBS packages, but most packages are marked as hidden even from DISM.
MODWIN: A Tool for Inspecting, Modifying, and Building "Lite" ISOs
Windows Server 2025, Build 26052 Datacenter Experience installed and running JPlay without issues so far. Only thing is that JPlay Mini now appears as a a command prompt window (on the taskbar too).
Allow me a few weeks to fine tune the new OS (removing components and disabling unnecessary services just as I did with Server 2022) and listen through more albums. The sonic traits appear to be similar to those of the 2022 DC (the 2022 DataCenter has been my OS of choice for JPlay after extensive testing); A good sign.
I installed the latest build 26063 and after a few days of OS tweaking/system tuning (change of speaker placement, etc.) have come to the conclusion that, with JPlay, the current build of Windows Server 2025 doesn't sound as good as Server 2022. The main difference lies in the tonal balance and harmonic content, where the rich and natural midrange (could be 100Hz to at least 3kHz) of the Server 2022 is missing/repressed on the 2025. This makes for a thin and inorganic sound that reminds me of the various editions of Windows 11 I tried quite some time ago when spending months comparing various versions of Windows 10, Windows 11, Server 2002, 2016, 2019 and 2022, as well as Windows PE/Foobar and some proprietary audio-specific Linux OSs/players. Note that the result might have to do with my audio PC setup, which is high speed, super low latency (Intel 12th Gen/DDR5, both overclocked to their limits), with huge power supplies for their excellent transient performance (Cosair AX1600 and several Cosel 1500W external power supplies for the disks and USB accessories)--this is in many ways contrary to the low power consumption, low speed CPU/DDR4, relatively low power linear PSU school that most audiophile PC setups seen on online forums belong to.
I recall reading somewhere that Server 2022 was actually based more on Windows 10 than 11 and that the position of the Windows start icon on the taskbar is the tell-tale sign. The start icon in Server 2025 is to the center instead of on the left end, same as in Windows 11.
...What build number of server 2022 that you prefer?
Hi Romaniac--I will find the build number tonight and report back. My current installation uses the iso downloaded from the official Windows Evaluation site after the launch, but I don't recall hearing differences from the couple builds I had tried previously.
I briefly tried a stripped PE from Server 2022 running Foobar, and it didn't have any advantage over the full Datacenter version with JPlay. However, the PE I made was not the leanest possible. Also, the DDC I use appears to play a key role in the overall performance and to have it running in Kernel Streaming mode is paramount. Unfortunately getting the DDC's proprietary driver to run in KS mode on PE was beyond my capabilities at that time. I might still give Server 2022 PE/Foobar another try, hopefully even running JPlay (but it means adding internet connection, etc.) if at all possible, but am in no hurry since I really enjoy what I get from Server 2022DC/JPlay currently.
Incidentally, I purchased an AudiophileOptimizer license when I did the OS/player shootout but soon realized that Server 2022 was my favourite, so never got around to using it. Now that the new AO 4.0 is going to cover Server 2022, I look forward to finally trying it on my system.
Just checked and it's build 20348.587. Server 2022 DC is LTSC so the version remains 21H2.
For system disk I tried several types of SSD including RAM disk, and Optane 900P really stood out. Both my control PC and audio PC have Optane 900P as system disk.
If you're running core mode don't forget to install FOD for Audio PC. You won't be able to run KS if not. AO4 beta installs it. Sound is amazing! Much, much better than WS2019!
Thuan and dequad like this
Furman Elite (power conditioner), JPlay Femto iOS, JPlay Femto, AO4, TC 3.1b: 2 x fanless mini PC (Intel I5-Skylake), Control PC - WS 2022 DataCenter core -16GB RAM, Audio PC - WS 2022 DataCenter core 8GB RAM, JCAT USB Femto Card, 2 x JCAT Femto Net Cards, 1 x 200VA Ultra Low Noise LPS, 4 x 100VA Ultra Low Noise LPS, JCAT USB Isolator, Singxer SU6, Gustard A26, Audia Flight Pre Mk III (dual mono class A preamplifier), Audia Flight FL50 Mk IV(dual mono class A amplifier), Focal Electra 1028BE,1008BE, Focal Electra sub;
Just clarifying things a little, AO4Beta will install KS in 2022 core without FOD.
The sound is stunning with just the AudioPC on 2022 and ControlPC still on 2019. It's like having a new very high end dac, I'm still getting used to it. No "upgrade fade" happening so far.
I now have 2022 running on the Control PC. This gave an additional improvement especially in the vocal range. This is a very special sound. I will not be going back to 2019.
I now have 2022 running on the Control PC. This gave an additional improvement especially in the vocal range. This is a very special sound. I will not be going back to 2019.
Some time ago I changed all the hardware with supermicro cards, Xeon RAMM processors etc and installed Win 11atomic.Compared to my previous setup, a notable leap and I felt satisfied, at least until I put my turntable back into operation, not even very hiend.I don't have the width of the digital scene but the voices are much more relaxed and natural: it could probably be win11's fault
I now have 2022 running on the Control PC. This gave an additional improvement especially in the vocal range. This is a very special sound. I will not be going back to 2019.
