R
Ronald Nissley
All,
Before it was decommissioned, I relied on Office Update to check for Office
updates, then manually patched an Office 2003 administrative installation
point using the full-file updates. Delivering updates to network clients is
then a simple matter of Redeploying Office via group policy. For the recent
volley of Office updates, I used Microsoft Update. After patching the
administrative installation point as usual, redeploying Office and confirming
that redeployment was successful (Application event log and Office file
versions on client), Microsoft Update still detects the most recent Office
updates as needed! KB903775 (http://support.microsoft.com/kb/903775) looks
interesting, but we have _only_ per-computer Office installations and we
don't use WSUS for Office updates.
Any ideas? Detected updates could simply be ignored if already installed,
but it would be better if Microsoft Update would correctly detect needed
updates.
Thank you,
Ronald Nissley
Before it was decommissioned, I relied on Office Update to check for Office
updates, then manually patched an Office 2003 administrative installation
point using the full-file updates. Delivering updates to network clients is
then a simple matter of Redeploying Office via group policy. For the recent
volley of Office updates, I used Microsoft Update. After patching the
administrative installation point as usual, redeploying Office and confirming
that redeployment was successful (Application event log and Office file
versions on client), Microsoft Update still detects the most recent Office
updates as needed! KB903775 (http://support.microsoft.com/kb/903775) looks
interesting, but we have _only_ per-computer Office installations and we
don't use WSUS for Office updates.
Any ideas? Detected updates could simply be ignored if already installed,
but it would be better if Microsoft Update would correctly detect needed
updates.
Thank you,
Ronald Nissley