Office update, did it work?
From: Brendon Rogers (brendon.rogers_at_WMANN.COM)
Date: 09/15/04
- Previous message: Toby Beaumont: "Security bug in .NET Forms Authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 15 Sep 2004 21:54:20 +0100 To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
We run Windows 2000 Pro SP4, use RIS to deploy the OS and Group Policy to
deploy Office XP, Project 2002 and Visio 2002 from admin installation
points.
Given the announcement by MS I thought it would be prudent to get patching.
So I RIS'd two fresh machines - installation was identical except, in
addition to Office XP SP2 (yes we are behind a service pack), the second
machine had Visio Pro 2002 SP 2 and Project Std 2002 installed automatically
via Group Policy. The two machines use exactly the same source software so
there could be no discrepancies there.
Before I dived into MBSA, WU, OfficeUpdate etc I thought I would just check
the Office versions, you know - Help, About Microsoft (Word) (Excel) etc.
Well I was quite surprised and confused.
PC1
Word
(10.5522.4219) SP2
Excel
(10.4524.4219) SP2
Outlook
(10.4712.4219) SP2
PowerPoint
(10.4205.4219) SP2
PC2
Word
(10.5522.6626) SP3
Excel
(10.4524.6626) SP3
Outlook
(10.4712.6626) SP3
PowerPoint
(10.4205.6626) SP3
So one PC had Office XP reporting itself as SP2 and the other as SP3. Since
the only difference between the 2 machines was Visio and Project, I reasoned
one of these must be the culprits. So I put PC1 into a W2K group which
resulted in Group Policy installing Visio 2002 SP2 (10.0.5110) at reboot and
sure enough PC1 also reports itself as Office XP SP3. And just to be sure I
wasn't going mad, I re-RIS'd both PCs again and achieved exactly the same
results.
I look forward to more confusing reports from MBSA and OfficeUpdate....
Regards
Brendon
-----Original Message-----
[snipped].
6. Office should be patched via OfficeUpdate. I'd appreciate hearing from
people who have been there (and not just WU). Did it work, didn't it, etc...
Cheers,
Russ - NTBugtraq Editor
-----
NTBugtraq Editor's Note:
Want to reply to the person who sent this message? This list is configured
such that just hitting reply is going to result in the message coming to the
list, not to the individual who sent the message. This was done to help
reduce the number of Out of Office messages posters received. So if you want
to send a reply just to the poster, you'll have to copy their email address
out of the message and place it in your TO: field.
-----
-----------------------------------------------------------------------
This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please contact the sender as soon as possible and delete this message and any attachment from your system. If you are not the intended recipient you must not copy this message or attachment or disclose the contents to any other person. When addressed to our clients any opinions or advice contained in this message and any attachments are subject to any applicable Whitehead Mann terms of business or client engagement letters.
-----
NTBugtraq Editor's Note:
Want to reply to the person who sent this message? This list is configured such that just hitting reply is going to result in the message coming to the list, not to the individual who sent the message. This was done to help reduce the number of Out of Office messages posters received. So if you want to send a reply just to the poster, you'll have to copy their email address out of the message and place it in your TO: field.
-----
- Previous message: Toby Beaumont: "Security bug in .NET Forms Authentication"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
