Tips and Recommendations for the use of security templates

Proper usage patterns

•
Ready or newly created templates security should not be used on a computer or network without prior verification, in which reconfirmed the existence of the required level of functionality applications.

•
We should not change the pattern Setup security.inf, as it allows to restore security settings used by default. In the case of removal of the template object of group security policy, use: Setup security.inf to restore the defaults.

•
Do not use a template Setup security.inf "snap through Group Policy." Template Setup security.inf should only apply to the local computer via a command line means "snap analysis and adjustment of security." Over the correct decision would be to apply a template for parts using command-line tools.

•
Do not use a template to compatible computers, which are the domain controllers. For example, should not be compatible import pattern in the object domain by default, or in the standard group policy object domain controller.
Compliance with caution when changing defaults

•
Instead of changing the template finished suggest setting such a template and save the changes under a different name template. Ready made templates were created to address the challenges of model and the maintenance of these patterns will enable them to use if necessary.

•
In determining the level of access to the computer end-users, the default is critical installed base of applications to be supported. If all users are working only with applications, certified for compliance with the logo of Windows, they can be made members of the group "Community". Otherwise, it may be necessary part of the allocation of users to the group "experienced users" to give them the appropriate authorization, the level of safety is reduced.