Word 2003 always asks to save the normal.dot since Acrobat 9 was installed

Question

Hello,
Until Acrobat 9 Standard was installed on the 5000 PCs of our company, the following issue never occured.
As soon as Acrobat 9 Standard was installed, our users started to complain of messages asking them to save the normal.dot every time Word 2003 or Outlook 2003 if Word is used as editor, is closed. And even if they save the normal.dot, of course, next time they are requested to save again.
And if we uninstall Acrobat 9 Standard on the PCs concerned, the issue dissapear... and reappear if we re-install it.
So, the issue is clearly linked to Acrobat 9 Standard.
Of course, the Word 2003 option "Confirm to save the normal.dot" is NOT checked.
It doesn't seems to happens on all the PCs but we can't isolate the commun point between those which have the issue.
All our PCs are made by ghosting so are pretty similar, with Windows XP SP3 avec Office 2003 SP3... and now Acrobat 9.1.3 Standard.
In case that would help the diagnostic, on the PCs without the issue, the message doesn't appear, but, still, the behavior of the normal.dot changes : the time stamp changes every time Word or Outlook is closed. Before the install of Acrobat 9, the timestamp was not changing everything, but only of changes were made.
So, I guess Acrobat 9 Standard (probably the add-in for pdfmaker) forces the saving of all the .dot everytime Word or Outlook is closed.
Can you help us ?
Thanks

Answer 1

Thanks for your reply, but the issue is the same even when Word is not the default editor in Outlook.
Regarding the Office 2003 and Acrobat 9 updates, we are already up-to-date for Acrobat 9, but it's true that all our PCs have not yet received the SP3 for Office 2003, so it may be a trail to follow.
But I think the issue also happens even on some PCs with most up-to-date Office 2003, so I'd say it's probably not the solution.
But it doesn't seems that this kind of issue is widly encountered (I mean elsewhere than in our company).
So there is probably something specific to our environnement. And since we pretty much "lock-down" the PCs (to avoid users to mess with it), it's not impossible that some restrictions somewhere on the PC causes the issue... at least to some categories of users who are missing some authorisations.
But I'm sure that when we uninstall the "Adobe PDFMaker" component (in add/remove programs), the problem dissappear. So we are probably going to adopt this "solution" to make the steam goes down among our annoyed employees... until we'll find a better one.