Upgrading DSfW
9
This section provides information and links for upgrading DSfW to OES 2 SP2.
Section 9.1, "Upgrading DSfW to OES 2 SP2," on page 127
Section 9.2, "Upgrading from OES 1.0 Linux," on page 127
Section 9.3, "Migrating Data to a Domain Services for Windows Server," on page 127
Section 9.4, "Limitations," on page 128
9.1 Upgrading DSfW to OES 2 SP2
To upgrade DSfW from OES 2 SP1 to OES 2 SP2, follow the process documented in the
"Upgrading to OES
2" in the
IMPORTANT: While running the upgrade process, make sure you first upgrade the first domain
controller and then upgrade the additional domain controllers in that domain.
9.1.1 Prerequisite
Before running the upgrade process, ensure that time is synchronized between all the servers in the
replica ring.
9.1.2 Limitations
After upgrading, you may encounter a Samba cache file corruption issue. Follow the instruction
documented in
"Error Mapping SID to UID" on page 211
9.2 Upgrading from OES 1.0 Linux
In-place upgrade of an existing OES 1.0 Linux server to a DSfW server is not supported.
You must first install and configure a new OES 2 Linux server with DSfW, then migrate data from
the existing OES 1.0 NetWare or Linux server.
9.3 Migrating Data to a Domain Services for
Windows Server
The migration of data to an OES 2 Linux server running DSfW is similar to any other data migration
to OES 2 Linux:
You should use the new OES 2 migration tools.
When the source and destination servers are in the same eDirectory
trustee rights are migrated.
When the source and destination servers are in different eDirectory trees, the data and
associated users are migrated.
OES 2 SP2: Planning and Implementation Guide
to resolve the error.
tree, only the data and
TM
9
Upgrading DSfW
127