The following table includes some examples of regular expressions and matches.
Table 139: Examples of regular expressions
st.n |
Austin and Boston |
Webster |
st[io]n |
Austin and Boston |
Stanton |
st[^io]n |
Stanton |
Boston or Austin |
^boston |
Boston |
South Boston or North Boston Harbor |
ston$ |
Boston and Galveston |
Stonewall |
sea|side |
Seattle and Seaside and Oceanside |
Seoul or Sidney |
dal(l|h)art |
Dalhart |
Dallas or Lockhart |
il?e$ |
Etoile and Wylie |
Beeville |
il*e$ |
Etoile and Wylie and Beeville |
Bellaire |
il+e$ |
Etoile and Beeville |
Wylie |
ad{2} |
Addison and Caddo |
Adkins |
(la.*){2,} |
Highland Village and Lake Dallas |
Laredo |
Once you have constructed a regular expression, it is evaluated much like an arithmetic expression. It is evaluated from left to right and follows an order of precedence.
The following table shows the order of precedence for the various regular expression operators, starting with the highest:
Table 140: Order of precedence
\ |
Escape |
(), [] |
Parentheses and Brackets |
*, +, ?, {n}, {n,}, {n,m} |
Quantifiers |
^, $, \anymetacharacter |
Anchors and Sequences |
| |
Alteration |
The Active Roles Administrative Template allows you to control the behavior and appearance of the Active Roles Console by using Group Policy. For more information, see Active Roles snap-in settings.
This Administrative Template also provides a number of policy settings allowing you to limit the list of Active Roles’s Administration Service instances for auto-connect. For more information, see Administration Service auto-connect settings.
With the Active Roles Snap-in policy settings you can:
-
Hide some areas of the user interface with the Console.
-
Specify default settings for some user interface elements.
-
Specify settings to register extension snap-ins with the Active Roles Console.
The Administrative Template provides the following policy settings to control the behavior and appearance of the Active Roles Console:
Table 141: Policy settings to control the behavior and appearance of the Active Roles Console
Hide Exchange management |
Removes all user interface elements (commands, wizards, and dialog boxes) intended to manage Exchange recipients. If you enable this policy, users cannot perform any Exchange tasks and manage any Exchange recipient settings with the Active Roles Console. If you disable this policy or do not configure it, users with appropriate permissions can use the Active Roles Console to perform Exchange tasks and manage Exchange recipient settings. |
Set default view mode |
Specifies view mode in which the Active Roles Console will start. If you enable this policy, you can select view mode from a list. When started, the Active Roles Console will switch to the view mode you have selected. By default, users are allowed to change view mode by using the Mode command on the View menu. If you want to enforce a view mode, select the User is not allowed to change view mode policy option. This option ensures that the Console user cannot change the view mode that you have selected. |
Hide Configuration node |
Removes the Configuration node from the Console tree when the Active Roles Console is in Advanced view mode. If you enable this policy, in Advanced view mode, all objects and containers related to the Active Roles configuration are not displayed. The Managed Units node and its contents are displayed as well as all advanced Active Directory objects and containers. |
Disable Remember password option |
Clears and disables the Remember password check box in the Connect to Administration Service dialog. If you enable this policy, the Connect as: The following user option in the Active Roles Console requires the user to enter their password every time when using that option, rather than encrypting and storing the password once it has been entered.
NOTE: Saving passwords may introduce a potential security risk. |
Disable Connect as options |
Disables the Connect as options in the Connect to Administration Service dialog, including the Remember password check box. If you enable this policy, the Console users are only allowed to connect to the Administration Service under their logon accounts. With this policy, the Current user option is selected under Connect as, and cannot be changed. |
Set controlled objects to be marked by default |
Specifies whether to use a special icon for visual indication of the objects to which Access Templates or Policy Objects are applied (linked). If you enable this policy, you can choose the category of object to be marked with a special icon by default. Users can modify this setting using the Mark Controlled Objects command on the View menu. |
In addition, the Administrative Template provides for policies allowing you to register extension snap-ins with the Active Roles Console. These policies are located in the folder named Extension Snap-ins. Each policy in that folder is used to register one of the following:
Table 142: Policies allowing to register extension snap-ins with Active Roles Console
Namespace extensions |
Allows you to register extension snap-ins to extend the namespace of the Active Roles Console. |
Context menu extensions |
Allows you to register extension snap-ins to extend a context menu in the Active Roles Console. |
Toolbar extensions |
Allows you to register extension snap-ins to extend the toolbar of the Active Roles Console. |
Property sheet extensions |
Allows you to register extension snap-ins to extend property sheets in the Active Roles Console. |
Task pad extensions |
Allows you to register extension snap-ins to extend a task pad in the Active Roles Console. |
View extensions |
Allows you to register extension snap-ins to add user interface elements to an existing view or to create new views in the Active Roles Console. |
When configuring a policy from the Extension Snap-ins folder, you are prompted to specify the name and the value of the item to be added.
The name parameter determines the type of the node you want to extend. Each type is identified with a GUID. For example, if you want to extend user objects, the GUID is {D842D417-3A24-48e8-A97B-9A0C7B02FB17}.
The value parameter determines the extension snap-ins to be added. Each snap-in is identified with a GUID. You add multiple snap-ins by entering their GUIDs separated by semicolons. For example, value might look as follows:
{AD0269D8-27B9-4892-B027-9B01C8A011A1}"Description";{71B71FD3-0C9B-473a-B77B-12FD456FFFCB}"Description"
The entry "Description" is optional and may contain any text describing the extension snap-in, enclosed in double quotation marks.