The domain boundary can be extended to include multiple partitions. This can be done either during install or post install. For more information, see Section 5.4, Extending a Domain Boundary in a Name-Mapped Installation.

The domain name and RDN of a mapped container can be different. For instance, the partition ou=example,o=organization can be mapped to a domain named dsfw.com.

Beginning OES 2 SP3, after successful mapping of a container to a DSfW domain, you can map any underlying container to a new DSfW child domain and skip any level of containers in between. For more information, see Deploying DSfW by Skipping Containers.

The administrator name of a domain can be renamed post provisioning using MMC. For more information, see Renaming Administrator Details Using MMC.

Beginning in OES 2 SP3, the DSfW provisioning wizard will not transfer the master replica of a mapped partition to the first Domain Controller of a DSfW domain. Due to this, there are certain implications on operations that assume the master replica to be present on the DSfW Domain Controller. One such operation is moving users into a DSfW domain. In this case, the moved user is not automatically samified. The samification of this moved user is initiated on the next eDirectory login, for instance using ndslogin.

Alternatively, the domain administrator or the tree administrator can modify the moved user by setting an optional attribute (for instance description) and then revoking the change to initiate the samification of the moved user immediately. For a bulk move of users, it is recommended to use domaincntrl tool's samify operation to trigger the samification by selecting the partitions that the user's are moved to. For more information on implications of a user move into a domain, see Section 12.4.1, User Samification Fails On Moving Users into a DSfW Domain.

DNS server can now be configured on a subsequent domain controller.

Support to join Windows 2008 server as a member server to the domain.