/build/static/layout/Breadcrumb_cap_w.png

Office 2003 SP2

I'm sorry this may come off as a bit confusing but this is my first go at this. I have several workstations which I wish to deploy Office 2003 SP2 which already have the local installs on the drives via a Ghosted image I created. All the workstations are in a AD Domain, so from what I understand, according to the whitepapers from M$ I should take advantage of the local install using the OHotFix.exe tool, editing the .ini file. Although, I'm not sure the easiest way to roll out the patch. (I have the .msp files already extracted and ready to go) Some say creating a scheduled task, but that seemed stupid, as I want this to be as automated as possible. So anyone who has done this, or something close I would appreciate the help. I could use GP, but that kind of cirumvents the whole local install thing. Maybe my brain is just running too much. I'm not really good at scripting, but i guess that is also another alternative.

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

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

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ