hello, thank you all for sharing your excellent work and support I currently use KMS_VL_ALL (with automatic renewal) on windows Enterprise Edition/Office 365 (without any issue) I intend to switch to MAS script to get the the benefit of the future ESU Should I uninstall KMS_VL_ALL before doing this ? Thanks again Add-on: In a virtual machine, I have kept KMS_VL_ALL and install TSforge ESU ONLY seems to work perfectly Is there any advantage to use also TSforge for Windows/Office activation instead of KMS_VL_ALL ?
IoT Enterprise has no advantages over Enterprise, basically. Only IoT Enterprise LTSC is valuable because of the 10 year support. In a nutshell: OEM:DM is the successor to OEM:SLP, but uses unique keys which are usually embedded in the system's UEFI firmware. TSForge ZeroCID/StaticCID uses that type of key for main licenses, if available, to resemble a normal OEM system as close as possible (no requirement for the embedded key). OEM:SLP is older, used for Vista, Windows 7, and now only Servers. Uses generic keys, certificates and special information in the firmware. Windows Loader exploits that activation channel by emulating the BIOS informnation. OEM:NSLP is usually the key type on the COA labels coming attached to OEM machines. If OEM:DM is not available, ZCID/SCID uses that type.
Actually, Win 11 (24H2) IoT Enterprise does not check the windows 11 system requirements, Enterprise does. Same for the LTSC versions, IoT Enterprise 2024 LTSC doesn't check the windows 11 system requirements, Enterprise 2024 LTSC does.. I never did test the 21H2 and 22/23H2 IoT Enterprise SKUs.
Thanks for the fast response, my friend! Couple questions: 1) How to we clean install an GAC IoT Enterprise? Never seen ISOs for that SKU... 2) is it barebones like the LTSC version? I mean, no MS Store pre-installed, no new apps (like the new Notepad) like the LTSC? 3) How does it compare to regular Enterprise and IoT Enterprise LTSC feature-wise? Asking because I'm really curious, never seen this SKU in the wild before! Tks
1) Creating an ISO from UUPDump with "Create virtual Editions" set will include IoTEnterprise in the final ISO. 2) AFAIK, it's just a full Enterprise with different license. I've never used it personally, though. 3) From what I've read, it's feature-equivalent to Enterprise. The barebones nature of the LTSC versions come from LTSC, not from IoT. IoT LTSC just so happens to get 10 years support, thus the hype. Non-LTSC IoTEnterprise is wasted time and effort.
For TSforge activation, these two services are a must. sppsvc, Winmgmt. All the tasks in this path shouldn't be touched. \Microsoft\Windows\SoftwareProtectionPlatform\
Hi there! 1) I see... never used UUPDump, tough... do we have a howto here in the forums on how to use it? 2) OK, got it. But someone mentioned it ignores the hardware requirements when installing, just like the IoT LTSC... Is that right? 3) Yeah, I know the LTSC versions, have used some since the Windows 10 day. It makes no sense to me, the change in support lifecycle that MS did for the regular LTSC (reduced to 5 years). IoT LTSC is the way to go, indeed!