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\Office\15.0\Common\OSPPREARM
if %errorlevel%==1 (goto RUN) else (goto END)
 
:RUN
set ProgramFilesPath=%ProgramFiles%
"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"
C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office15\ospp.vbs" /act
set ProgramFilesPath=%ProgramFiles(x86)%
"%ProgramFilesPath%\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\OSPPREARM.EXE"
C:\Windows\system32\cscript.exe "%ProgramFilesPath%\Microsoft Office\Office15\ospp.vbs" /act
REG ADD "HKLM\Software\Microsoft\Office\15.0\Common\OSPPREARM"
 
:END
Exit
lianne143Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Neil RussellTechnical Development LeadCommented:
I assume this is on a DOMAIN?
Use a group policy to run the script created at the domain level NOT on each local pc.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lianne143Author Commented:
This is a domain.
( 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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VB Script

From novice to tech pro — start learning today.