Help! Office 2010 Pro Plus MAK Auto-Activation on both 32bit and 64bits Windows
-
martedì 21 febbraio 2012 22:47
Hi,
I am creating a customization file to deploy Office 2010 Pro Plus (32bits) with MAK key to all users running both 32bits and 64bits Windows...
I have configured everything and the customization file is working great and I know the methods to activate the Office after the installation. That is to run the script file to call for OSPP.VBS /act. I have created a batch file to call for this script:
C:\WINDOWS\system32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /act
However, this script only works for 32bits Windows. To activate it in 64bits Windows, the path has to be
C:\WINDOWS\system32\cscript.exe "C:\Program Files x86\Microsoft Office\Office14\OSPP.VBS" /act
Can I include both lines in 1 batch file? or do I have to create a seperate customization file? I am hoping that I can combine both lines in one to make it easier for deployment and end-users.
What are the other methods to work around this issue?
If I configure by adding to OCT these lines (see below), will it work on both versions of Windows? please help, thanks!
TARGET: [WindowsFolder]\system32\cscript [INSTALLLOCATION]\OSPP.VBS
ARGUMENT: /act
A@RJC
- Modificato ARJC mercoledì 22 febbraio 2012 01:17
Tutte le risposte
-
mercoledì 22 febbraio 2012 11:42
Hi, have you tried the setup property AUTO_ACTIVATE ?
http://technet.microsoft.com/en-us/library/cc179195.aspx#ConfigxmlElementReference
(scroll down to the "Setting element" section of this page)Note that you can also set the AUTO_ACTIVATE property value by using the Office Customization Tool. To do this, follow these steps:
- In the OCT, select
Modify Setup properties on the left pane, and then click
Add in the right pane.
- In the
Add Property Value dialog box, in the Name box, type
AUTO_ACTIVATE. Note that property names must be uppercase.
- In the
Value box, type 1, and then click OK.
You could alternatively try using the environment variable %ProgramFiles% in your batch file.
This article may help with the syntax:
http://social.technet.microsoft.com/Forums/en/winserverTS/thread/b808c7a9-8de2-454c-8eee-595712fc10abNote that the TN Library content states that when chaining commands you should use fully qualified paths, so (not tested) but I don't think you can use [WindowsFolder] nor [INSTALLLOCATION} as part of your "Target":
http://technet.microsoft.com/en-us/library/cc179200
"For Target, enter the fully qualified path of the executable file that you want to run "
Don
- Modificato Don - tesgroupMicrosoft Community Contributor mercoledì 22 febbraio 2012 11:49
- In the OCT, select
Modify Setup properties on the left pane, and then click
Add in the right pane.
-
mercoledì 22 febbraio 2012 17:06
I did actually, but it didn't work!
About using the environment variable, yes, I was looking into it, and just about finishing the script in my batch file. I will post it up after I test and confirm it.
Thank you Don for the info on the Target path... that's a good info!
A@RJC
-
mercoledì 22 febbraio 2012 23:04
As promised, I am back with the batch file scripts for my own question!
Here you go:
Open you notepad and paste the following code & save it as [whateveryoucallit].bat. This will auto-activate your Office 2010 Pro Plus (32bits) on both 32bits and 64 bits system. AUTO_ACTIVATE with value key 1 doesn't work that well, that's why batch file is my resolution to this problem.
*Save you batch file under UPDATES folder, and call for it post-installation using OCT.
@echo off & setLocal enabledelayedexpansion
if exist "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" (
set PPATH="C:\Program Files\"
) else (
set PPATH="C:\Program Files (x86)\"
)
start "" C:\WINDOWS\system32\cscript.exe %PPATH%"Microsoft Office\Office14\OSPP.VBS" /act-----------------------------------------------------------------------------------------------------------------
Although I have got this problem solved by myself and for myself, I am now running into other problems with ERROR1406 (permission problem) and previous version of Office wasn't uninstalled correctly and corrupted error (happens on certain workstation not all).. I am going to post this issue on another thread. Please follow me on another thread if you have the answer http://social.technet.microsoft.com/Forums/en-US/officesetupdeploy/thread/e8b4ccad-109d-4c2a-ab7a-41b50bd55244. Thanks!
A@RJC
.png)
