How to Manually Activate Microsoft Office 2010/2013

The following commands should be done from a command prompt using Elevated Permissions. 

First, find out the address of the Key Management Server (KMS) using DNS replacing the example ".domain.com" with the proper domain for your workstation and environment.

I am using "dig" instead of "nslookup" because it is what I am most familiar with. If using "nslookup" go into interactive mode and change the query type to SRV before searching.

c:\>dig SRV _vlmcs._tcp.domain.com

For example, if your Company Domain is "acme.com", the command would be:

c:\>dig SRV _vlmcs._tcp.acme.com

Next, change to the MS Office 2010 directory. On Windows 7 x64 it is:

c:\>cd "\program files (x86)\Microsoft Office\Office14"

Office 2013 may be in directory Office15:

c:\>cd "\program files (x86)\Microsoft Office\Office15"

Display the current activation status

cscript ospp.vbs /dstatus

Next, set the default server to be used where "lic_server.domain.com" is the one discovered using the DNS lookup above.

cscript ospp.vbs /sethst:lic_server.domain.com

For example, if your company domain is "acme.com" and the license server hostname is "mslicenseserver01" the command should be:

cscript ospp.vbs /sethst:mslicenseserver01.acme.com

Activate Office

cscript ospp.vbs /act

How to Manually Activate Windows 7 Enterprise

How to Manually Activate Windows 7 Enterprise against a domain License Server

How to find the address of KMS servers

dig SRV _VLMCS._tcp.yourdomain.com

The correct sequence of events for converting a MAK activation back over to a KMS client is as follows:

• Open an elevated command prompt.
• Run this command : slmgr.vbs /ipk "win7KmsKey", where win7KmsKey comes from the appropriate value in this table.
• Run this command: slmgr.vbs /ato

Now, for the above to work automatically, the machines need to be able to resolve _vlmcs._tcp.yourdomain.com. There's a number of ways this can be achieved:

• For domain-joined machines, this should work by default (so long as it's joined to the same domain, of course)
• For non domain-joined machines, you can either set the computer's primary DNS suffix (in with the change computer name settings), or
• Specify a DNS suffix search order via the DNS tab in the network adapter's properties or via local group policy.

If you do not intend or have the ability to use the automatic discovery, you can use the following commands to manually configure where the client initially looks:

• slmgr.vbs /skms kmsServer.yourdomain.com:1688 (you could use the IP address instead of the hostname if you have no DNS resolution occurring at all)
• slmgr.vbs /ato