-
Notifications
You must be signed in to change notification settings - Fork 1
/
vlmcs.1.html
515 lines (389 loc) · 16.5 KB
/
vlmcs.1.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Tue Aug 25 00:13:50 2015 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta name="generator" content="groff -Thtml, see www.gnu.org">
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="Content-Style" content="text/css">
<style type="text/css">
p { margin-top: 0; margin-bottom: 0; vertical-align: top }
pre { margin-top: 0; margin-bottom: 0; vertical-align: top }
table { margin-top: 0; margin-bottom: 0; vertical-align: top }
h1 { text-align: center }
</style>
<title>VLMCS</title>
</head>
<body>
<h1 align="center">VLMCS</h1>
<a href="#NAME">NAME</a><br>
<a href="#SYNOPSIS">SYNOPSIS</a><br>
<a href="#DESCRIPTION">DESCRIPTION</a><br>
<a href="#OPTIONS">OPTIONS</a><br>
<a href="#FILES">FILES</a><br>
<a href="#EXAMPLES">EXAMPLES</a><br>
<a href="#BUGS">BUGS</a><br>
<a href="#AUTHOR">AUTHOR</a><br>
<a href="#CREDITS">CREDITS</a><br>
<a href="#SEE ALSO">SEE ALSO</a><br>
<hr>
<h2>NAME
<a name="NAME"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">vlmcs − a
client for testing and/or charging KMS servers</p>
<h2>SYNOPSIS
<a name="SYNOPSIS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>vlmcs</b> [
<i>options</i> ] [ <i>target</i> ] [ <i>options</i> ]</p>
<p style="margin-left:11%; margin-top: 1em"><i>target</i>
can be one of the following:</p>
<p style="margin-left:22%; margin-top: 1em"><i>hostname</i>|<i>ipaddress</i>[:<i>tcp-port</i>]
or to query a specific KMS server (example: vlmcs
kms.example.com:1688). <br>
.<i>domain</i> to automatically detect KMS servers via DNS
for <i>domain</i> (example: vlmcs .example.com). Please note
the dot before <i>domain</i>. <i><br>
-</i> (a single dash) to detect KMS servers in your own
domain.</p>
<p style="margin-left:11%; margin-top: 1em">If you use
<i>ipaddress</i>:<i>port</i> as the <i>target</i>, the
<i>ipaddress</i> must be enclosed in brackets if it contains
colons, e.g. [2001:db8:dead:beef::1]:1688. If you use a
link-local IPv6 address on Unix systems, you must append a
percent sign and the interface identifier of the source
interface, for example fe80::dead:beef%eth0.</p>
<p style="margin-left:11%; margin-top: 1em">If you omit the
<i>target</i>, 127.0.0.1:1688 will be used except if you use
<b>-i6</b>. In this case the default target is
[::1]:1688.</p>
<h2>DESCRIPTION
<a name="DESCRIPTION"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>vlmcs</b> is
a program that can be used to test a KMS server that
provides activation for several Microsoft products. The KMS
server may also be an emulator. It supports KMS protocol
versions 4, 5 and 6.</p>
<p style="margin-left:11%; margin-top: 1em"><b>vlmcs</b>
generates one or more activation requests for a Microsoft
KMS product and sends it to a KMS server. It then analyzes
and displays the responses of the KMS server.</p>
<p style="margin-left:11%; margin-top: 1em"><b>vlcms</b>
checks both the DCE-RPC protocol and the activation message
for correctness and reports any errors that it finds.</p>
<p style="margin-left:11%; margin-top: 1em"><b>vlmcs</b>
can also be used to "charge" a KMS server. A
Microsoft KMS server sends correct activation messages only
if it detects a certain minimum of clients (25 for Windows
client OSses, 5 otherwise) on the network. This is
Microsoft’s futile attempt to prevent running a KMS
server in a home environment.</p>
<h2>OPTIONS
<a name="OPTIONS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>-h</b> or
<b>-?</b></p>
<p style="margin-left:22%;">Show help.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>-x</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Show valid <i>application</i>s that can be used with
<b>-l</b>.</p> </td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>-e</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Show some examples how to use vlmcs correctly.</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>-v</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Be verbose. Instead of just displaying the returned ePID
and the HwId (protocol v6 only) vlmcsd shows all details of
the query and the response.</p></td></tr>
</table>
<p style="margin-left:11%;"><b>-l</b>
<i>application</i></p>
<p style="margin-left:22%;">Request activation for a
specific <i>application</i>. Valid applications can be
displayed by using <b>-x</b>. The default <i>application</i>
is <i>Windows Vista Business</i>. The list of available
applications is not complete. You may supply GUIDs with
<b>-a</b>, <b>-k</b> and <b>-s</b> to specify applications
that are not listed with <b>-x</b>. The <b>-l</b> option is
used as a shortcut for the most common applications.</p>
<p style="margin-left:11%;"><b>-4</b>, <b>-5</b> and
<b>-6</b></p>
<p style="margin-left:22%;">Force version 4, 5 or 6 of the
KMS protocol. The default is to select a suitable version
according to the <i>application</i> selected. Plese note
that some products (e.g. Office 2013) may use different
protocols with different versions of Windows.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>-m</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Let the client pretend to be a virtual machine. Early
versions of Microsoft’s KMS server did not increase
the client count if the request came from a virtual machine.
Newer versions ignore this flag.</p></td></tr>
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>-d</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Use NetBIOS names instead of DNS names. By default
vlmcsd generates some random DNS names for each request. If
you prefer NetBIOS names, you may use <b>-d</b>. A real
Microsoft activation client uses DNS names or NetBIOS
depending on the client name configuration. KMS servers
treat the workstation name as a comment that affects logging
only. Clients will be identified by a GUID that can be
specified using <b>-c</b>. <b>-d</b> has no effect if you
also specify <b>-w</b>.</p></td></tr>
</table>
<p style="margin-left:11%;"><b>-a</b>
<i>application-guid</i></p>
<p style="margin-left:22%;">Send requests with a specific
<i>application-guid</i>. There are currently only three
known valid <i>application-guid</i>s:</p>
<p style="margin-left:22%; margin-top: 1em">55c92734-d682-4d71-983e-d6ec3f16059f
(Windows) <br>
59a52881-a989-479d-af46-f275c6370663 (Office 2010) <br>
0ff1ce15-a989-479d-af46-f275c6370663 (Office 2013)</p>
<p style="margin-left:22%; margin-top: 1em">A Microsoft KMS
server uses these GUIDs to have seperate counters for the
already activated clients. A client that does not contact
the KMS server within 30 days will be deleted from the
database. Emulated KMS servers are always fully charged.</p>
<p style="margin-left:11%;"><b>-k</b> <i>kms-guid</i></p>
<p style="margin-left:22%;">Send requests with a specific
<i>kms-guid</i>. A Microsoft KMS server uses these GUIDs as
a product id to decide whether to grant activation or not. A
list of current <i>kms-guid</i>s can be found in kms.c
(table KmsIdList). Emulated KMS servers grant activation
unconditionally and do not check the <i>kms-guid</i>.</p>
<p style="margin-left:11%;"><b>-s</b>
<i>activation-guid</i></p>
<p style="margin-left:22%;">The <i>activation-guid</i>
defines the actual product, e.g. "Windows 8.1
Professional WMC KMSCLIENT edition". A
<i>activation-guid</i> maps 1:1 to a product key. However,
neither a Microsoft KMS server nor emulated servers check
this id. The <i>activation-guid</i> is useful in logging to
get a specific product description like "Windows 8.1
Professional WMC". A list of current
<i>activation-guid</i>s can be found in kms.c (table
ExtendedProductList).</p>
<p style="margin-left:11%;"><b>-n</b> <i>requests</i></p>
<p style="margin-left:22%;">Send <i>requests</i> requests
to the server. The default is to send at least one request
and enough subsequent requests that the server is fully
charged afterwards for the <i>application−guid</i> you
selected (explicitly with <b>-a</b> or implicitly by using
<b>-l</b>).</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>-T</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Causes to use a new TCP connection for each request if
multiple requests are sent with vlmcsd. This is useful when
you want to test an emulated KMS server whether it suffers
from memory leaks. To test for memory leaks use <b>-n</b>
with a large number of requests (> 100000) and then test
twice (with and without <b>-T</b>). This option may become
neccessary for future versions of Microsoft’s KMS
server because multiple requests with different
<i>clients-guid</i>s for the same <i>kms-id-guid</i> are
impossible in a real KMS szenario over the same TCP
connection.</p> </td></tr>
</table>
<p style="margin-left:11%;"><b>-c</b>
<i>client-machine-guid</i></p>
<p style="margin-left:22%;">Normally vlmcs generates a
random <i>client-machine-guid</i> for each request. By using
this option you can specify a fixed
<i>client-machine-guid</i> This causes a Microsoft KMS not
to increment its client count because it receives multiple
requests for the same client. Thus do not use <b>-c</b> if
you want to charge a real KMS server.</p>
<p style="margin-left:11%;"><b>-o</b>
<i>previous-client-machine-guid</i></p>
<p style="margin-left:22%;">If the
<i>client-machine-guid</i> changes for some reason, the real
KMS client stores a <i>previous-client-machine-guid</i>
which is sent to the KMS server. This happens rarely and
usually 00000000-0000-0000-0000-000000000000 is used. You
can use <b>-o</b> to specify a different
<i>previous-client-machine-guid</i>.</p>
<p style="margin-left:11%;"><b>-G</b> <i>filename</i></p>
<p style="margin-left:22%;">Grabs ePIDs and HWIDs from a
KMS server and writes the information to <i>filename</i> in
format suitable to be used as a configuration file (aka ini
file) for <b>vlmcsd</b>(8). This is especially useful if you
have access to a genuine KMS server and want to use the same
data with <b>vlmcsd</b>(8).</p>
<p style="margin-left:22%; margin-top: 1em">If
<i>filename</i> does not exist, it will be created. If you
specify an existing <i>filename</i>, it will be updated to
use the information received from the remote KMS server and
a backup <i>filename</i>~ will be created.</p>
<p style="margin-left:22%; margin-top: 1em"><b>-G</b>
cannot be used with <b>-l</b>, <b>-4</b>, <b>-5</b>,
<b>-6</b>, <b>-a</b>, <b>-s</b>, <b>-k</b>, <b>-r</b> and
<b>-n</b></p>
<p style="margin-left:11%;"><b>-w</b>
<i>workstation-name</i></p>
<p style="margin-left:22%;">Send requests with a specific
<i>workstation-name</i>. This disables the random generator
for the workstation name. Since it is a comment only, this
option does not have much effect.</p>
<p style="margin-left:11%;"><b>-r</b>
<i>required-client-count</i></p>
<p style="margin-left:22%;">Also known as the "N count
policy". Tells the KMS server that successful
activation requires <i>required-client-count</i> clients.
The default is the <i>required-client-count</i> that the
product would need if the request was a real activation. A
Microsoft KMS server counts clients up to the double amount
what was specified with <b>-r</b>. This option can be used
to "overcharge" a Microsoft KMS server.</p>
<p style="margin-left:11%;"><b>−t </b><i>status</i></p>
<p style="margin-left:22%;">Reports a specific license
status to the KMS server. <i>status</i> is a number that can
be from 0 to 6. 0=unlicensed, 1=licensed, 2=OOB grace, 3=OOT
grace, 4=Non-genuinue grace, 5=notification, 6=extended
grace. Refer to
<a href="http://technet.microsoft.com/en-us/library/ff686879.aspx#_Toc257201371">TechNet</a>
for more information. A Microsoft KMS server collects this
information for statistics only.</p>
<p style="margin-left:11%;"><b>-g</b>
<i>binding-expiration</i></p>
<p style="margin-left:22%;">This tells the KMS server how
long a client will stay in its current license status. This
can be the remaining OOB time (the grace peroid that is
granted between installation of a product and when
activation is actuall required) or the remaining time when
KMS activation must be renewed. <i>binding-expiration</i> is
specified in minutes. A Microsoft KMS server apparantly does
not use this information.</p>
<p style="margin-left:11%;"><b>-i</b>
<i>protocol-version</i></p>
<p style="margin-left:22%;">Force the use of Internet
protocol <i>protocol-version</i>. Allowed values are 4
(IPv4) and 6 (IPv6). This option is useful only if you
specfiy a <i>hostname</i> and not an <i>ip-address</i> on
the command line.</p>
<table width="100%" border="0" rules="none" frame="void"
cellspacing="0" cellpadding="0">
<tr valign="top" align="left">
<td width="11%"></td>
<td width="3%">
<p><b>-p</b></p></td>
<td width="8%"></td>
<td width="78%">
<p>Do not set the RPC_PF_MULTIPLEX flag in the RPC bind
request. This can be used to test if the KMS server uses the
same setting of this flag in the RPC bind respone. Some KMS
emulators don’t set this correctly.</p></td></tr>
</table>
<p style="margin-left:11%;"><b>-N0</b> and <b>-N1</b></p>
<p style="margin-left:22%;">Disables (<b>-N0</b>) or
enables (<b>-N1</b>) the NDR64 transfer syntax in the RPC
protocol. Disable NDR64 only in case of problems. If NDR64
is not used, vlmcs cannot detect many RPC protocol errors in
KMS emulators. If you want to test whether a KMS emulator
fully supports NDR64, you must use the <b>-n</b> option to
send at least two requests. This is because
Microsoft’s client always sends the first request
using NDR32 syntax and subsequent requests using NDR64
syntax.</p>
<p style="margin-left:11%;"><b>-B0</b> and <b>-B1</b></p>
<p style="margin-left:22%;">Disables (<b>-B0</b>) or
enables (<b>-B1</b>) bind time feature negotiation (BTFN) in
the RPC protocol. Disable BTFN only in case of problems. If
BTFN is not used, vlmcs cannot detect many RPC protocol
errors in KMS emulators.</p>
<p style="margin-left:11%; margin-top: 1em">Options that do
not require an argument can be specified together with a
single dash, e.g. vlmcs -6mvT. If you specify an option more
than once, the last occurence will be in effect.</p>
<h2>FILES
<a name="FILES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>vlmcsd.ini</b>(5)</p>
<h2>EXAMPLES
<a name="EXAMPLES"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>vlmcs
kms.example.com</b></p>
<p style="margin-left:22%;">Request activation for Windows
Vista using v4 protocol from kms.example.com. Repeat
activation requests until server is charged for all Windows
products.</p>
<p style="margin-left:11%;"><b>vlmcs -</b></p>
<p style="margin-left:22%;">Request activation for Windows
Vista using v4 protocol from a KMS server that is published
via DNS for the current domain.</p>
<p style="margin-left:11%;"><b>vlmcs .example.com</b></p>
<p style="margin-left:22%;">Request activation for Windows
Vista using v4 protocol from a KMS server that is published
via DNS for domain example.com.</p>
<p style="margin-left:11%;"><b>vlmcs -6 -l Office2013 -v -n
1</b></p>
<p style="margin-left:22%;">Request exactly one activation
for Office2013 using v6 protocol from localhost. Display
verbose results.</p>
<p style="margin-left:11%;"><b>vlmcs kms.bigcompany.com -G
/etc/vlmcsd.ini</b></p>
<p style="margin-left:22%;">Get ePIDs and HWIDs from
kms.bigcompany.com and create/update /etc/vlmcsd.ini
accordingly.</p>
<h2>BUGS
<a name="BUGS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Some platforms
(e.g. Solaris) may have a <b>man</b>(7) system that does not
handle URLs. URLs may be omitted in the documentation on
those platforms. Cygwin, Linux, FreeBSD and Mac OS X are
known to work correctly.</p>
<h2>AUTHOR
<a name="AUTHOR"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Written by
Hotbird64</p>
<h2>CREDITS
<a name="CREDITS"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em">Thanks to
CODYQX4, crony12, deagles, DougQaid, eIcn, mikmik38,
nosferati87, qad, Ratiborus, vityan666, ...</p>
<h2>SEE ALSO
<a name="SEE ALSO"></a>
</h2>
<p style="margin-left:11%; margin-top: 1em"><b>vlmcsd</b>(7),
<b>vlmcsd</b>(8), <b>vlmcsdmulti</b>(1)</p>
<hr>
</body>
</html>