[ms office - 2010] Office auto activation behind cachepilot proxy

[Admiral208]

Hi folks,

 

Im trying to deploy Office 2010 to out to our teachers workstations. I have followed the method of using the Microsoft script and deploying via group policy at computer start up. I have created the admin install file and it all works perfectly except the automatic activation. I have read that I can enter AUTO_ACTIVATE=1 in the OCT to achieve this but it doesnt work at startup.

 

We use a cachepilot box as our proxy and this requires authentication.

 

How would the computer get its proxy settings to auto activate before a user logs in??

 

Has anyone got this to work? I want to roll it our over night and would like for the users to not have to do anything when they come in, like activate office over the net.

 

Thanks

James

[jamesreedersmith]

Have a look at VAMT - Volume activatio management tool -allows you to remotely deploy and manage licenses and activate them remotely too!

[Admiral208]

the clients are XP, does this matter?

[jamesreedersmith]

No - should work - will onyl be able to manage the office licenses not the XP ones.

[Admiral208]

Ok thanks,

 

Ill use that for now but is this problem actually solvable?

 

Can a computer connect to the internet via a proxy server before a user logs on to automatically activate?

[pete]

Install the office 2010 keys on your KMS host.

 

Download Details - Microsoft Download Center - Office 2010 KMS Host License Pack

 

Volume Activation Deployment Guide

[Admiral208]

Im not using a kms host

 

there are only going to be about 40 deployments. As mentioned above, I can use the VAMT to activate them, I want to know if its possible to activate them automatically at computer start up when the product gets installed.

 

If i run the script with a user logged in, it works. I can install the product and have it auto activate. I just cant do it at startup.

[tumbleweed]

have a look at the proxycfg command - was often needed to get automatic updates to work.

[browolf]

proxy is a user setting in group policy that applies when a user logs on. Obviously this happens after software deployment. A possibility which may or may not work for you is use loopback processing to apply user settings when computer settings are applied. There's a merge option that splices user settings into the computer settings. The only issue is what order will it do things in. I don't know. It's still no good if it applies the user settings after the computer settings before logon.

 

another option is to use a special login, that installs the software with msiexec in a login script and then logs off afterwards. In this instance user settings have applied when the login script has run.

[ricki]

have a look at the proxycfg command - was often needed to get automatic updates to work.

 

Hi I think its proxycfg -u for windows xp off the top of my head.

 

Richard

[ricki]

Hi

 

What I did was in the script for the install. I got the script to insert the registry key for the lancs proxy and then after the activation it swapped back with another registry key inserted.

 

Richard