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   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity