massgrave/activation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix NSLP description

Browse Source 
Made an oopsie - NSLP is definitely not "an SLP equivalent" as the activation is not authorized by the OEM.
This commit is contained in:
awuctl 2022-01-21 09:19:31 +01:00 committed by GitHub
parent 9f355ce1c4
commit e5ab74c2d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -69,10 +69,9 @@ There are multiple types of keys that will accompany OEM licenses. Those are:
The differences between them are pretty extreme but ultimately do not matter The differences between them are pretty extreme but ultimately do not matter
that much. In short, **SLP** keys do not require Microsoft's activation servers that much. In short, **SLP** keys do not require Microsoft's activation servers
to activate - the OEM marks a machine as activated during manufacturing, to activate - the OEM marks a machine as activated during manufacturing,
**DM** are the "BIOS keys" you might have seen/heard about and **NSLP**s are the **DM** are the "BIOS keys" you might have seen/heard about and **NSLP**s are for
**SLP** equivalent for when the OEM doesn't want to bother with activation when the OEM doesn't want to bother with activation during manufacturing. In
during manufacturing. In terms more people might understand, NSLP is analogous terms more people might understand, NSLP is analogous to COA.
to COA.
### Volume Licensing ### Volume Licensing
Microsoft's bigger customers that "need" more licenses for more computer can opt Microsoft's bigger customers that "need" more licenses for more computer can opt