Office 2013 pro plus (KMS) not active after a Kace 1000 inplace upgrade from windows 7 to 10.
After doing a In place windows 10 upgrade that I pushed via k100 which is working fine, office 2013 sp1 is no longer active(PRO PLUS 64 BIt MSI Install). I assume it has to do with KMS and windows 10.
Windows does activate via the KMS, but office 2013 does not. prior to the inplace upgrade, under windows 7 office 2013 was active.
Any ideas if it KMS or something else?
Anyone dealing with this issue before have a solution?
Should I contact MS support, as I tried to google for a solution and yet to find one.
I also tried stop and restarting the software protection and activation service but office is still not active.
Windows does activate via the KMS, but office 2013 does not. prior to the inplace upgrade, under windows 7 office 2013 was active.
Any ideas if it KMS or something else?
Anyone dealing with this issue before have a solution?
Should I contact MS support, as I tried to google for a solution and yet to find one.
I also tried stop and restarting the software protection and activation service but office is still not active.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
SMal.tmcc
8 years ago
run a post bat
"C:\Program Files (x86)\Microsoft Office\Office15\ospprearm.exe"
cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act
Comments:
-
you can push this via a k2 post script or a k1 kscript - SMal.tmcc 8 years ago
-
I tried this "C:\Program Files (x86)\Microsoft Office\Office15\ospprearm.exe"
cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act
and I got the following
c:\Program Files\Microsoft Office>"C:\Program Files\Microsoft Office\Office15\OSPPREARM.EXE" cscript "c:\program files (x86)\microsoft office\office15\ospp.vbs" /act
Error: Invalid SKUID specified. Example format: {00000000-0000-0000-0000-000000000000}
And when I tried it by it self the last commands
c:\Program Files\Microsoft Office>cscript "c:\program files\microsoft office\office15\ospp.vbs" /act
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
---------------------------------------
<No installed product keys detected>
---------------------------------------
---------------------------------------
---Exiting-----------------------------
I got this.
It was working fine prior to the windows 10 inplace upgrade in 7. - itadder 8 years ago-
sounds like you need to give it a serial number,
/inpkey:value
https://www.google.com/search?q=osopp&ie=utf-8&oe=utf-8#q=ospp.vbs+switches - SMal.tmcc 8 years ago
Posted by:
Bilo111
8 years ago
Hello, i have the problems to.
We Upgrade about 500 Clients from Win7 to Win10 with kace K2000. No Problems with that.
All have this Office 2013 problem.
After upgrading the machine the user logged in and open a Microsoft Office programm.
In the first Use it install something and need Admin Credentials. So we must
remotly logged in and must activate it.
Has anybody a idea how to integrate that in the K2000 so they activate it after upgrading ?
