This section lists various known issues that have been encountered during the installation and configuration of Domain Services for Windows (DSfW). For installation instructions, see Installing Domain Services for Windows
in the OES 2 SP3: Domain Services for Windows Administration Guide.
This section contains the Domain Services for Windows installation and configuration issues.
If you are installing DSfW in an existing eDirectory setup, the installation overwrites the /etc/init.d/ndsd script.
We recommend that you back up the ndsd script before proceeding with the installation.
Novell plans to address this issue in a future OES release.
The provisioning process for non-name-mapped child domain controller fails if the forest root domain administrator name has space in it.
A DSfW upgrade to OES 2 SP3 might fail in a multiple-domain setup. This is an intermittent issue. To solve it, you must retry the upgrade process.
You might encounter the following issues while using MMC to manage the DSfW server:
When you copy a user object from MMC, it fails with an unspecified error.
Novell has no current plans to change this.
After a user is created, the administrator cannot force password changes through MMC because the check box is disabled. Users must change their own passwords.
Novell has no current plans to change this.
If an existing eDirectory is configured on a non-default port, the DSfW installation in a name-mapped scenario fails.
Novell plans to address this issue in a future OES release.
If you attempt to delete a file without having file delete permissions, the file disappears and an error message is not displayed. This is a display error and the file is not deleted from the system. To resolve this, refresh the screen.
Novell plans to address this issue in a future OES release.
In a name-mapped DSfW installation, the username for authentication should be entered in standard eDirectory/LDAP format and not the DSfW (domain) format.
Novell plans to address this issue in a future OES release.
If the configuration partition on an additional domain controller is not present locally and if you use the domaincntrl tool to add, remove, or list partitions, the following error is displayed:
Cannot read the crosssRef object.: Internal (implementation specific) error
This error occurs only for name-mapped scenarios. As a workaround, you must ensure that the configuration partition is present locally.
Novell plans to address this issue in a future OES release.
In a multiple-server scenario, when you run the domaincntrl tool on an additional domain controller to remove a partition, the tool fails to desamify the removed partition. This failure occurs because the synchronization between the servers is slow.
As a workaround, run the remove command followed by the desamify command. For more information about the domaincntrl tool options, refer to Verifying the Installation
in the OES 2 SP3: Domain Services for Windows Administration Guide.
IMPORTANT:The following list is provided here for your convenience. Do not consider the list as complete. Be sure to consult the documentation for your other Novell products for information on interoperability issues with DSfW.
The GroupWise installation program creates all GroupWise objects in the DSfW partition except for the WebAccess Application object.
Use iManager to create the WebAccess Application object inside the domain object and name it GroupWiseWebAccess. After this, run the installation program to install and configure the WebAccess Application software.
Novell has no current plans to change this.
On an OES 2 SP3 machine with DSfW installed, the ESM utility fails on all DSfW server ports.
Novell has no current plans to change this.
When you attempt to map to an NSS share from a Windows 7 or Windows 2008 R2 workstation by using the IP address, it fails to open the share.
To resolve this issue, use the DNS name to map the share.