Office 2013 needs rearming through VBS script to activate through KMS server - VBS script provided from the link
Hi
We have 250 windows 7 PCs in our network, with office 2010 installed.
I wanted to introduce office 2013 into our network. I built a Window7 image and installed office 2013 and imaged 20 PCs with this same image. The office 2013 clients was not activating with our KMS server.
I came across the below article and I did not rearmed office 2013 before the deployment image was created. It says there are two ways to resolve this:
http://blogs.technet.com/b/office_resource_kit/archive/2013/06/05/why-isnt-kms-counting-activation-requests.aspx
1 - Create a new image but rearm office before saving the image
2- fix existing clients using a script
I want to do the second instruction, the instruction says “you can use this startup script on each computer to rearm Office and generate a new unique Office CMID”
Does this mean I have to go to Windows 7 PC(where office 2013 is installed) , Run-Gpedit.msc- Computer Configuration\Windows Settings\Scripts Startup –add this .VBS here and restart the PC?
Or can I copy the .VBS file to the desktop of ever PC and execute the script manually.
After restart do I need to remove the vbs script?
Any suggestions much appreciated.
Thanks
This is the script copied from the link above:
@echo off
:OSPP
reg query HKLM\Software\Microsoft\Of
if %errorlevel%==1 (goto RUN) else (goto END)
:RUN
set ProgramFilesPath=%ProgramF
"%ProgramFilesPath%\Common
C:\Windows\system32\cscrip
set ProgramFilesPath=%ProgramF
"%ProgramFilesPath%\Common
C:\Windows\system32\cscrip
REG ADD "HKLM\Software\Microsoft\O
:END
Exit
We have 250 windows 7 PCs in our network, with office 2010 installed.
I wanted to introduce office 2013 into our network. I built a Window7 image and installed office 2013 and imaged 20 PCs with this same image. The office 2013 clients was not activating with our KMS server.
I came across the below article and I did not rearmed office 2013 before the deployment image was created. It says there are two ways to resolve this:
http://blogs.technet.com/b/office_resource_kit/archive/2013/06/05/why-isnt-kms-counting-activation-requests.aspx
1 - Create a new image but rearm office before saving the image
2- fix existing clients using a script
I want to do the second instruction, the instruction says “you can use this startup script on each computer to rearm Office and generate a new unique Office CMID”
Does this mean I have to go to Windows 7 PC(where office 2013 is installed) , Run-Gpedit.msc- Computer Configuration\Windows Settings\Scripts Startup –add this .VBS here and restart the PC?
Or can I copy the .VBS file to the desktop of ever PC and execute the script manually.
After restart do I need to remove the vbs script?
Any suggestions much appreciated.
Thanks
This is the script copied from the link above:
@echo off
:OSPP
reg query HKLM\Software\Microsoft\Of
if %errorlevel%==1 (goto RUN) else (goto END)
:RUN
set ProgramFilesPath=%ProgramF
"%ProgramFilesPath%\Common
C:\Windows\system32\cscrip
set ProgramFilesPath=%ProgramF
"%ProgramFilesPath%\Common
C:\Windows\system32\cscrip
REG ADD "HKLM\Software\Microsoft\O
:END
Exit
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
( Total office 2013 PCs=20). I have 10 PCs joined into the domain and and remaining PCs are in imaged and needs to be joined to domain.
Firstly If i run through the domain level by creating a GPO, will this cause any problems to our existing office 2010 clients which are located on the same OU.
Secondly :Please see the steps below
On the DC GPMC.MSC- Create GPO under the OU where all the 20 workstations and remaining office 2010 workstations clients are located.
Computer configuration-Windows settings-Scripts( Startup scripts)- Place the .VBS script here.
Thanks