Directory and Resource Administrator
Exchange Administrator

Version 7 Service Pack 1

Release Notes

Revised: April 12, 2004

 

 

Directory and Resource Administrator (DRA) and Exchange Administrator (ExA) provide secure, automated administration of your Windows and Exchange environments. DRA and ExA increase security, reduce administrative cost, and protect the integrity of your Active Directory, Exchange, and NT SAM.

Customer suggestions direct many of the improvements provided in this release. Your time and input are invaluable.

This document outlines the updates included with this version. We assume you are familiar with previous versions of these products.

What this Service Pack Addresses

DRA and ExA 7 SP 1 provides a number of performance, usability, and stability enhancements. The following sections outline the key issues resolved with this version:

Upgrading from Version 7

You must have DRA version 7 or DRA and ExA version 7 installed to install the service pack. To upgrade from DRA version 7 or DRA and ExA version 7, install the new version over your existing version. Do not uninstall your existing version.

If the setup program fails after stopping services, ensure you restart the services that were stopped. For example, ensure you restart the World Wide Web Publishing Service. The setup program rolls back all other changes.

Return to Top

Microsoft Exchange Issues

A number of issues involving the administration of Microsoft Exchange objects have been addressed in DRA and ExA 7 SP 1, including the following issues:

Exchange 5.5 Delivery Restriction Power

Corrects an issue in which the delegation of the Exchange 5.5 Delivery Restriction power did not allow an Assistant Admin the ability to set delivery restrictions on a mailbox.

Viewing Exchange 5.5 Distribution Lists

Corrects an issue when viewing distribution lists with a large number of members. You no longer receive the following error when attempting to view distribution lists: The address list could not be displayed. The table requested by this operation contains too many names and cannot be accessed.

Creating Exchange 2003 Mailboxes for Existing User Accounts

Corrects an issue when attempting to create a mailbox for an existing user account using DRA and ExA in conjunction with Exchange 2003. Before applying the service pack, you may have encountered the following error: Error performing task: An operation error occurred.

Setting the Display Name of Distribution Groups

Corrects an issue that could be encountered when using and viewing distribution groups created by DRA and ExA. DRA and ExA incorrectly set the Display name of distribution groups to /o=org/ou=First Administrative Group. These distribution groups function correctly, but can cause erroneous Undeliverable errors. The service pack corrects this issue.

Cloning Mailboxes

Resolves the following mailbox cloning issues:

  • An Assistant Admin with the Clone Exchange 5.5 mailbox power could not clone mailboxes.
  • Cloning a mailbox without specifying new values for the first name or last name could cause the alias to be incorrectly set or the clone operation to fail.

Applying this service pack corrects these issues.

Cloning User Accounts with Mailboxes

Resolves an issue in which an Assistant Admin with the Clone user account power was able to see and edit the Exchange 5.5 mailbox properties tab during the cloning of a user account, though the mailbox would not be created. Applying this service pack ensures Assistant Admins with the power to clone user accounts do not see this tab unless they also have the power to clone mailboxes.

Specifying a User Account for Send on Behalf

Resolves an issue in which the user account specified for the Send on Behalf value on the Delivery options tab is not persisted. The service pack corrects this issue.

Setting Mailbox Storage Limits

Corrects the inability to set mailbox storage limits through the Account and Resource Management and Delegation and Configuration user interfaces.

Viewing All Available Exchange Servers

Ensures the Account and Resource Management and Delegation and Configuration user interfaces correctly display all the available Exchange 2000 or later servers on which a mailbox can be created. In environments containing numerous Exchange 2000 or later servers, the user interfaces could display a subset of the available servers.

Updating Exchange 5.5 Mailbox Properties

Ensures that Exchange 5.5 mailbox property updates do not cause thread concurrency issues during server selection in environments with numerous Exchange servers. User experiencing this issue may have seen the user interface stop responding.

Attempting to Connect to an Exchange 5.5 Server

Corrects an issue in which an unavailable Exchange 5.5 server caused the Administration server to cache a blank Exchange 5.5 server name. This blank cached value caused future connections to the Exchange server to fail.

Moving Multiple Mailboxes

Ensures that moving multiple Exchange 5.5 mailboxes does not cause thread concurrency issues. User experiencing this issue may have seen the NetIQ Administration Service stop responding.

Return to Top

Web Console Issues

A number of issues involving the Web Console have been addressed in DRA and ExA 7 SP 1, including the following issues:

Scrolling and Using the Go Option

Corrects an issue when attempting to scroll or use Go on the Member of tab for groups, user accounts, or computers. Scrolling or using Go could reset the displayed information to the General tab.

Viewing and Modifying Mailbox Properties through the Web Console

Resolves an issue involving Assistant Admins with the appropriate powers being unable to view and modify the mailbox properties of user accounts in the Web Console. Individuals experiencing this problem may have received the following error: You do not have power to see any properties on this form.

Persisting Fields between Different Tabs

Corrects an issue when displaying or updating the properties of a user account and switching between the Terminal Services tab and the Profile tab or the Profile tab and the Terminal Services tab. Either the User account profile path or the Terminal services profile path would persist between the two tabs.

Updating the User Account Comment During a Clone Operation

Ensures that the Comment field of a User Account updated through the Web Console during a clone operation correctly maps to the User Comment field in the client user interfaces. Previously, the comment supplied during the cloning of a user account through the Web Console updated the Comment field of the General tab in the client user interfaces.

Displaying Available OUs with Internet Explorer 5.5

Resolves an issue in which the OU list remained empty when viewed using Internet Explorer 5.5 during the creation of a new user account.

Managing Services and Printers through the Web Console

Corrects an issue in which custom roles created to grant nominal powers to Assistant Admins over services and printers did not allow the Assistant Admins the ability to control services and printers through the Web Console.

Detecting the Correct Internet Explorer Version

Resolves an issue found when running the Web Console from a client on which a decimal is represented with the comma (,). Individuals experiencing this issue may have seen the following warning: WARNING: The internet browser software you are using may not be compatible with DRA Web Console, which has only been confirmed to support Microsoft Internet Explorer versions 5.5 and higher. Review the information below.

Return to Top

Client User Interface Issues

A number of issues involving the client user interfaces have been addressed in DRA and ExA 7 SP 1, including the following issues:

Specifying Exchange Options During Group Cloning

Resolves an issue in which the client user interfaces did not enable the Exchange tab during the clone of a group. The Exchange tab is now enabled as long as the Assistant Admin is granted both the Clone Group and Modify All Properties power and the Enable Email for Group power.

Unable to Refresh Agents when Connected to a Secondary Administration Server

Allows you to click Refresh Agents on the General tab of the Administration Server Options window when connected to a secondary Administration server. Previously, you needed to be connected to the primary Administration server to enable this option.

Updating the Group Type for Windows 2003 Groups in Native Mode

Corrects an issue in which the group type for pre–existing Windows 2003 groups in native mode was not enabled. You can now update both the scope and type of Windows 2003 groups.

Previewing a Large Number of Objects

Resolves an issue with the ability to stop enumerations in the Preview Manage Objects window when focused on ActiveViews with a large number of objects. Previously, enumerations that resulted in a very large number of returned objects could cause undue computer resource usage. Clicking Stop canceled the enumeration. Applying this service pack allows you to either click Stop or close the window.

Removing Multiple Group Memberships

Corrects an issue in which selecting multiple groups from the Member of tab for a user account and attempting to delete these group memberships caused an exception or the following erroneous error: The Object is not a member of the Group. Applying this service pack ensure that the use of the shift key to select multiple group memberships to delete no longer causes an error.

Displaying Child OUs at the Root Level in the Right Hand Tree Pane

Corrects an issue in which an exclude rule is used to exclude a child OU but sub-child OUs were displayed at the root of the tree pane. While Assistant Admins were not granted control over any objects the exclude rule excluded, the display of sub-child OUs has been corrected.

Clearing the User Must Change Password at Next Logon Check Box

Resolves an issue in which clearing Generate Password also cleared User Must Change Password at Next Logon when resetting a password.

Changing the Administration Server from a Non-English Operating System

Allows user interfaces to connect to an alternate Administration server without receiving the error.NulReferenceException error and without changing the network provider order of the network connection.

Updating User Account Properties

Resolves an issue where the not enough power to run UserSetInfo error was encountered when attempting to modify the properties of a user account. For example, you may have encountered this error when attempting to set the Windows Terminal Services (WTS) properties of a user account.

Specifying WTS Home Directory Drives Using Lowercase Letters

Corrects an exception when using lowercase letters to specify the home directory drive for an account using WTS.

Creating or Cloning Groups in a Windows NT Domain

Corrects the inability to create or clone groups in a Windows NT domain. Previously you may have encountered the Error changing the property displayname message when attempting this operation.

Return to Top

Memory Management Issues

A number of issues involving memory management have been addressed in DRA and ExA 7 SP 1, including the following issues:

Running Consecutive Domain Configuration Refreshes

Corrects an issue in which running numerous consecutive domain configuration refreshes could make the Administration server unresponsive or consume unnecessary system resources.

Enumerating a Large Number of Objects

Corrects an issue in which large enumerations could cause an exception or an Out of memory error.

Changing Mailbox Rights

Corrects an issue in which changing mailbox rights for a number of user accounts could cause an exception and, ultimately, shutdown the server service.

Running a Full Accounts Cache Refresh

Corrects the failure of a full accounts cache refresh after performing a domain configuration refresh. Client user interfaces attempting to connect to an Administration server after performing a domain configuration refresh followed by a full accounts cache refresh may have had the connection refused and received a Can not identify client error.

Return to Top

User Account and Object Issues

A number of issues involving the user account and object administration have been addressed in DRA and ExA 7 SP 1, including the following issues:

Receiving Not Enough Storage to Complete this Operation Error

Corrects an issue in which Assistant Admins enumerating a large number of managed objects receive the Not enough storage to complete this operation error. After receiving the error, other Assistant Admins would also receive the error and not be able to use the Administration server. Applying the service pack resolves this issue.

Enabling the LastNameFirstPre.vbs Automation Trigger

Corrects an issue in which enabling the LastNameFirstPre.vbs automation trigger to set the common name (CN) and display name during a the cloning of a user account could delete a previously existing account with the same display name. This trigger is available to customers from the Knowledge Depot on the NetIQ Web site (www.netiq.com).

Cloning User Accounts

Resolves an issue in which an Assistant Admin with the Clone User and Modify General Properties power cannot clone user accounts. Individuals who experienced this problem received the following error: The Assistant Admin does not have the power to clone user. Applying the service pack resolves this issue.

Modifying User Accounts Containing the / Character

Corrects a problem renaming, deleting, or changing the properties of user accounts, groups, contacts, and OUs containing the / character in the common name. The common name is equivalent to the CN value in an ADSI string. For example, the value j,dob/telphn in the following string: OnePoint://CN=j,dob/telphn,OU=NM,OU=US,DC=box,DC=local.

Creating the UPN of a User Account

Corrects an issue in which the user principal name (UPN) did not default to the same domain in which DRA created an account. Applying the service pack resolves this issue.

Return to Top

Upgrading Issues

A number of issues involving upgrading to version 7 have been addressed, including the following issues:

Modifying ActiveView Rules

Corrects a number of issues concerning the viewing and modifying ActiveView rules created in previous versions of the product. Individuals may have seen a number of different symptoms of this error, including the following:

  • mcsStatus::StatusMSG::FormatMessage failed - unable to format message - Error (317) DLL=C:\Program files\netiq\dra\mcsadminmsgenu.dll when attempting to create Computer accounts.
  • This is a special rule. You can only remove it, not edit it when attempting to edit include rules.

Applying the service pack resolves these issues.

Modifying Rules Generated by EAMigrate

Corrects an issue in which rules migrated using EAMigrate could cause the client user interfaces to generate an exception. These rules no longer cause errors in the user interfaces.

Client User Interfaces Connect to the Correct Administration Servers

Corrects an issue in which the user interfaces connected to the nearest Administration server without regard for the server version. This change ensure that 6.6 clients only provide 6.6 servers and 7.0 clients provide only 7.0 servers when selecting Administration servers to which to connect.

Return to Top

Windows NT Administration Issues

A number of issues involving the administration of Windows NT objects have been addressed in DRA and ExA 7 SP 1, including the following issues:

Providing Access to Windows NT Objects

Corrects an issue in which Windows NT objects could inadvertently be included in or excluded from an ActiveView.

Showing Advanced AD Objects

Resolves an issue in which the administrators of a managed Windows NT domain were able to view the advanced Active Directory objects in a Windows 2000 domain.

Registering Agents in Windows NT Domains

Corrects an issue in which agents appeared to install correctly but were unable to communicate with the Administration server. Individuals experiencing this problem received one of the following errors: Failed to get agent registration, hr=8001011C or Remote calls are not allowed for this process.

Return to Top

Command Line Interface Issue

Corrects an issue in which the command line interface (CLI) ignored the client user interface setting controlling whether to update the mailbox alias name during mailbox updates (Enforce alias naming rules during mailbox updates). Previously, changing the user account name through the CLI would also change the mailbox alias name. The CLI now only updates the alias if this option is set in the client user interface.

Return to Top

Legal Notice

Return to Top