massgrave.dev/docs/oem-folder.md

97 lines
5.4 KiB
Markdown
Raw Normal View History

2024-04-12 05:05:28 +02:00
# $OEM$ Folders
2022-07-25 20:03:20 +02:00
2024-04-13 23:09:49 +02:00
To create a pre-activated Windows installation .iso, do the following:
2023-10-24 15:46:54 +02:00
- Extract the `$OEM$` folder to the desktop using the MAS script.
2022-07-25 20:03:20 +02:00
- Copy the `$OEM$` folder to the `sources` folder in the Windows installation media (.iso or USB).
- The directory will appear like this: `\sources\$OEM$` in your altered .iso or on your bootable USB drive.
2023-10-24 15:46:54 +02:00
- Now use this .iso or bootable USB drive to install Windows, it will either already be activated (KMS38) as soon as it boots or will self-activate (HWID or Online KMS) at the first internet contact.
2024-04-12 05:05:28 +02:00
- You can check [here](intro.md) for activation method details and select the activation method as per your requirement.
2023-01-11 12:19:43 +01:00
2024-04-13 23:09:49 +02:00
:::warning
2024-06-09 06:37:49 +02:00
- On Windows 8 and later, [**running setupcomplete.cmd is disabled**](https://learn.microsoft.com/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup?view=windows-11#windows-setup-scripts) if the default installed key for the edition is from the OEM channel, except for Enterprise editions and Windows Server operating systems.
- However, in Windows 10, IoT Enterprise editions were not included in the Enterprise category list during the installation process. As a result, Enterprise with an OEM key can handle setupcomplete.cmd, but IoT Enterprise (LTSC) cannot. This was fixed in later Windows 11 versions.
- In Windows 10 IoT Enterprise (LTSC), you can resolve this issue by using the Non-IoT Windows 10 Enterprise LTSC ISO. In this case, the HWID method in preactivation will install the IoT LTSC key to change the edition and enable HWID activation.
- In Windows 11 IoT Enterprise (LTSC), it works fine as expected by default.
2024-04-13 23:09:49 +02:00
:::
2023-10-24 00:12:58 +02:00
------------------------------------------------------------------------
## Edit ISO File
2023-10-24 15:46:54 +02:00
- As stated above, you can copy the `$OEM$` folder to your bootable USB so you don't have to edit the ISO file. However, if you need to, then follow the steps below.
2024-02-12 09:21:03 +01:00
- Download [AnyBurn Free Portable](https://www.anyburn.com/anyburn.zip) and extract this zip file
- Run the file named `AnyBurn(64-bit)\AnyBurn.exe`
- Select the option named `Edit image file`
- Follow the on-screen instructions and add the `$OEM$` folder to the `sources` folder so that the directory will appear like this: `\sources\$OEM$`
- Save the ISO, that's it.
2023-10-24 00:12:58 +02:00
------------------------------------------------------------------------
2022-11-07 21:30:36 +01:00
## KMS38 - Server Cor/Acor
2022-07-25 20:03:20 +02:00
2023-10-24 15:46:54 +02:00
- Windows Server Cor/Acor (No GUI) editions don't have the `clipup.exe` file.
2024-04-12 05:05:28 +02:00
- To KMS38 activate it, you need to download the missing `ClipUp.exe` file from [this link](/files/ClipUp.zip).
`File: ClipUp.exe`
`SHA-256: 0d6e9f6bbd0321eda149658d96040cb4f79e0bd93ba60061f25b28fecbf4d4ef`
2023-10-24 15:46:54 +02:00
This file has digital signatures that can be verified. You can also get this file from the official [Windows Server 2016 x64 RTM ISO](https://download.microsoft.com/download/1/6/F/16FA20E6-4662-482A-920B-1A45CF5AAE3C/14393.0.160715-1616.RS1_RELEASE_SERVER_EVAL_X64FRE_EN-US.ISO).
2023-03-16 19:09:16 +01:00
- Put the `ClipUp.exe` beside the KMS38 Activation script. That would be either `MAS_AIO.cmd` or `KMS38_Activation.cmd`
2024-01-24 02:12:44 +01:00
- The activation script will check `ClipUp.exe` in the current folder (from where script is running) and will use it accordingly.
2022-07-25 20:03:20 +02:00
------------------------------------------------------------------------
## HWID
- When using HWID activation, no files are stored on the system, and Windows 10-11 will be activated when connected to the internet for the first time.
------------------------------------------------------------------------
2023-09-25 15:45:25 +02:00
## Ohook
- If Office is preinstalled then Ohook method will activate the Office immediately without Internet. This activation uses custom sppc.dll file for the activation.
------------------------------------------------------------------------
2022-07-25 20:03:20 +02:00
## KMS38
- When using KMS38 activation, no files are stored on the system, and Windows 10-11-Server becomes activated immediately without Internet.
------------------------------------------------------------------------
## Online KMS
2023-09-25 15:45:25 +02:00
- When using Online KMS activation, Windows-Server and Office (Preinstalled) both will be activated when connected to the internet for the first time. This option uses a renewal task for lifetime activation.
------------------------------------------------------------------------
## HWID + Ohook
- In this method, Windows 10-11 will be activated with HWID, and **Office** (Preinstalled) will be activated using Ohook.
2022-07-25 20:03:20 +02:00
------------------------------------------------------------------------
## HWID + Online KMS
2023-09-25 15:45:25 +02:00
- In this method, Windows 10-11 will be activated with HWID, and **Office** (Preinstalled) will be activated using Online KMS.
------------------------------------------------------------------------
## KMS38 + Ohook
- In this method, Windows 10-11-Server will be activated with KMS38, and **Office** (Preinstalled) will be activated using Ohook.
2022-07-25 20:03:20 +02:00
------------------------------------------------------------------------
## KMS38 + Online KMS
2023-09-25 15:45:25 +02:00
- In this method, Windows 10-11-Server will be activated with KMS38, and **Office** (Preinstalled) will be activated using Online KMS.
------------------------------------------------------------------------
## Online KMS + Ohook
- In this method, Windows-Server will be activated with Online KMS, and **Office** (Preinstalled) will be activated using Ohook.
------------------------------------------------------------------------