Macro security level can't be raised

[Joe]

I can't raise the macro security level in Word 2003 even though I am logged
on as Administrator. Additionally, the "Trust Access to Visual Basic
Project" check box in the "Trusted Publishers" tab is greyed out and the tick
cannot be removed. The macro level is currently set to "Low".

Office 2003 was originally deployed using group policy and an MST file that
was created with the ORK's Custom Installation Wizard. I have used the RSOP
mmc add-in on the Windows XP client computer and the settings are NOT the
result of group policy from the Office ADM templates.

I believe the Word security settings were locked down in the initial MST
file created for the deployment and that it is related to the Computer
settings.

Can anyone please help me out and let me know how I could change the
security settings? Thanks.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[neo [mvp outlook]]

The CIW creates the same registry keys values as the Office ADM templates.
Might want to check under
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\11.0... to see if some
of the policy keys have been set since policy object editors do not read
existing settings from the registry.

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe

 

[Joe]

I fixed this problem by deleting two registry values: "AccessVBOM" and
"Level" from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Word\Security.

The answer you gave was very close to what I needed. Thanks very much
getting me on the right track.

Joe