Up until this week, I have been pushing O2K3 with SP1 out as part of our standard RIS build through Group Policy - no probs.

Last night, I updated the Admin installation point by applying the .msp files to it and then re-deployed O2K3 through the GP console. On rebooting a couple of computers, the re-installation appears to work fine - no errors, nothing. However, head on into one of the Office applications and it's still running SP1!!!!!!!

This to me makes no sense, as redeploying the app should make it re-read the MSI and the machines should then refer to the Admin installation point (which is the same) for the re-install. Does anyone know why this would happen??? New builds are getting O2K3 with SP2 fine.

0 Comments   [ - ] Hide Comments


Please log in to comment

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


OK - cause found.

For some reason, the application of the .msp files had not done it's job properly, despite not giving any error. After running through the process from scratch, this all worked hunky dory.

Answered 03/10/2006 by: dgdavis
Orange Belt

Please log in to comment