Re: Security Update for Microsoft Word 2003

Shaun Pond

unread,

Feb 9, 2010, 3:54:29 AM2/9/10

to

Shandi,

not deploying to? Or deploying and failing? Or deploying and still
showing as vulnerable?

--

Shaun Pond

unread,

Feb 10, 2010, 11:33:01 PM2/10/10

to

Shandi,

lookat the deployments for the device, find the deployment where you
deployed the patch, check the status?

--

Shaun Pond

unread,

Feb 17, 2010, 11:47:10 PM2/17/10

to

Shandi,

OK, it's important to get the terminology right, because we need to
look in different places for something that's not deploying vs
something that's deploying but still showing as vulnerable :)

I have to wait to get an answer for you, my PDK license just expired...
:(

--

Shaun Pond

unread,

Feb 18, 2010, 9:27:04 AM2/18/10

to

Shandi,

to be patched, it needs:
Mswrd832.cnv with the version (not file version) >= 2003.1100.8313 with
a modification date of >= August 3 2009 in the directory Microsoft
Shared\TextConv found under the path described in
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion,CommonFilesDir
and
Msconv97.dll with the version (not file version) >= 2003.1100.8202 and
a modification date of >= 17 november 2007 in the same location

--

Shaun Pond

unread,

Feb 21, 2010, 5:06:18 AM2/21/10

to

Shandi,

> PDK?
>
Patch Developer's Kit - it enables me to see what's inside the
vulnerability

--

Shaun Pond

unread,

Feb 21, 2010, 5:07:22 AM2/21/10

to

Shandi,

hmm... I was looking at http://support.microsoft.com/kb/975539 - do
these machines have the full Office 2003, or a mixture of versions?

--

Shaun Pond

unread,

Feb 23, 2010, 7:41:27 AM2/23/10

to

Shandi,

did you look at the "known issues" section?

--

Shaun Pond