Microsoft Project Standard 2010 - automating Program Activation
I have a package for Microsoft Project Standard 2010. We're installing this to a Windows XP SP3 environment; target PCs are 32-bit and have Office 2007 installed. We use a volume license key, not a KMS (Key Management Service) key.
After the app installs, each unique user that runs the app is presented with an Activation Wizard screen.
I'm trying to automate the Activation Wizard piece by adding the command line
This works if I do the install manually, but when I deploy using SCCM, the Activation Wizard screen appears for each user accessing Project.
I'm guessing the reason this is happening is because SCCM uses the System account, and that account doesn't have access to go through our proxy (the OSPP.VBS script, part of the Project install, creates an instance of Internet Explorer so the app can be activated).
Wondering if anyone has experienced a similar scenario and what they've done to resolve it.
After the app installs, each unique user that runs the app is presented with an Activation Wizard screen.
I'm trying to automate the Activation Wizard piece by adding the command line
%windir%\system32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /act
This works if I do the install manually, but when I deploy using SCCM, the Activation Wizard screen appears for each user accessing Project.
I'm guessing the reason this is happening is because SCCM uses the System account, and that account doesn't have access to go through our proxy (the OSPP.VBS script, part of the Project install, creates an instance of Internet Explorer so the app can be activated).
Wondering if anyone has experienced a similar scenario and what they've done to resolve it.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
dunnpy
13 years ago
Ron,
This was mentioned on the Office 2010 Webinar that Dell KACE/AppDeploy ran yesterday.
Believe it or not the public property below should active at install time:
AUTO_ACTIVATE=1
This link provides further details, when using MAK licence keys (which you are).
Hope that helps,
Dunnpy
This was mentioned on the Office 2010 Webinar that Dell KACE/AppDeploy ran yesterday.
Believe it or not the public property below should active at install time:
AUTO_ACTIVATE=1
This link provides further details, when using MAK licence keys (which you are).
Hope that helps,
Dunnpy
Posted by:
RonW
13 years ago
Hi, Paul. I noticed the AUTO_ACTIVATE code during the webinar yesterday and gave it a try earlier today, but no luck. Tried again after reading your response, this time adding a reg key change they mention just to see if that made any difference, but that didn't do the trick either.
This leads me more toward my suspicion that it has something to do with our proxy in some way. Need to talk to the network folks and one of the SCCM wizards here. Will post my findings.
This leads me more toward my suspicion that it has something to do with our proxy in some way. Need to talk to the network folks and one of the SCCM wizards here. Will post my findings.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.