I'm in the process of creating a script to activate office 2013, i already have a script for office 2010 so i created a duplicate and was just going to edit tweak that one. i have run into a standstil on how to set it up so i can enter a Activation Key then update it as the keys update. i can answer any question you need to better explain my question.

The 2010 Script looks like this.

cd windows\system32
cscript "%ProgramFiles%\Microsoft Office\Office14\ospp.vbs" /act

it looks like it is setup to activate without a given key. so i would like to make a script that uses a key

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



these are for 32bit office on 32bit and 64 bit machines.

64bit machine:

"C:\Program Files (x86)\Microsoft Office\Office15\ospprearm.exe"

cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act

32bit machine:

"C:\Program Files\Microsoft Office\Office15\ospprearm.exe"

cscript "c:\program files\microsoft office\office15\ospp.vbs" /act

Answered 04/17/2014 by: SMal.tmcc
Red Belt

  • we use kms also but due to sysprep office gets messed up sometimes. I place these lines in my post script to be sure office is activated to the KMS server

    here is my post k2000 bat for a 64bit machine running 32 bit office with kms activation for both.

    net start w32time

    start /wait %SystemRoot%\system32\w32tm /config /update /manualpeerlist:ntp.tmcc.edu /syncfromflags:manual

    Start /wait net user administrator password
    Start /wait net user dfault password
    start /wait net localgroup administrators dfault /add

    start /wait cscript %SystemRoot%\System32\slmgr.vbs -ATO

    reg.exe DELETE HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /f

    "C:\Program Files (x86)\Microsoft Office\Office15\ospprearm.exe"

    cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act

    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoAdminLogon /d 1 /f
    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v AutoLogonCount /t REG_DWORD /d 1 /f
    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultUserName /d Administrator /f
    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultPassWord /d password /f
    start /wait reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon" /v DefaultDomainName /f

    del C:\Users\default\AppData\Local\Microsoft\Windows\WebCache\*.* /s /q

    start /wait reg.exe add "HKLM\SYSTEM\CurrentControlSet\services\Tcpip\Parameters" /v SearchList /d "tmccadmn.tmcc.edu,tmcc.edu,tmccacad.tmcc.edu" /f

    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background" /v OEMBackground /t REG_DWORD /d 1 /f

    start /wait msiexec /qn /i "\\kbox\client_3\agent_provisioning\windows_platform\ampagent-5.5.30275-x86.msi" HOST=kbox.tmcc.edu

    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" /v ipv6kill /d "reg.exe add \"HKLM\SYSTEM\CurrentControlSet\services\Tcpip6\Parameters\" /v DisabledComponents /t REG_DWORD /d 4294967295 /f"

    start /wait reg.exe add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" /v iconcopy /d "xcopy c:\windows\w2d\links\*.* c:\users\administrator\desktop /q /y" /f
Please log in to comment

The command line to set the key is:

cscript "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /inpkey:<key goes here>

You need to run this before the ospp.vbs /act command.

We use KMS activation in our environment which makes activating Office much easier, since it will automatically activate after installation.

Answered 04/18/2014 by: chucksteel
Red Belt

  • we also use KMS that activates them after install. however i have a couple stragglers that had theirs manually installed so i was going to create a script to activate all at once.
    • You can run OSPP.VBS /dstatus to query the activation status. I have a custom inventory rule setup to query for Windows activation so that we can find systems that have lost their KMS activation so you could do the same thing for Office activation. If you aren't familiar with the Volume Activation Management Tool then I would recommend checking it out, too:
      It allows you to query computers and set their activation keys and activate remotely.
      • thank you very much, i will look into this right now. if i have more questions i know who to contact.
  • this is for office 2010 not 2013
    • The download page says it's for 2010 but it's working for 2013 as well.
      • only difference is the path
        ...\Office14\... for 2010
        ...\Office15\... for 2013
      • Oh right. I thought you were referring to the VAMT. Yes, the path needs to be for the correct version of Office.
Please log in to comment