BrokeBerry

Attack Computer Wiz

A Security & Technology Weblog

Open an elevated Command Prompt and type the appropriate lines for your need.

Replace FQDN with the Fully Qualified Domain Name of your KMS server:


Windows 7, Windows 8, Windows 8.1, Server 2008/2008R2 and Server 2012/2012R2:

    
    
  1. CD \Windows\System32 
  2. cscript slmgr.vbs /skms FQDN 
  3. cscript slmgr.vbs /ato 

Office 2010 32 bit

    
    
  1. CD \Program Files (x86)\Microsoft Office\Office14 
  2. cscript ospp.vbs /sethst:FQDN 
  3. cscript ospp.vbs /act 
Office 2010 64 bit

    
    
  1. CD \Program Files\Microsoft Office\Office14 
  2. cscript ospp.vbs /sethst:FQDN 
  3. cscript ospp.vbs /act 
Office 2013 32 bit

    
    
  1. CD \Program Files (x86)\Microsoft Office\Office15 
  2. cscript ospp.vbs /sethst:FQDN 
  3. cscript ospp.vbs /act 

Office 2013 64 bit

    
    
  1. CD \Program Files\Microsoft Office\Office15 
  2. cscript ospp.vbs /sethst:FQDN 
  3. cscript ospp.vbs /act
If your product is still not activating, you may have KMS configuration issues. A good place to start looking for problems is to run the below command on the same machine that you ran the above commands. This will tell you when and what KMS server your client is trying to activate.

    
    
  1. cscript ospp.vbs /dhistoryacterr

user Posted by John "Mike" Wright

| More

0 comments

Post a Comment