P
Patrick
I've got a problem with Outlook reading the Outlook Security Settings
folder properly. I have 2 Public Folders - one called "Outlook
Security Settings" for Office 2k clients, and one called "Outlook 10
Security Settings" for Office XP clients. In my login script I have a
command to merge the appropriate registry info
(hkcu\software\policies\microsoft\security\checkadminsettings=2 for
the Office XP users). No problem because all users have local admin
rights to their machines.
Enter terminal server, where no one has local rights except domain
admins; result: registry key doesn't merge and forms crap out with "A
program is trying to access email address you have stored in Outlook .
.. . blah blah blah". If I temporarily add the user to local admins on
the terminal server, then login once it's fine. When I remove him from
the local admins group and try again the value of that key reverts
back to 1 and the error recurs.
Is there any way to globally set that key for all users? Perhaps via a
group policy? In addition, can anyone explain why the key is reverting
back to 1? That's really mystifying me.
TIA.
- Patrick
folder properly. I have 2 Public Folders - one called "Outlook
Security Settings" for Office 2k clients, and one called "Outlook 10
Security Settings" for Office XP clients. In my login script I have a
command to merge the appropriate registry info
(hkcu\software\policies\microsoft\security\checkadminsettings=2 for
the Office XP users). No problem because all users have local admin
rights to their machines.
Enter terminal server, where no one has local rights except domain
admins; result: registry key doesn't merge and forms crap out with "A
program is trying to access email address you have stored in Outlook .
.. . blah blah blah". If I temporarily add the user to local admins on
the terminal server, then login once it's fine. When I remove him from
the local admins group and try again the value of that key reverts
back to 1 and the error recurs.
Is there any way to globally set that key for all users? Perhaps via a
group policy? In addition, can anyone explain why the key is reverting
back to 1? That's really mystifying me.
TIA.
- Patrick