Hi Everyone,

I got a Office 2010 packaging request, with activation. I have never done activation before this. If I check help>about, then it says, if we do not activate this copy then it would deactivate, license.
Please guide me with the preferred method of activating office 2010.
1. I tried to activate it online, but I am not able to capture settings.
2. I tried below command:-
cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.vbs" /act
1st doubt is, will this command activate office? or it will just hide pop-up?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Assuming you've used the OCT and a config.xml file during deployment, have you tried adding the following line to the config.xml:

<Setting Id="AUTO_ACTIVATE" Value="1" />

PJ
Answered 03/12/2012 by: pjgeutjens
Red Belt

Please log in to comment
0
I tried it in msp file. Waiting to complete installation.
Answered 03/12/2012 by: MadForMsi
Blue Belt

Please log in to comment
0
office 2010 does not use the mst as other msi do. you have to use the config.xml file as described by pj.

check the package kb for more details.
Answered 03/12/2012 by: kardock
Second Degree Green Belt

Please log in to comment
0
ya, you are right...I am not saying about mst or msi. I am saying msp, which we create through oct. Anyways it did not work through that. I am trying it in xml file now.
Answered 03/12/2012 by: MadForMsi
Blue Belt

Please log in to comment
0
Still it did not work...does it need internet working, at the time of installation?
Answered 03/12/2012 by: MadForMsi
Blue Belt

Please log in to comment
0
Still it did not work...does it need internet working, at the time of installation?

Depends on the type of key you're using. For MAK keys the answer is yes. If you're using KMS activation, only the KMS server needs access to the internet, the other machines need access to the KMS server. Also, when using KMS, there's a five host minimum activation count needed before further hosts are able to automatically activate their licenses.

Also see: http://technet.microsoft.com/en-us/library/ee624358.aspx

Kr,
PJ
Answered 03/12/2012 by: pjgeutjens
Red Belt

Please log in to comment
0
sorry. that was my early monday morning eyes. i really saw mst.

haha!
Answered 03/12/2012 by: kardock
Second Degree Green Belt

Please log in to comment
0
I did not do this myself but I think my colleague had to run the OSPP.vbs in two steps first add the license and the activate. For some reason it did not accept the license when added with OCT, and therefore he added it with the script instead. This was when using a MAK license.

You should verify that the license is actually added after install, if not you might need to run the script in two steps aswell.
http://technet.microsoft.com/en-us/library/ee624350.aspx
Answered 03/13/2012 by: henrik80
Second Degree Blue Belt

Please log in to comment
0
Has anyone managed a successful SCCM deploy of any Office 2010 products that use MAK (not KMS) licensing? I haven't been able to get it to work so far. I started this almost a year ago, working with Project 2010, but then the effort got tabled until just recently, so I'm picking it up again. All my efforts so far have failed.

Here's my scenario: need to install Project 2010 (will eventually need packages for both Standard and Professional versions) via SCCM. Most PCs are running Windows XP Service Pack 3 (x86), but some are Windows 7 PCs (x64). All have Microsoft Office 2007 installed. Most users do not have administrative rights.

I've tried a number of things to prevent the Activation Wizard dialog from appearing, but so far, nothing but a string of failures.

I've tried adding AUTO_ACTIVATE (Value=1) to the config.xml file.
I've tried adding AUTO_ACTIVATE to the MSP, using the Office Customization tool.
I've tried adding %windir%\system32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /act into the MSP and setting it to run post-install.
I've tried writing the install into one exe (using Wise script), then triggering OSPP.VBS with a separate exe that I run post-reboot when the next user logs in.

I'm running the SCCM installation to install only when no user is logged on, since we have non-admin users. But if the PC isn't connected to the Internet at the time of Project installing, that seems to be the critical piece that prevents any attempt to automate the program activation.

I'm out of ideas at this point and hope someone can give me something new to try. Thanks.
Answered 03/14/2012 by: RonW
Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity