Then don't address me by quoting my post and using the ? Normally that means the one who is quoted is the one the question under the quote is asked.
That will be activated through KMS which is not ideal as SLP 2.7 BIOS already exists. The only thing which is lacking here is the DELL SLP key.
The key does not necessarily need to be the Dell one, you can use any valid SLP key for the SKU in question. Only the SLP 2.x SLIC and the OS certificate have to match.
N Nope... tsforge are permanent activation like retail , kms4k are kms token for 4000 years before need renewall and kms38 are activation up to 2038
Well as long as we will probably be all dead in 4000 years, that might be ok, except the fact that last time I used a KMS activation on some client/server OS, Microsoft always published some updates that killed the activation and/or KMS local server. Is this still applicable with "tsforge" ?
Nevermind, I figured out what was my problem. BIOS/EFI wasn't taken into action from my VM ".vmx" file because I forgot to use the correct parameter name. Anyway, ESXi never shown any error message, even in the logs at VM startup time (which was starting fine). So far so good, everything got activated as long as this time the ACPI SLIC table was shown. >>> See this post for resolution : https://forums.mydigitallife.net/th...-bios-efi-slic-mod.64693/page-21#post-1883734
What are the updates to the base isos and skus of Server 2025 and what are the main ones that can be created with create editions, because applying updates to 4 indices is time-consuming. Anyone who can help would be grateful.
The updates are the same as client 26100 Service one SKU and you can offline set-edition the other SKUs