Microsoft KB Archive/812287

= XADM: Considerations and Limitations That Apply If You Replace the Everyone Group with the Authenticated Users Group in Exchange System Manager =

Article ID: 812287

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange 2000 Enterprise Server

-



SUMMARY
This article discusses the considerations and limitations that apply when you modify permissions in Exchange 2000 Server. Specifically, this article discusses the scenario that involves removing the Everyone group and replacing it with the Authenticated Users group on all objects and containers in Exchange System Manager to which permissions apply.



MORE INFORMATION
By default, the Everyone group is included in the Name box of the Security tab of every container and object in Exchange System Manager to which permissions apply. If you want to modify permissions on all objects and containers in Exchange System Manager by removing the Everyone group and replacing it with another group, such as the Authenticated Users group, you must first consider the following:  This configuration has not been thoroughly tested, and is not supported by Microsoft Product Support Services (PSS). It is highly recommended that you apply this configuration in a test environment and monitor it closely before you deploy it in a production environment. The Everyone group is required for Anonymous access by Web-based programs and by the Network News Transfer Protocol (NNTP) Service. By default, the Everyone group is granted permissions to create top-level public folders and public folders, and to read from the metabase. If these permissions are removed, some programs on the server may not work correctly. When you manually modify permissions, the permissions are reset to their default values if you reinstall Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

320007 XADM: Permissions That Were Modified Manually Are Reset to the Default Values



Important: Because the scenario discussed in this article has not been exhaustively tested and is not supported, this list of considerations and potential implications that may occur as a result of this configuration may not be complete.

Keywords: kbnofix kbbug KB812287

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.