You need three components: 1. SLIC in firmware. 2. Matching OEM:SLP certificate installed in Windows. 3. OEM:SLP key. Note that generated, not official keys can get blacklisted.
Indeed! This was just for the PoC and test latest SLIC 2.5 elsewhere than Server 2019 Std. No real need for this...
There seems to be an OEM:SLP channel, but I'm not aware of any working OEM:SLP key for ServerRDSH in the wild.
Thanks for the idea, but I have 2 questions: 1) How will RDP work? (Will it still be possible to use 3 sessions at the same time without a 120 day limit?) 2) Will updates from Microsoft need to be installed in the ServerRdsh edition or will it be possible in Azure Stack HCI?
Sorry I don't use them, but the relevant policy should be the following, and is the same in both SKUs TerminalServices-RemoteConnectionManager-AllowMultipleSessions = 1 WU base itself on the installed packages, not the activation status. Turn a Pro in to a Server Standard and it will get the Pro updates while having the Server behavior At least it's how it always worked, things may change in the future. Whatever... being easy and fast going back and forth, test it, if you don't like it just go back to rdsh.
It's an online procedure https://forums.mydigitallife.net/th...st-install-settings.84501/page-7#post-1714633 Just follow the above replacing the mentioned SKUs with ones of your interest
If your certs are coming from 20348 and you are on older build, there's a small variation, you need to move out the whole tokens dir, then copy the tokens dir from 20348, then (if you want to keep the possibility of going back to the original SKU) copy again the original SKUs (Pro and all others) folder where they were. P.S. there is little point in switching to Server Standard or Server ACor, since Azure stack HCI was made available. Practically the same thing minus the activation (unless I missed something).