Office2003 SP2
Hi All,
I have been asked by our client to incorporate the Office2003 SP2 into our current packages of Office2003. The Office2003 SP2 is a file called "Office2003SP2-KB887616-FullFile-ENU.exe" which is 104 MB in size. They are suggesting we add this into an existing MST to ensure ease of use for deployment. Because of the size and also when I extract from this exe I get 3 MSP's I am very reluctant to even try going down this route. Has anyone else had the pleasure of trying to incorporate this into a previous package or what solution did you arrive at? I am thinking of creating a new package altogether. Thanks
I have been asked by our client to incorporate the Office2003 SP2 into our current packages of Office2003. The Office2003 SP2 is a file called "Office2003SP2-KB887616-FullFile-ENU.exe" which is 104 MB in size. They are suggesting we add this into an existing MST to ensure ease of use for deployment. Because of the size and also when I extract from this exe I get 3 MSP's I am very reluctant to even try going down this route. Has anyone else had the pleasure of trying to incorporate this into a previous package or what solution did you arrive at? I am thinking of creating a new package altogether. Thanks
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
fosteky
16 years ago
I recommend making a different package from the existing one (assuming the existing one is deployed), make a new administrative installation point, then run the patches against that AIP, then use the O2k3 ORK to make your transform, then use the resulting MST/MSI and deploy it as an upgrade to existing wkstns with O2k3 on it.
Posted by:
nheim
16 years ago
Hi oreillyr,
this widely depends on the deployment solution you have.
This exe mainly consists of a installer patch file (MSP), which could applied directly to the clients.
However, as fostkey already stated, the common solution would be, to make a new AIP and apply this patch there. That's all you need to do.
But the easiest approach would be to stream it down to the existing clients through Windows Update.
Regards, Nick
this widely depends on the deployment solution you have.
This exe mainly consists of a installer patch file (MSP), which could applied directly to the clients.
However, as fostkey already stated, the common solution would be, to make a new AIP and apply this patch there. That's all you need to do.
But the easiest approach would be to stream it down to the existing clients through Windows Update.
Regards, Nick
Posted by:
oreillyr
16 years ago
I wont even begin to tell you what the deployment method is! I have merged the MSP and the original using a new AIP as suggested and all seems to be well. I can still keep the original MST also. Thanks for your help.
Deployment involves dragging a server around to each desk![:D]
Deployment involves dragging a server around to each desk![:D]
Posted by:
spartacus
16 years ago
ORIGINAL: oreillyr
I wont even begin to tell you what the deployment method is!
Deployment involves dragging a server around to each desk![:D]
ahhh, couldn't resist telling us after all then ? - you have my sympathy [:)]
Regards,
Spartacus
Posted by:
jmcfadyen
16 years ago
hmm there is also ohotfix which is designed to cater for this type of deployment.
a new AIP requires that you deploy the entire app again resulting in a considerable network overhead.
ohotifx will just deploy the delta's of the current. both methods work one may be more suitable to you thanthe other.
a new AIP requires that you deploy the entire app again resulting in a considerable network overhead.
ohotifx will just deploy the delta's of the current. both methods work one may be more suitable to you thanthe other.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.