Microsoft Webcam 2 ユーザーズマニュアル
Volume Activation 2.0 Operations Guide
6
Issue
Resolution
12289.
Check this event for the following:
Check this event for the following:
•
Is the result code 0? Anything else is an error.
•
Is the KMS host name in the event correct?
•
Is the KMS port correct?
•
Is the KMS host accessible?
•
If the client is running a third-party firewall, do you need
to configure the outbound port?
to configure the outbound port?
On the KMS host, look in the KMS event log for event 12290.
Check this event for the following:
•
Did the KMS host log a request from the client computer?
Verify that the name of the KMS client is listed. Verify
that the client and KMS host can communicate. Did the
client receive the response? Ensure that routers do not
block traffic using TCP port 1688, if you are using the
default port, and that stateful traffic to the KMS client is
allowed.
Verify that the name of the KMS client is listed. Verify
that the client and KMS host can communicate. Did the
client receive the response? Ensure that routers do not
block traffic using TCP port 1688, if you are using the
default port, and that stateful traffic to the KMS client is
allowed.
•
If no event is logged from the KMS client, the request did
not reach the KMS host or the KMS host was unable to
process it.
not reach the KMS host or the KMS host was unable to
process it.
What does this
error code mean?
error code mean?
If Slmgr.vbs returns a hexadecimal error code, or event 12288
contains a result code other than 0, determine the
corresponding error message by running the following
command:
contains a result code other than 0, determine the
corresponding error message by running the following
command:
Slui.exe 0x2a ErrorCode
Clients are not
adding to the
KMS count.
adding to the
KMS count.
You need to run
sysprep /generalize
or
slmgr /rearm
to
reset the client computer ID (CMID) and other product
activation information. Otherwise, each client computer looks
identical and the KMS host does not count them as separate
KMS clients.
activation information. Otherwise, each client computer looks
identical and the KMS host does not count them as separate
KMS clients.
KMS hosts are
unable to create
SRV records on a
non-Microsoft
DNS server.
unable to create
SRV records on a
non-Microsoft
DNS server.
Your DNS may restrict write access, or may not support
dynamic DNS (DDNS). In this case, you need to give the KMS
host write access to the DNS database or create the SRV record
manually. For more information about this, see the Volume
Activation 2.0 Deployment Guide.
dynamic DNS (DDNS). In this case, you need to give the KMS
host write access to the DNS database or create the SRV record
manually. For more information about this, see the Volume
Activation 2.0 Deployment Guide.
Only the first
KMS host is able
to create SRV
records on a
Microsoft DNS
server.
KMS host is able
to create SRV
records on a
Microsoft DNS
server.
If you have more than one KMS host, the other hosts are not
able to update the SRV record unless the SRV default
permissions are changed. See. For more information about this,
see the Volume Activation 2.0 Deployment Guide.
able to update the SRV record unless the SRV default
permissions are changed. See. For more information about this,
see the Volume Activation 2.0 Deployment Guide.
I installed a KMS
key on the KMS
key on the KMS
KMS keys should only be installed on KMS hosts and should not
be installed on KMS clients. Run
be installed on KMS clients. Run
slmgr.vbs -ipk <SetupKey>.