Automated Outlook Signature Issue

[Paul]

I have a vbs script that runs at logon to create a signature file from AD for
users. It writes the HTML file in the signature folder and also adds the
registry settings to make it the default signature for new and replies under
this key:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles\[Profile
Name]\9375CFF0413111d3B88A00104B2A6676\00000002\New Signature & Reply-Forward
Signature

The signature adds correctly to any new HTM emails however when I reply or
create or reply to a plain text or RTF message it deletes the registry key
"HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles\[Profile
Name]\9375CFF0413111d3B88A00104B2A6676\00000002\New Signature" which then
prevents signatures being added to any new messages. It is not until I reset
the signatures that it continues to operate correctly.

Is this a common problem? I have narrowed it down to the fact that the rtf &
txt versions of the signature do not exist which causes Outlook to create
them, then deleting the New Signature key. Can you suggest a way around this
or a possible fix?

Thanks in advanced

 

[Sue Mosher [MVP-Outlook]]

The fix would be to provide .rtf and .txt versions of the signature file.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Paul]

That's what I was expecting however it seems all the scripts I came across
only create the HTM file. Seemed odd that this has not been address so I
thought it may be a bug in Outlook.

The fix would be to provide .rtf and .txt versions of the signature file.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

I have a vbs script that runs at logon to create a signature file from AD for
users. It writes the HTML file in the signature folder and also adds the
registry settings to make it the default signature for new and replies under
this key:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles\[Profile
Name]\9375CFF0413111d3B88A00104B2A6676\00000002\New Signature & Reply-Forward
Signature

The signature adds correctly to any new HTM emails however when I reply or
create or reply to a plain text or RTF message it deletes the registry key
"HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles\[Profile
Name]\9375CFF0413111d3B88A00104B2A6676\00000002\New Signature" which then
prevents signatures being added to any new messages. It is not until I reset
the signatures that it continues to operate correctly.

Is this a common problem? I have narrowed it down to the fact that the rtf &
txt versions of the signature do not exist which causes Outlook to create
them, then deleting the New Signature key. Can you suggest a way around this
or a possible fix?

Thanks in advanced

 

[Sue Mosher [MVP-Outlook]]

No, it's not a bug. If you want full signature support, you have to provide the signature files.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

That's what I was expecting however it seems all the scripts I came across
only create the HTM file. Seemed odd that this has not been address so I
thought it may be a bug in Outlook.

The fix would be to provide .rtf and .txt versions of the signature file.

I have a vbs script that runs at logon to create a signature file from AD for
users. It writes the HTML file in the signature folder and also adds the
registry settings to make it the default signature for new and replies under
this key:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles\[Profile
Name]\9375CFF0413111d3B88A00104B2A6676\00000002\New Signature & Reply-Forward
Signature

The signature adds correctly to any new HTM emails however when I reply or
create or reply to a plain text or RTF message it deletes the registry key
"HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
Messaging Subsystem\Profiles\[Profile
Name]\9375CFF0413111d3B88A00104B2A6676\00000002\New Signature" which then
prevents signatures being added to any new messages. It is not until I reset
the signatures that it continues to operate correctly.

Is this a common problem? I have narrowed it down to the fact that the rtf &
txt versions of the signature do not exist which causes Outlook to create
them, then deleting the New Signature key. Can you suggest a way around this
or a possible fix?

Thanks in advanced