Cannot change macro security level

[Sue Mosher [MVP-Outlook]]

For each application, User Configuration / Administrative Templates / <name
of app> / Tools | Macro / Security / Security Level.

Also, User Configuration / Administrative Templates / Microsoft Office 2003
/ Security Settings / Automation Security.

 

[Sue Mosher [MVP-Outlook]]

For each application, User Configuration / Administrative Templates / <name
of app> / Tools | Macro / Security / Security Level.

Also, User Configuration / Administrative Templates / Microsoft Office 2003
/ Security Settings / Automation Security.

 

[Sue Mosher [MVP-Outlook]]

For each application, User Configuration / Administrative Templates / <name
of app> / Tools | Macro / Security / Security Level.

Also, User Configuration / Administrative Templates / Microsoft Office 2003
/ Security Settings / Automation Security.

 

[Sue Mosher [MVP-Outlook]]

For each application, User Configuration / Administrative Templates / <name
of app> / Tools | Macro / Security / Security Level.

Also, User Configuration / Administrative Templates / Microsoft Office 2003
/ Security Settings / Automation Security.

 

[Sue Mosher [MVP-Outlook]]

For each application, User Configuration / Administrative Templates / <name
of app> / Tools | Macro / Security / Security Level.

Also, User Configuration / Administrative Templates / Microsoft Office 2003
/ Security Settings / Automation Security.

 

[Sue Mosher [MVP-Outlook]]

For each application, User Configuration / Administrative Templates / <name
of app> / Tools | Macro / Security / Security Level.

Also, User Configuration / Administrative Templates / Microsoft Office 2003
/ Security Settings / Automation Security.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Prem]

Thank you for your reply.

In order to execute your suggestions, I had to download the office
2003 resource kit to add administrative templates to the GPO, changed
the macro settings to medium, but that does not change anything when I
open the Word or Excel application, always unable to enable macro's,
and the macro security setting sets itself to 'high'. (and the office
2003 adm templates disappear each time, I have to insert them each
time again)

I get the following macro's that I must disable to open the office
applications:
C:\Progra1~1\common~1\mocros~1\smartt~1\fplace.dll
and same location:
fdate.dll
mofl
fstock
fperson
fname

N.B.: This behaviour appears on the server machine itself, not on the
client computers (the client computers have their own office2003
installed).
On the server, I uninstalled Office2003, rebooted, reinstalled office
2003, but still with the same symptoms.

Maybe you can help me a bit further: What processes in SBS2003 are
checking the macro security settings of applications? WMI ?

I have a second thread on this topic, that I will drop, focussing on
this one.

 

[Sue Mosher [MVP-Outlook]]

Check the registry to see what the value of DontTrustInstalledFiles is. It should be zero for each application.

Why are you running Office on the server in the first place?

I don't know why the .adm templates would be disappearing. You might want to ask in an AD group. Have you tried using the new Group Policy manager tool from MS to look at the policy results for the user logged on to the server?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Check the registry to see what the value of DontTrustInstalledFiles is. It should be zero for each application.

Why are you running Office on the server in the first place?

I don't know why the .adm templates would be disappearing. You might want to ask in an AD group. Have you tried using the new Group Policy manager tool from MS to look at the policy results for the user logged on to the server?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Check the registry to see what the value of DontTrustInstalledFiles is. It should be zero for each application.

Why are you running Office on the server in the first place?

I don't know why the .adm templates would be disappearing. You might want to ask in an AD group. Have you tried using the new Group Policy manager tool from MS to look at the policy results for the user logged on to the server?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Check the registry to see what the value of DontTrustInstalledFiles is. It should be zero for each application.

Why are you running Office on the server in the first place?

I don't know why the .adm templates would be disappearing. You might want to ask in an AD group. Have you tried using the new Group Policy manager tool from MS to look at the policy results for the user logged on to the server?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Check the registry to see what the value of DontTrustInstalledFiles is. It should be zero for each application.

Why are you running Office on the server in the first place?

I don't know why the .adm templates would be disappearing. You might want to ask in an AD group. Have you tried using the new Group Policy manager tool from MS to look at the policy results for the user logged on to the server?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers