Ranger profiles and system policies

Question

Do Ranger profiles stop or interfere with either System policies or Active Directory domain security policies?

Symptoms

N/A

N/A

Cause

N/A

Resolution

No, Ranger doesn't disable or ignore System policies or Active Directory policies.

 
Any policy settings configured from within RangerAdmin are implemented in addition to whatever settings are set in system policies/Active Directory policies. Ranger's "policy" settings are simply registry key changes set from the same ADM files as used by system policies.

 

These registry keys are merged into the registry directly before the shell is launched - hence are the last things to be configured before the user environment is created.

Instructions

Ranger profiles are designed to complement and work beside any existing policies/profiles running on a system. They do not replace or implement the user.dat copying functions of roaming profiles, nor do they stop system policies working.

 

It is important to note however, that if the same setting (eg: Start Menu location) is configured both within system policies and within Ranger, the Ranger value will take priority as it will be the last to modify the user's registry when logging in. If Ranger policies are not being used, ensure all settings are "greyed" to ensure no changes are implemented by Ranger.

 

Ranger profiles are intended as a simple and extendible method of implementing many of the useful system settings configured via policy editor ADM templates. They allow policies to be implemented without the need for System Policy editor to be explicitly installed on each machine, can be configured directly within RangerAdmin, are not operating system dependant for configuration and are extendible with custom or standard ADM files.

 

Ranger uses profiles to provide a consistent and familiar interface to system policies that is pre-configured, easy to use and complements the specialised Ranger network security.

Testing

N/A