Does anyone know of a script that I could add to my post installation scripts that will acticate office without prompting. Currently my system has a MAK when deployed but it does not activate so we have to do it in post op. I would like it to do so with out having to prompt.  Any help would be awesome.

Thanks

Answer Summary:
start /wait cscript "c:\program files (x86)\microsoft office\office14\ospp.vbs" /Inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx start /wait cscript "c:\program files (x86)\microsoft office\office14\ospp.vbs" /act
Cancel
1 Comment   [ + ] Show Comment

Comments

  • Are you using the Office Customization Tool to install MS Office in your post install task?
Please log in to comment

Community Chosen Answer

4

for 32 bit office on a 32 bit machine

2010 KMS

"C:\Program Files\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\ospprearm.exe"

start /wait cscript "c:\program files\microsoft office\office14\ospp.vbs" /act

for 2010 MAK

start /wait cscript "c:\program files\microsoft office\office14\ospp.vbs"  /Inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

start /wait cscript "c:\program files\microsoft office\office14\ospp.vbs" /act

Answered 06/04/2013 by: SMal.tmcc
Red Belt

  • when you upgrade to 2013 it will be
    for KMS 32 office on a 64bit machine

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

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

    for MAK 32 office on a 64bit machine

    start /wait cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /Inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

    start /wait cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act
  • Excellent scripts. Thank you for sharing!
  • What if I am installing 32 bit on a 64 bit machine?
    • use c:\program files (x86)\... instead of c:\program files\... like in the 2013 example
      • This content is currently hidden from public view.
        Reason: Removed by member request
        For more information, visit our FAQ's.
      • start /wait cscript "c:\program files (x86)\microsoft office\office14\ospp.vbs" /Inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

        start /wait cscript "c:\program files (x86)\microsoft office\office14\ospp.vbs" /act
  • Script worked Awesome. Thank you
Please log in to comment

Answers

0

I would head on out over to our KKE recording site and watch a few sessions on 2010 deployment.  They will go over using the Office Customization Tool (OCT) which allows you to build in the MAK key into your deployments.

http://www.kace.com/support/resources/kb/article/kace-kontinuing-education-k1000-and-k2000-recordings

Answered 06/04/2013 by: andrew_lubchansky
Black Belt

  • I build my masters with KMS license's. The only difference in the laptop vs the desktop deployment is some post script commands to change the windows 7 and office 2013 to MAK license's. I can use the same image file for both.

    For the desktops I have these 3 lines in my post scripts to insure windows and office are KMS activated during post imaging

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

    "C:\Program Files (x86)\Microsoft Office\Office15\ospprearm.exe"
    cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act

    For the laptops I use these lines to switch it over to MAK key so they can go off campus for extended periods of time.

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

    start /wait cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /Inpkey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
    start /wait cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act
Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja

Share