|
|
|
|
|
1.
|
|
User Accounts added to other policies are not being enforced properly
|
|
|
|
|
|
One of the dangers of setting a default policy is that unexpected behaviour can result if
user accounts are incorrectly added to another policy. If the account name is entered
incorrectly PC Chaperone will automatically use the default policy, which can make it
appear as if the users restrictions are not being enforced
If this behaviour is suspected check the User Info option on the PC Chaperone icon's menu
to confirm the policy being enforced
|
|
|
|
|
|
|
1.
|
|
User Account Types
|
|
|
|
|
|
The default security policy is only used when the
User Account Type
is set to mirror the Windows user accounts
|
|
|
|
|
|
|
1.
|
|
Set the default policy to the most restrictive policy
|
|
|
|
|
|
The most restrictive policy should be chosen as the default security policy. This will
ensure that any user accounts that have not been added to PC Chaperone will not have
more permissions then they should, and will prevent users from overriding their own
permissions if they manage to create a new Windows account
|
|
|
|
2.
|
|
Using the default policy as the main restricted policy
|
|
|
|
|
|
The default security policy can be used to group together all restricted users without the
need to add each of their Windows accounts to PC Chaperone. For example, if there are
many Windows user accounts that require the same restrictions, instead of adding each
Windows account to PC Chaperone simply set a default security policy with the
necessary restrictions. All of the Windows accounts, except the ones that are added to
other Security Policies, will now be controlled by this default policy,
including Windows accounts that are added to Windows at a later date
|
|
