| T O P I C R E V I E W |
| DennisMCSE |
Posted - 09/07/2011 : 11:01:52 AM
Need to set up a manufacturing server with Windows Server 2008 R2 x64, but it won't be in our corporate AD. Normally, to activate the OS to the KMS server, all the information comes from the domain, which the new server won't be part of. Is there a way to activate a non-AD win2008 R2 server to the KMS server in AD? Until I figure it out, we'll have to operate in non-licensed mode for a bit. The server won't have external access to the Internet.
|
| 6 L A T E S T R E P L I E S (Newest First) |
| DennisMCSE |
Posted - 09/08/2011 : 6:13:00 PM
So it does look like as long as the DNS seeting on the client are correct and the SVR records of the KMS server are in DNS, the client registers right away. I didn't have to do anything else and as soon as I booted the server on the network, the Server activated the license and is registered on the KMS server. So it seems to work for domain clients as well as standalone clients. Cool.
|
| Jazzy |
Posted - 09/07/2011 : 4:43:29 PM
In that case I would go for the DNS option. |
| DennisMCSE |
Posted - 09/07/2011 : 4:10:17 PM
OK, just talked with our Central IT group. And showed him the cscript from the "Volume Activation 2.0 Deployment Guide.doc". He said that's for a single server manual KMS, but we have KMS failover servers in our environment that won't be recognized by the standalone server:
"Our standard for activation is to use SRV records, which is used automatically based on domain membership. Not sure that you can specify that kind of activation with a standalone machine. We can specify a single KMS server, but we won't have KMS failover, and if the KMS server is changed in the future you could run into some issues."
|
| NMDANGE |
Posted - 09/07/2011 : 2:13:36 PM
You can also assign the KMS host manually on the client by running "cscript slmgr.vbs /skms kmshost.domain.com" |
| DennisMCSE |
Posted - 09/07/2011 : 1:27:00 PM
Thanks. So just need to make sure the domain suffix is listed in the client settings and that the KMS DNS entries are listed on the DNS Server. If that's all, then we should be good to go.
|
| Jazzy |
Posted - 09/07/2011 : 11:09:56 AM
http://kb.ucla.edu/articles/kms-activation-for-non-domain-clients |
