elie/vlmcsd
1
0
Fork 0
mirror of https://github.com/Wind4/vlmcsd.git synced 2025-06-22 01:23:40 +02:00
Code Issues Packages Projects Releases Wiki Activity

vlmcsd-svn1099-2016-10-25-Hotbird64

Browse Source
This commit is contained in:
Wind4
2016-10-31 20:59:15 +08:00
parent 936811ff5c
commit fcbbc40d60
39 changed files with 904 additions and 305 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
man/vlmcs.1.html
View File

@ -1,5 +1,5 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
<!-- CreationDate: Tue Oct 25 06:23:57 2016 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

BIN
man/vlmcs.1.pdf
View File

Binary file not shown.

5
man/vlmcsd-floppy.7
View File

@ -1,5 +1,5 @@
.mso www.tmac
.TH "VLMCSD-FLOPPY" 7 "June 2016" "Hotbird64" "KMS Activation Manual"
.TH "VLMCSD-FLOPPY" 7 "October 2016" "Hotbird64" "KMS Activation Manual"
.LO 8
.SH NAME
@ -166,6 +166,9 @@ Sets the password for the pre-defined guest user. This user has the same privili
.IP "\fBINETD=\fRY | N"
\fBINETD=\fRY specifies that \fBinetd\fR(8) should automatically be started. That means you can telnet and ftp to your virtual machine.
.IP "\fBVLMCSD_EXTRA_ARGS=\fR\fIcomma-seperated-argument-list\fR"
Allows you to specify additional command line options that will be passed to \fBvlmcsd\fR(8). Instead of spaces you use commas between arguments. Example: \fBVLMCSD_EXTRA_ARGS=\fR\-c1,-K3,-M1
.SH OPERATION
.SS Diskless System

8
man/vlmcsd-floppy.7.dos.txt
View File

@ -310,6 +310,12 @@ CONFIGURATION
That means you can telnet and ftp to your virtual machine.
VLMCSD_EXTRA_ARGS=comma-seperated-argument-list
Allows you to specify additional command line options that will
be passed to vlmcsd(8). Instead of spaces you use commas between
arguments. Example: VLMCSD_EXTRA_ARGS=-c1,-K3,-M1
OPERATION
Diskless System
The floppy144.vfd virtual machine is a diskless system that works
@ -527,4 +533,4 @@ SEE ALSO
Hotbird64 June 2016 VLMCSD-FLOPPY(7)
Hotbird64 October 2016 VLMCSD-FLOPPY(7)

10
man/vlmcsd-floppy.7.html
View File

@ -1,5 +1,5 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
<!-- CreationDate: Tue Oct 25 06:23:57 2016 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
@ -499,6 +499,14 @@ pre-defined guest user. This user has the same priviliges
<b>inetd</b>(8) should automatically be started. That means
you can telnet and ftp to your virtual machine.</p>
<p style="margin-left:11%;"><b>VLMCSD_EXTRA_ARGS=</b><i>comma-seperated-argument-list</i></p>
<p style="margin-left:22%;">Allows you to specify
additional command line options that will be passed to
<b>vlmcsd</b>(8). Instead of spaces you use commas between
arguments. Example: <b>VLMCSD_EXTRA_ARGS=</b>-c1,-K3,-M1</p>
<h2>OPERATION
<a name="OPERATION"></a>
</h2>

BIN
man/vlmcsd-floppy.7.pdf
View File

Binary file not shown.

8
man/vlmcsd-floppy.7.unix.txt
View File

@ -310,6 +310,12 @@ CONFIGURATION
That means you can telnet and ftp to your virtual machine.
VLMCSD_EXTRA_ARGS=comma-seperated-argument-list
Allows you to specify additional command line options that will
be passed to vlmcsd(8). Instead of spaces you use commas between
arguments. Example: VLMCSD_EXTRA_ARGS=-c1,-K3,-M1
OPERATION
Diskless System
The floppy144.vfd virtual machine is a diskless system that works
@ -527,4 +533,4 @@ SEE ALSO
Hotbird64 June 2016 VLMCSD-FLOPPY(7)
Hotbird64 October 2016 VLMCSD-FLOPPY(7)

2
man/vlmcsd.7.html
View File

@ -1,5 +1,5 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
<!-- CreationDate: Tue Oct 25 06:23:57 2016 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

BIN
man/vlmcsd.7.pdf
View File

Binary file not shown.

8
man/vlmcsd.8
View File

@ -203,6 +203,14 @@ The SKU ID is not checked. Like a genuine KMS server vlmcsd activates a product
.IP "\fB-c0\fR and \fB-c1\fR"
\fB-c1\fR causes vlmcsd to check if the client time differs no more than four hours from the system time. \fB-c0\fR (the default) disables this check. \fB-c1\fR is useful to prevent emulator detection. A client that tries to detect an emulator could simply send two subsequent request with two time stamps that differ more than four hours from each other. If both requests succeed, the server is an emulator. If you specify \fB-c1\fR on a system with no reliable time source, activations will fail. It is ok to set the correct system time after you started vlmcsd.
.IP "\fB-M0\fR and \fB-M1\fR"
Disables (\fB-M0\fR) or enables (\fB-M1\fR) maintaining a list of client machine IDs (CMIDs). The default is \fB-M0\fR. \fB-M1\fR is useful to prevent emulator detection. By maintaing a CMID list, vlmcsd reports current active clients exactly like a genuine KMS emulator. This includes bug compatibility to the extent that you can permanently kill a genuine KMS emulator by sending an "overcharge request" with a required client count of 376 or more and then request activation for 671 clients. vlmcsd can be reset from this condition by restarting it. If \fB-M0\fR is used, vlmcsd reports current active clients as good as possible. If no client sends an "overcharge request", it is not possible to detect vlmcsd as an emulator with \fB-M0\fR. \fB-M1\fR requires the allocation of a buffer that is about 50 kB in size. On hardware with few memory resources use it only if you really need it.
If you start vlmcsd from an internet superserver, \fB-M1\fR cannot be used. Since vlmcsd exits after each activation, it cannot maintain any state in memory.
.IP "\fB-E0\fR and \fB-E1\fR"
These options are ignored if you do not also specify \fB-M1\fR. If you use \fB-E0\fR (the default), vlmcsd starts up as a fully "charged" KMS server. Clients activate immediately. \fB-E1\fR lets you start up vlmcsd with an empty CMID list. Activation will start when the required minimum clients (25 for Windows Client OSses, 5 for Windows Server OSses and Office) have registered with the KMS server. As long as the minimum client count has not been reached, clients end up in HRESULT 0xC004F038 "The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator". You may use \fBvlmcs\fR(1) or another KMS client emulator to "charge" vlmcsd. \fB-E1\fR does not improve emulator detection prevention. It's primary purpose is to help developers of KMS clients to test "charging" a KMS server.
.IP "\fB-R\fR \fIrenewal-interval\fR"
Instructs clients to renew activation every \fIrenewal-interval\fR. The \fIrenewal-interval\fR is a number optionally immediately followed by a letter indicating the unit. Valid unit letters are s (seconds), m (minutes), h (hours), d (days) and w (weeks). If you do not specify a letter, minutes is assumed.

38
man/vlmcsd.8.dos.txt
View File

@ -449,6 +449,44 @@ OPTIONS
system time after you started vlmcsd.
-M0 and -M1
Disables (-M0) or enables (-M1) maintaining a list of client
machine IDs (CMIDs). The default is -M0. -M1 is useful to pre‐
vent emulator detection. By maintaing a CMID list, vlmcsd
reports current active clients exactly like a genuine KMS emula‐
tor. This includes bug compatibility to the extent that you can
permanently kill a genuine KMS emulator by sending an "over‐
charge request" with a required client count of 376 or more and
then request activation for 671 clients. vlmcsd can be reset
from this condition by restarting it. If -M0 is used, vlmcsd
reports current active clients as good as possible. If no client
sends an "overcharge request", it is not possible to detect vlm‐
csd as an emulator with -M0. -M1 requires the allocation of a
buffer that is about 50 kB in size. On hardware with few memory
resources use it only if you really need it.
If you start vlmcsd from an internet superserver, -M1 cannot be
used. Since vlmcsd exits after each activation, it cannot main‐
tain any state in memory.
-E0 and -E1
These options are ignored if you do not also specify -M1. If you
use -E0 (the default), vlmcsd starts up as a fully "charged" KMS
server. Clients activate immediately. -E1 lets you start up vlm‐
csd with an empty CMID list. Activation will start when the
required minimum clients (25 for Windows Client OSses, 5 for
Windows Server OSses and Office) have registered with the KMS
server. As long as the minimum client count has not been
reached, clients end up in HRESULT 0xC004F038 "The count
reported by your Key Management Service (KMS) is insufficient.
Please contact your system administrator". You may use vlmcs(1)
or another KMS client emulator to "charge" vlmcsd. -E1 does not
improve emulator detection prevention. It's primary purpose is
to help developers of KMS clients to test "charging" a KMS
server.
-R renewal-interval
Instructs clients to renew activation every renewal-interval.
The renewal-interval is a number optionally immediately followed

47
man/vlmcsd.8.html
View File

@ -1,5 +1,5 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
<!-- CreationDate: Tue Oct 25 06:23:57 2016 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
@ -667,6 +667,51 @@ system with no reliable time source, activations will fail.
It is ok to set the correct system time after you started
vlmcsd.</p>
<p style="margin-left:11%;"><b>-M0</b> and <b>-M1</b></p>
<p style="margin-left:22%;">Disables (<b>-M0</b>) or
enables (<b>-M1</b>) maintaining a list of client machine
IDs (CMIDs). The default is <b>-M0</b>. <b>-M1</b> is useful
to prevent emulator detection. By maintaing a CMID list,
vlmcsd reports current active clients exactly like a genuine
KMS emulator. This includes bug compatibility to the extent
that you can permanently kill a genuine KMS emulator by
sending an &quot;overcharge request&quot; with a required
client count of 376 or more and then request activation for
671 clients. vlmcsd can be reset from this condition by
restarting it. If <b>-M0</b> is used, vlmcsd reports current
active clients as good as possible. If no client sends an
&quot;overcharge request&quot;, it is not possible to detect
vlmcsd as an emulator with <b>-M0</b>. <b>-M1</b> requires
the allocation of a buffer that is about 50 kB in size. On
hardware with few memory resources use it only if you really
need it.</p>
<p style="margin-left:22%; margin-top: 1em">If you start
vlmcsd from an internet superserver, <b>-M1</b> cannot be
used. Since vlmcsd exits after each activation, it cannot
maintain any state in memory.</p>
<p style="margin-left:11%;"><b>-E0</b> and <b>-E1</b></p>
<p style="margin-left:22%;">These options are ignored if
you do not also specify <b>-M1</b>. If you use <b>-E0</b>
(the default), vlmcsd starts up as a fully
&quot;charged&quot; KMS server. Clients activate
immediately. <b>-E1</b> lets you start up vlmcsd with an
empty CMID list. Activation will start when the required
minimum clients (25 for Windows Client OSses, 5 for Windows
Server OSses and Office) have registered with the KMS
server. As long as the minimum client count has not been
reached, clients end up in HRESULT 0xC004F038 &quot;The
count reported by your Key Management Service (KMS) is
insufficient. Please contact your system
administrator&quot;. You may use <b>vlmcs</b>(1) or another
KMS client emulator to &quot;charge&quot; vlmcsd. <b>-E1</b>
does not improve emulator detection prevention. It&rsquo;s
primary purpose is to help developers of KMS clients to test
&quot;charging&quot; a KMS server.</p>
<p style="margin-left:11%;"><b>-R</b>
<i>renewal-interval</i></p>

BIN
man/vlmcsd.8.pdf
View File

Binary file not shown.

38
man/vlmcsd.8.unix.txt
View File

@ -449,6 +449,44 @@ OPTIONS
system time after you started vlmcsd.
-M0 and -M1
Disables (-M0) or enables (-M1) maintaining a list of client
machine IDs (CMIDs). The default is -M0. -M1 is useful to pre‐
vent emulator detection. By maintaing a CMID list, vlmcsd
reports current active clients exactly like a genuine KMS emula‐
tor. This includes bug compatibility to the extent that you can
permanently kill a genuine KMS emulator by sending an "over‐
charge request" with a required client count of 376 or more and
then request activation for 671 clients. vlmcsd can be reset
from this condition by restarting it. If -M0 is used, vlmcsd
reports current active clients as good as possible. If no client
sends an "overcharge request", it is not possible to detect vlm‐
csd as an emulator with -M0. -M1 requires the allocation of a
buffer that is about 50 kB in size. On hardware with few memory
resources use it only if you really need it.
If you start vlmcsd from an internet superserver, -M1 cannot be
used. Since vlmcsd exits after each activation, it cannot main‐
tain any state in memory.
-E0 and -E1
These options are ignored if you do not also specify -M1. If you
use -E0 (the default), vlmcsd starts up as a fully "charged" KMS
server. Clients activate immediately. -E1 lets you start up vlm‐
csd with an empty CMID list. Activation will start when the
required minimum clients (25 for Windows Client OSses, 5 for
Windows Server OSses and Office) have registered with the KMS
server. As long as the minimum client count has not been
reached, clients end up in HRESULT 0xC004F038 "The count
reported by your Key Management Service (KMS) is insufficient.
Please contact your system administrator". You may use vlmcs(1)
or another KMS client emulator to "charge" vlmcsd. -E1 does not
improve emulator detection prevention. It's primary purpose is
to help developers of KMS clients to test "charging" a KMS
server.
-R renewal-interval
Instructs clients to renew activation every renewal-interval.
The renewal-interval is a number optionally immediately followed

10
man/vlmcsd.ini.5
View File

@ -118,8 +118,16 @@ The SKU ID is not checked. Like a genuine KMS server vlmcsd activates a product
.IP "\fBCheckClientTime\fR"
Can be TRUE or FALSE. The default is FALSE. If you set this to TRUE \fBvlmcsd\fR(8) checks if the client time differs no more than four hours from the system time. This is useful to prevent emulator detection. A client that tries to detect an emulator could simply send two subsequent request with two time stamps that differ more than four hours from each other. If both requests succeed, the server is an emulator. If you set this to TRUE on a system with no reliable time source, activations will fail. It is ok to set the correct system time after you started \fBvlmcsd\fR(8).
.IP "\fBMaintainClients\fR"
Can be TRUE or FALSE (the default). Disables (FALSE) or enables (TRUE) maintaining a list of client machine IDs (CMIDs). TRUE is useful to prevent emulator detection. By maintaing a CMID list, \fBvlmcsd\fR(8) reports current active clients exactly like a genuine KMS emulator. This includes bug compatibility to the extent that you can permanently kill a genuine KMS emulator by sending an "overcharge request" with a required client count of 376 or more and then request activation for 671 clients. \fBvlmcsd\fR(8) can be reset from this condition by restarting it. If FALSE is used, \fBvlmcsd\fR(8) reports current active clients as good as possible. If no client sends an "overcharge request", it is not possible to detect \fBvlmcsd\fR(8) as an emulator with \fBMaintainClients\fR\~=\~FALSE. Maintaining clients requires the allocation of a buffer that is about 50 kB in size. On hardware with few memory resources use it only if you really need it.
If you start \fBvlmcsd\fR(8) from an internet superserver, this setting cannot be used. Since \fBvlmcsd\fR(8) exits after each activation, it cannot maintain any state in memory.
.IP "\fBStartEmpty\fR"
This setting is ignored if you do not also specify \fBMaintainClients\fR\~=\~TRUE. If you specify FALSE (the default), \fBvlmcsd\fR(8) starts up as a fully "charged" KMS server. Clients activate immediately. \fBStartEmpty\fR\~=\~TRUE lets you start up \fBvlmcsd\fR(8) with an empty CMID list. Activation will start when the required minimum clients (25 for Windows Client OSses, 5 for Windows Server OSses and Office) have registered with the KMS server. As long as the minimum client count has not been reached, clients end up in HRESULT 0xC004F038 "The count reported by your Key Management Service (KMS) is insufficient. Please contact your system administrator". You may use \fBvlmcs\fR(1) or another KMS client emulator to "charge" \fBvlmcsd\fR(8). Setting this parameter to TRUE does not improve emulator detection prevention. It's primary purpose is to help developers of KMS clients to test "charging" a KMS server.
.IP "\fBActivationInterval\fR"
This is the same as specifying \fB-A\fR on the command line. See \fBvlmcsd\fR(8) for details. The default is 2 hours. Example: ActivationInterval = 1h
This is the same as specifying \fB-A\fR on the command line. See \fBvlmcsd\fR(8) for details. The default is 2 hours. Example: ActivationInterval\~=\~1h
.IP "\fBRenewalInterval\fR"
This is the same as specifying \fB-R\fR on the command line. See \fBvlmcsd\fR(8) for details. The default is 7 days. Example: RenewalInterval = 3d. Please note that the KMS client decides itself when to renew activation. Even though vlmcsd sends the renewal interval you specify, it is no more than some kind of recommendation to the client. Older KMS clients did follow the recommendation from a KMS server or emulator. Newer clients do not.

40
man/vlmcsd.ini.5.dos.txt
View File

@ -243,6 +243,46 @@ KEYWORDS
csd(8).
MaintainClients
Can be TRUE or FALSE (the default). Disables (FALSE) or enables
(TRUE) maintaining a list of client machine IDs (CMIDs). TRUE is
useful to prevent emulator detection. By maintaing a CMID list,
vlmcsd(8) reports current active clients exactly like a genuine
KMS emulator. This includes bug compatibility to the extent that
you can permanently kill a genuine KMS emulator by sending an
"overcharge request" with a required client count of 376 or more
and then request activation for 671 clients. vlmcsd(8) can be
reset from this condition by restarting it. If FALSE is used,
vlmcsd(8) reports current active clients as good as possible. If
no client sends an "overcharge request", it is not possible to
detect vlmcsd(8) as an emulator with MaintainClients = FALSE.
Maintaining clients requires the allocation of a buffer that is
about 50 kB in size. On hardware with few memory resources use
it only if you really need it.
If you start vlmcsd(8) from an internet superserver, this set‐
ting cannot be used. Since vlmcsd(8) exits after each activa‐
tion, it cannot maintain any state in memory.
StartEmpty
This setting is ignored if you do not also specify Maintain‐
Clients = TRUE. If you specify FALSE (the default), vlmcsd(8)
starts up as a fully "charged" KMS server. Clients activate
immediately. StartEmpty = TRUE lets you start up vlmcsd(8) with
an empty CMID list. Activation will start when the required min‐
imum clients (25 for Windows Client OSses, 5 for Windows Server
OSses and Office) have registered with the KMS server. As long
as the minimum client count has not been reached, clients end up
in HRESULT 0xC004F038 "The count reported by your Key Management
Service (KMS) is insufficient. Please contact your system admin‐
istrator". You may use vlmcs(1) or another KMS client emulator
to "charge" vlmcsd(8). Setting this parameter to TRUE does not
improve emulator detection prevention. It's primary purpose is
to help developers of KMS clients to test "charging" a KMS
server.
ActivationInterval
This is the same as specifying -A on the command line. See vlm‐
csd(8) for details. The default is 2 hours. Example: Activation‐

54
man/vlmcsd.ini.5.html
View File

@ -1,5 +1,5 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
<!-- CreationDate: Tue Oct 25 06:23:57 2016 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
@ -386,12 +386,60 @@ to TRUE on a system with no reliable time source,
activations will fail. It is ok to set the correct system
time after you started <b>vlmcsd</b>(8).</p>
<p style="margin-left:11%;"><b>MaintainClients</b></p>
<p style="margin-left:22%;">Can be TRUE or FALSE (the
default). Disables (FALSE) or enables (TRUE) maintaining a
list of client machine IDs (CMIDs). TRUE is useful to
prevent emulator detection. By maintaing a CMID list,
<b>vlmcsd</b>(8) reports current active clients exactly like
a genuine KMS emulator. This includes bug compatibility to
the extent that you can permanently kill a genuine KMS
emulator by sending an &quot;overcharge request&quot; with a
required client count of 376 or more and then request
activation for 671 clients. <b>vlmcsd</b>(8) can be reset
from this condition by restarting it. If FALSE is used,
<b>vlmcsd</b>(8) reports current active clients as good as
possible. If no client sends an &quot;overcharge
request&quot;, it is not possible to detect <b>vlmcsd</b>(8)
as an emulator with
<b>MaintainClients&nbsp;</b>=&nbsp;FALSE. Maintaining
clients requires the allocation of a buffer that is about 50
kB in size. On hardware with few memory resources use it
only if you really need it.</p>
<p style="margin-left:22%; margin-top: 1em">If you start
<b>vlmcsd</b>(8) from an internet superserver, this setting
cannot be used. Since <b>vlmcsd</b>(8) exits after each
activation, it cannot maintain any state in memory.</p>
<p style="margin-left:11%;"><b>StartEmpty</b></p>
<p style="margin-left:22%;">This setting is ignored if you
do not also specify <b>MaintainClients&nbsp;</b>=&nbsp;TRUE.
If you specify FALSE (the default), <b>vlmcsd</b>(8) starts
up as a fully &quot;charged&quot; KMS server. Clients
activate immediately. <b>StartEmpty&nbsp;</b>=&nbsp;TRUE
lets you start up <b>vlmcsd</b>(8) with an empty CMID list.
Activation will start when the required minimum clients (25
for Windows Client OSses, 5 for Windows Server OSses and
Office) have registered with the KMS server. As long as the
minimum client count has not been reached, clients end up in
HRESULT 0xC004F038 &quot;The count reported by your Key
Management Service (KMS) is insufficient. Please contact
your system administrator&quot;. You may use <b>vlmcs</b>(1)
or another KMS client emulator to &quot;charge&quot;
<b>vlmcsd</b>(8). Setting this parameter to TRUE does not
improve emulator detection prevention. It&rsquo;s primary
purpose is to help developers of KMS clients to test
&quot;charging&quot; a KMS server.</p>
<p style="margin-left:11%;"><b>ActivationInterval</b></p>
<p style="margin-left:22%;">This is the same as specifying
<b>-A</b> on the command line. See <b>vlmcsd</b>(8) for
details. The default is 2 hours. Example: ActivationInterval
= 1h</p>
details. The default is 2 hours. Example:
ActivationInterval&nbsp;=&nbsp;1h</p>
<p style="margin-left:11%;"><b>RenewalInterval</b></p>

BIN
man/vlmcsd.ini.5.pdf
View File

Binary file not shown.

40
man/vlmcsd.ini.5.unix.txt
View File

@ -243,6 +243,46 @@ KEYWORDS
csd(8).
MaintainClients
Can be TRUE or FALSE (the default). Disables (FALSE) or enables
(TRUE) maintaining a list of client machine IDs (CMIDs). TRUE is
useful to prevent emulator detection. By maintaing a CMID list,
vlmcsd(8) reports current active clients exactly like a genuine
KMS emulator. This includes bug compatibility to the extent that
you can permanently kill a genuine KMS emulator by sending an
"overcharge request" with a required client count of 376 or more
and then request activation for 671 clients. vlmcsd(8) can be
reset from this condition by restarting it. If FALSE is used,
vlmcsd(8) reports current active clients as good as possible. If
no client sends an "overcharge request", it is not possible to
detect vlmcsd(8) as an emulator with MaintainClients = FALSE.
Maintaining clients requires the allocation of a buffer that is
about 50 kB in size. On hardware with few memory resources use
it only if you really need it.
If you start vlmcsd(8) from an internet superserver, this set‐
ting cannot be used. Since vlmcsd(8) exits after each activa‐
tion, it cannot maintain any state in memory.
StartEmpty
This setting is ignored if you do not also specify Maintain‐
Clients = TRUE. If you specify FALSE (the default), vlmcsd(8)
starts up as a fully "charged" KMS server. Clients activate
immediately. StartEmpty = TRUE lets you start up vlmcsd(8) with
an empty CMID list. Activation will start when the required min‐
imum clients (25 for Windows Client OSses, 5 for Windows Server
OSses and Office) have registered with the KMS server. As long
as the minimum client count has not been reached, clients end up
in HRESULT 0xC004F038 "The count reported by your Key Management
Service (KMS) is insufficient. Please contact your system admin‐
istrator". You may use vlmcs(1) or another KMS client emulator
to "charge" vlmcsd(8). Setting this parameter to TRUE does not
improve emulator detection prevention. It's primary purpose is
to help developers of KMS clients to test "charging" a KMS
server.
ActivationInterval
This is the same as specifying -A on the command line. See vlm‐
csd(8) for details. The default is 2 hours. Example: Activation‐

2
man/vlmcsdmulti.1.html
View File

@ -1,5 +1,5 @@
<!-- Creator : groff version 1.22.3 -->
<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
<!-- CreationDate: Tue Oct 25 06:23:57 2016 -->
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

BIN
man/vlmcsdmulti.1.pdf
View File

Binary file not shown.