Directory and Resource Administrator 6.60
The bHideUnmanagedObjects flag in hideUnmanagedObjectsFlag.js does not function in Directory and Resource Administrator 6.6.
All objects enumerate correctly in the AD and Domain Explorer snap-in node. Only the My ActiveViews node does not work correctly.
The ability to control whether an Assistant Admin sees unmanaged objects in an ActiveView can be controlled by setting the bHideUnmanagedObjects flag to True in the hideUnmanagedObjectsFlag.js script file. Setting this value to True (the default value is False) prohibits AA's from seeing objects that they have no powers over when viewing an ActiveView that has source-only rules associated with it.
Setting this flag in DRA 6.6 prohibits any DRA Administratoror Assistant Admin from enumerating any objects under the My ActiveViews snap-in node. When attempting to search for any account under the appropriate object-related view, the search returns No objects found that match your criteria.
This is caused by en error in the filter parsing code on the server. Instead of passing the filter avmatch='*',ruletype=source to the server, the client reverses the order of the individual filters and passes ruletype=source,avmatch='*'.
Hotfix 24326 ensures the MMC interface correctly lists account objects when you perform the following tasks:
- You define an ActiveView to include objects as source objects only. You can set the MMC interface to not display these objects in the associated ActiveView.
- You select a user account or contact in an ActiveView. If you enabled domain nodes and are selecting a user account or contact from a specific domain, the MMC interface should display all available groups in the secondary list of the results pane.
If you want to control whether an Assistant Admin can view source objects in an ActiveView, apply this hotfix. If your Assistant Admins use secondary lists to manage group memberships, apply this hotfix.
To install this hotfix, run the DRA66000_Hotfix24326.exe file on each computer where you installed the Web component. By default, the setup program installs the Web component on the Administration server computer.
This hotfix modifies the following files on the Administration server computer:
By default, these files are located in the C:\Inetpub\wwwroot\DRAWeb\Admin\lib\js\custom directory.