/* 017 */{{0x6d5f5270,0x31ac,0x433e,{0xb9,0x0a,0x39,0x89,0x29,0x23,0xc6,0x57,}}/*6d5f5270-31ac-433e-b90a-39892923c657*/,"Windows Server Preview",EPID_WINDOWS,6,5},
/* 017 */{{0x6d5f5270,0x31ac,0x433e,{0xb9,0x0a,0x39,0x89,0x29,0x23,0xc6,0x57,}}/*6d5f5270-31ac-433e-b90a-39892923c657*/,"Windows Server Preview",EPID_WINDOWS,6,5},
/* 021 */{{0x6e9fc069,0x257d,0x4bc4,{0xb4,0xa7,0x75,0x05,0x14,0xd3,0x27,0x43,}}/*6e9fc069-257d-4bc4-b4a7-750514d32743*/,"Windows Server 2016",EPID_WINDOWS,6,5},
/* 021 */{{0x6e9fc069,0x257d,0x4bc4,{0xb4,0xa7,0x75,0x05,0x14,0xd3,0x27,0x43,}}/*6e9fc069-257d-4bc4-b4a7-750514d32743*/,"Windows Server 2016",EPID_WINDOWS,6,5},
{{0x9caabccb,0x61b1,0x4b4b,{0x8b,0xec,0xd1,0x0a,0x3c,0x3a,0xc2,0xce,}}/*9caabccb-61b1-4b4b-8bec-d10a3c3ac2ce*/,"Office Mondo 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x9caabccb,0x61b1,0x4b4b,{0x8b,0xec,0xd1,0x0a,0x3c,0x3a,0xc2,0xce,}}/*9caabccb-61b1-4b4b-8bec-d10a3c3ac2ce*/,"Office Mondo 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xe914ea6e,0xa5fa,0x4439,{0xa3,0x94,0xa9,0xbb,0x32,0x93,0xca,0x09,}}/*e914ea6e-a5fa-4439-a394-a9bb3293ca09*/,"Office Mondo R 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xe914ea6e,0xa5fa,0x4439,{0xa3,0x94,0xa9,0xbb,0x32,0x93,0xca,0x09,}}/*e914ea6e-a5fa-4439-a394-a9bb3293ca09*/,"Office Mondo R 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xec9d9265,0x9d1e,0x4ed0,{0x83,0x8a,0xcd,0xc2,0x0f,0x25,0x51,0xa1,}}/*ec9d9265-9d1e-4ed0-838a-cdc20f2551a1*/,"Office Outlook 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xec9d9265,0x9d1e,0x4ed0,{0x83,0x8a,0xcd,0xc2,0x0f,0x25,0x51,0xa1,}}/*ec9d9265-9d1e-4ed0-838a-cdc20f2551a1*/,"Office Outlook 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xd450596f,0x894d,0x49e0,{0x96,0x6a,0xfd,0x39,0xed,0x4c,0x4c,0x64,}}/*d450596f-894d-49e0-966a-fd39ed4c4c64*/,"Office Professional Plus 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xd450596f,0x894d,0x49e0,{0x96,0x6a,0xfd,0x39,0xed,0x4c,0x4c,0x64,}}/*d450596f-894d-49e0-966a-fd39ed4c4c64*/,"Office Professional Plus 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x4f414197,0x0fc2,0x4c01,{0xb6,0x8a,0x86,0xcb,0xb9,0xac,0x25,0x4c,}}/*4f414197-0fc2-4c01-b68a-86cbb9ac254c*/,"Office Project Pro 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x4f414197,0x0fc2,0x4c01,{0xb6,0x8a,0x86,0xcb,0xb9,0xac,0x25,0x4c,}}/*4f414197-0fc2-4c01-b68a-86cbb9ac254c*/,"Office Project Pro 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x829b8110,0x0e6f,0x4349,{0xbc,0xa4,0x42,0x80,0x35,0x77,0x78,0x8d,}}/*829b8110-0e6f-4349-bca4-42803577788d*/,"Office Project Pro 2016 XC2R",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x829b8110,0x0e6f,0x4349,{0xbc,0xa4,0x42,0x80,0x35,0x77,0x78,0x8d,}}/*829b8110-0e6f-4349-bca4-42803577788d*/,"Office Project Pro 2016 XC2R",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xda7ddabc,0x3fbe,0x4447,{0x9e,0x01,0x6a,0xb7,0x44,0x0b,0x4c,0xd4,}}/*da7ddabc-3fbe-4447-9e01-6ab7440b4cd4*/,"Office Project Standard 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xda7ddabc,0x3fbe,0x4447,{0x9e,0x01,0x6a,0xb7,0x44,0x0b,0x4c,0xd4,}}/*da7ddabc-3fbe-4447-9e01-6ab7440b4cd4*/,"Office Project Standard 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xcbbaca45,0x556a,0x4416,{0xad,0x03,0xbd,0xa5,0x98,0xea,0xa7,0xc8,}}/*cbbaca45-556a-4416-ad03-bda598eaa7c8*/,"Office Project Standard 2016 XC2R",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xcbbaca45,0x556a,0x4416,{0xad,0x03,0xbd,0xa5,0x98,0xea,0xa7,0xc8,}}/*cbbaca45-556a-4416-ad03-bda598eaa7c8*/,"Office Project Standard 2016 XC2R",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x83e04ee1,0xfa8d,0x436d,{0x89,0x94,0xd3,0x1a,0x86,0x2c,0xab,0x77,}}/*83e04ee1-fa8d-436d-8994-d31a862cab77*/,"Office Skype for Business 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x83e04ee1,0xfa8d,0x436d,{0x89,0x94,0xd3,0x1a,0x86,0x2c,0xab,0x77,}}/*83e04ee1-fa8d-436d-8994-d31a862cab77*/,"Office Skype for Business 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xdedfa23d,0x6ed1,0x45a6,{0x85,0xdc,0x63,0xca,0xe0,0x54,0x6d,0xe6,}}/*dedfa23d-6ed1-45a6-85dc-63cae0546de6*/,"Office Standard 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xdedfa23d,0x6ed1,0x45a6,{0x85,0xdc,0x63,0xca,0xe0,0x54,0x6d,0xe6,}}/*dedfa23d-6ed1-45a6-85dc-63cae0546de6*/,"Office Standard 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x6bf301c1,0xb94a,0x43e9,{0xba,0x31,0xd4,0x94,0x59,0x8c,0x47,0xfb,}}/*6bf301c1-b94a-43e9-ba31-d494598c47fb*/,"Office Visio Pro 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x6bf301c1,0xb94a,0x43e9,{0xba,0x31,0xd4,0x94,0x59,0x8c,0x47,0xfb,}}/*6bf301c1-b94a-43e9-ba31-d494598c47fb*/,"Office Visio Pro 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xb234abe3,0x0857,0x4f9c,{0xb0,0x5a,0x4d,0xc3,0x14,0xf8,0x55,0x57,}}/*b234abe3-0857-4f9c-b05a-4dc314f85557*/,"Office Visio Pro 2016 XC2R",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xb234abe3,0x0857,0x4f9c,{0xb0,0x5a,0x4d,0xc3,0x14,0xf8,0x55,0x57,}}/*b234abe3-0857-4f9c-b05a-4dc314f85557*/,"Office Visio Pro 2016 XC2R",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xaa2a7821,0x1827,0x4c2c,{0x8f,0x1d,0x45,0x13,0xa3,0x4d,0xda,0x97,}}/*aa2a7821-1827-4c2c-8f1d-4513a34dda97*/,"Office Visio Standard 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xaa2a7821,0x1827,0x4c2c,{0x8f,0x1d,0x45,0x13,0xa3,0x4d,0xda,0x97,}}/*aa2a7821-1827-4c2c-8f1d-4513a34dda97*/,"Office Visio Standard 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x361fe620,0x64f4,0x41b5,{0xba,0x77,0x84,0xf8,0xe0,0x79,0xb1,0xf7,}}/*361fe620-64f4-41b5-ba77-84f8e079b1f7*/,"Office Visio Standard 2016 XC2R",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0x361fe620,0x64f4,0x41b5,{0xba,0x77,0x84,0xf8,0xe0,0x79,0xb1,0xf7,}}/*361fe620-64f4-41b5-ba77-84f8e079b1f7*/,"Office Visio Standard 2016 XC2R",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xbb11badf,0xd8aa,0x470e,{0x93,0x11,0x20,0xea,0xf8,0x0f,0xe5,0xcc,}}/*bb11badf-d8aa-470e-9311-20eaf80fe5cc*/,"Office Word 2016",EPID_OFFICE2013,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
{{0xbb11badf,0xd8aa,0x470e,{0x93,0x11,0x20,0xea,0xf8,0x0f,0xe5,0xcc,}}/*bb11badf-d8aa-470e-9311-20eaf80fe5cc*/,"Office Word 2016",EPID_OFFICE2016,APP_ID_OFFICE2013,KMS_ID_OFFICE2016},
// End marker (necessity should be removed when time permits)
// End marker (necessity should be removed when time permits)
@ -135,7 +135,10 @@ Use \fIePID\fR as Windows ePID. If specified, \fB-r\fR is disregarded for Window
Use \fIePID\fR as Office 2010 ePID (including Project and Visio). If specified, \fB-r\fR is disregarded for Office 2010.
Use \fIePID\fR as Office 2010 ePID (including Project and Visio). If specified, \fB-r\fR is disregarded for Office 2010.
.IP"\fB-3\fR \fIePID\fR"
.IP"\fB-3\fR \fIePID\fR"
Use \fIePID\fR as Office 2013/2016 ePID (including Project and Visio). If specified, \fB-r\fR is disregarded for Office 2013/2016.
Use \fIePID\fR as Office 2013 ePID (including Project and Visio). If specified, \fB-r\fR is disregarded for Office 2013.
.IP"\fB-6\fR \fIePID\fR"
Use \fIePID\fR as Office 2016 ePID (including Project and Visio). If specified, \fB-r\fR is disregarded for Office 2016.
.IP"\fB-H\fR \fIHwId\fR"
.IP"\fB-H\fR \fIHwId\fR"
Use \fIHwId\fR for all products. All HWIDs in the ini file (see \fB-i\fR) will not be used. In an ini file you can specify a seperate HWID for each \fIapplication-guid\fR. This is not possible when entering a HWID from the command line.
Use \fIHwId\fR for all products. All HWIDs in the ini file (see \fB-i\fR) will not be used. In an ini file you can specify a seperate HWID for each \fIapplication-guid\fR. This is not possible when entering a HWID from the command line.
@ -162,15 +165,15 @@ These options determine how ePIDs are generated if
.br
.br
- the file specified by \fB-i\fR cannot be opened or
- the file specified by \fB-i\fR cannot be opened or
.br
.br
- the file specified by \fB-i\fR does not contain the \fIapplication-guid\fR for the KMS request
- the file specified by \fB-i\fR does not contain an ePID for the KMS request
\fB-r0\fR means there are no random ePIDs. vlmcsd simply issues default ePIDs that are built into the binary at compile time. \fBPro:\fR behaves like real KMS server that also always issues the same ePID. \fBCon\fR: Microsoft may start blacklisting again and the default ePID may not work any longer.
\fB-r0\fR means there are no random ePIDs. vlmcsd simply issues default ePIDs that are built into the binary at compile time. \fBPro:\fR behaves like real KMS server that also always issues the same ePID. \fBCon:\fR Microsoft may start blacklisting again and the default ePID may not work any longer.
\fB-r1\fR instructs vlmcsd to generate random ePIDs when the program starts or receives a SIGHUP signal and uses these ePIDs until it is stopped or receives another SIGHUP. Most other KMS emulators generate a new ePID on every KMS request. This is easily detectable. Microsoft could just modify sppsvc.exe in a way that it always sends two identical KMS requests in two RPC requests but over the same TCP connection. If both KMS responses contain the different ePIDs, the KMS server is not genuine. \fB-r1\fR is the default mode. \fB-r1\fR also ensures that all three ePIDs (Windows, Office 2010 and Office 2013) use the same OS build number and LCID (language id).
\fB-r1\fR instructs vlmcsd to generate random ePIDs when the program starts or receives a SIGHUP signal and uses these ePIDs until it is stopped or receives another SIGHUP. Most other KMS emulators generate a new ePID on every KMS request. This is easily detectable. Microsoft could just modify sppsvc.exe in a way that it always sends two identical KMS requests in two RPC requests but over the same TCP connection. If both KMS responses contain the different ePIDs, the KMS server is not genuine. \fB-r1\fR is the default mode. \fB-r1\fR also ensures that all three ePIDs (Windows, Office 2010 and Office 2013) use the same OS build number and LCID (language id).
If vlmcsd has been started by an internet superserver, \fB-r1\fR works identically to \fB-r2\fR. This is simply due to the fact that vlmcsd is started upon a connection request and does not stay in memory after servicing a KMS request.
If vlmcsd has been started by an internet superserver, \fB-r1\fR works almost identically to \fB-r2\fR. The only exception occurs if you send more than one activation request over the same TCP connection. This is simply due to the fact that vlmcsd is started upon a connection request and does not stay in memory after servicing a KMS request. Consider using \fB-r0\fR or \fB-w\fR, \fB-0\fR, \fB-3\fR and \fB-6\fB when starting vlmcsd by an internet superserver.
\fB-r2\fR behaves like most other KMS server emulators with random support and generates a new random ePID on every request. Use this mode with "care". However since Microsoft currently does not seem to do any verification of the ePID, you currently don't need to pay attention to ePIDs at all.
\fB-r2\fR behaves like most other KMS server emulators with random support and generates a new random ePID on every request. \fB-r2\fR should be treated as debugging option only because it allows very easy emulator detection.
.IP"\fB-C\fR \fILCID\fR"
.IP"\fB-C\fR \fILCID\fR"
Do not randomize the locale id part of the ePID and use \fILCID\fR instead. The \fILCID\fR must be specified as a decimal number, e.g. 1049 for "Russian - Russia". This option has no effect if the ePID is not randomized at all, e.g. if it is selected from the command line or an ini file.
Do not randomize the locale id part of the ePID and use \fILCID\fR instead. The \fILCID\fR must be specified as a decimal number, e.g. 1049 for "Russian - Russia". This option has no effect if the ePID is not randomized at all, e.g. if it is selected from the command line or an ini file.
@ -73,7 +73,7 @@ Can be TRUE or FALSE. Specifies whether you want to use the NDR64 transfer synta
Can be TRUE or FALSE. Specifies whether you want to use bind time feature negotiation in RPC. See options \fB-b0\fR and \fB-b1\fR in \fBvlmcsd\fR(8). The default is TRUE.
Can be TRUE or FALSE. Specifies whether you want to use bind time feature negotiation in RPC. See options \fB-b0\fR and \fB-b1\fR in \fBvlmcsd\fR(8). The default is TRUE.
.IP"\fBRandomizationLevel\fR"
.IP"\fBRandomizationLevel\fR"
The \fIargument\fR must 0, 1 or 2. This specifies the ePID randomization level. See options \fB-r0\fR, \fB-r1\fR and \fB-r2\fR in \fBvlmcsd\fR(8). The default randomization level is 1.
The \fIargument\fR must 0, 1 or 2. This specifies the ePID randomization level. See options \fB-r0\fR, \fB-r1\fR and \fB-r2\fR in \fBvlmcsd\fR(8). The default randomization level is 1. A \fBRandomizationLevel\fR of 2 is not recommended and should be treated as a debugging level.
.IP"\fBLCID\fR"
.IP"\fBLCID\fR"
Use a specific culture id (LCID) even if the ePID is randomized. The \fIargument\fR must be a number between 1 and 32767. While any number in that range is valid, you should use an offcial LCID. A list of assigned LCIDs can be found at http://msdn.microsoft.com/en\-us/goglobal/bb964664.aspx. On the command line you control this setting with option \fB-C\fR.
Use a specific culture id (LCID) even if the ePID is randomized. The \fIargument\fR must be a number between 1 and 32767. While any number in that range is valid, you should use an offcial LCID. A list of assigned LCIDs can be found at http://msdn.microsoft.com/en\-us/goglobal/bb964664.aspx. On the command line you control this setting with option \fB-C\fR.
@ -111,24 +111,20 @@ Run vlmcsd as another, preferrably less privileged, user. The \fIargument\fR can
.IP"\fBGroup\fR"
.IP"\fBGroup\fR"
Run vlmcsd as another, preferrably less privileged, group. The \fIargument\fR can be a group name or a numeric group id. You must have the required privileges (capabilities on Linux) to change the security context of a process without providing any credentials (a password in most cases). On most unixoid OSses 'root' is the only user who has these privileges in the default configuration. This setting is not available in the native Windows version of vlmcsd. See \fB-g\fR in \fBvlmcsd\fR(8). This setting cannot be changed on the fly by sending SIGHUP to vlmcsd.
Run vlmcsd as another, preferrably less privileged, group. The \fIargument\fR can be a group name or a numeric group id. You must have the required privileges (capabilities on Linux) to change the security context of a process without providing any credentials (a password in most cases). On most unixoid OSses 'root' is the only user who has these privileges in the default configuration. This setting is not available in the native Windows version of vlmcsd. See \fB-g\fR in \fBvlmcsd\fR(8). This setting cannot be changed on the fly by sending SIGHUP to vlmcsd.
.SH "SPECIAL KEYWORDS"
.IP "\fBWindows\fR"
Any valid GUID is being treated as a special \fBkeyword\fR in the ini file. It is used to select a specfic ePID and HwId for an application GUID. The \fIargument\fR has the form \fIePID\fR [ / \fIHwId\fR ]. KMS currently knows only 3 application GUIDs:
The \fIargument\fR has the form \fIePID\fR [ / \fIHwId\fR ]. Always use \fIePID\fR and \fIHwId\fR for Windows activations. If specified, \fBRandomizationLevel\fR for Windows activitations will be ignored.
The \fIargument\fR has the form \fIePID\fR [ / \fIHwId\fR ]. Always use \fIePID\fR and \fIHwId\fR for Office 2010 activations. If specified, \fBRandomizationLevel\fR for Office 2010 activitations will be ignored.
To use specific ePIDs for Windows, Office 2010 and Office 2013/2016 you could add the following lines to vlmcsd.ini:
.IP"\fBOffice2013\fR"
The \fIargument\fR has the form \fIePID\fR [ / \fIHwId\fR ]. Always use \fIePID\fR and \fIHwId\fR for Office 2013 activations. If specified, \fBRandomizationLevel\fR for Office 2013 activitations will be ignored.
The \fIargument\fR has the form \fIePID\fR [ / \fIHwId\fR ]. Always use \fIePID\fR and \fIHwId\fR for Office 2016 activations. If specified, \fBRandomizationLevel\fR for Office 2016 activitations will be ignored.
The ePID is currently a comment only. You can specify any string up to 63 bytes. In Windows 7 Microsoft has blacklisted few ( < 10 ) ePIDs that were used in KMSv5 versions of the "ratiborus virtual machine". Microsoft has given up on blacklisting when KMS emulators appeared in the wild.
.SH"VALID EPIDS"
The ePID is currently a comment only. You can specify any string up to 63 bytes. In Windows 7 Microsoft has blacklisted few ( < 10 ) ePIDs that were used in KMSv5 versions of the "Ratiborus Virtual Machine". Microsoft has given up on blacklisting when KMS emulators appeared in the wild.
Even if you can use "Activated by cool hacker guys" as an ePID, you may wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't know how these "valid" ePIDs look like exactly, do not use GUIDS in vlmcsd.ini. vlmcsd provides internal mechanisms to generate valid ePIDs.
Even if you can use "Activated by cool hacker guys" as an ePID, you may wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't know how these "valid" ePIDs look like exactly, do not use GUIDS in vlmcsd.ini. vlmcsd provides internal mechanisms to generate valid ePIDs.