9.1 Upgrading DSfW to OES 11 SP3

9.1.1 Upgrade Scenario

If a DSfW domain has multiple domain controllers, it is recommended to upgrade the primary domain controller first, followed by the upgrade of the remaining domain controllers.

To determine the IP address of the server that is the primary domain controller, use the following command:

dig -t SRV _ldap._tcp.pdc._msdcs._DOMAIN_NAME_ +short

Here, _DOMAIN_NAME_ is the domain name of the current domain, for example dsfw.com. In a DSfW setup that has multiple domains like FRD or child domain, the upgrade can be commenced from any domain.

NOTE:If all the domain controllers are not upgraded to the same patch level, the OES features will not be available.

9.1.2 Supported Mixed Mode configurations

Mixed mode DSfW domains in a DSfW forest is supported. However, it is recommended to have all the domain controllers of a domain run the same version of OES. You can have DSfW domains run different versions of OES (for example, OES 2 SP2 and OES11) in the same DSfW forest. However, SP2-specific features will only work in domains that run OES 2 SP2 and above. Similarly, OES 11-specific features will only work in domains that run OES 11.

9.1.3 Prerequisite

Before running the upgrade process, ensure that time is synchronized between all the servers in the replica ring.

9.1.4 Media Upgrade

Media upgrade involves upgrading in an offline mode from a physical media such as CD or DVD. For step-by-step instructions, refer to Using Physical Media to Upgrade (Offline) in the OES 11 SP3: Installation Guide.

9.1.5 Channel Upgrade

For information about channel upgrade from OES 11 to OES 11 SP3, see Channel Upgrade from OES 11 SP2 to OES 11 SP3 in the OES 11 SP3: Installation Guide.

9.1.6 AutoYaST Upgrade

AutoYaST upgrade enables you to upgrade to an OES server without user intervention.For more information, see Using AutoYaST for an OES 11 SP3 Upgrade in the OES 11 SP3: Installation Guide.

9.1.7 Configuring WINS and Sites in an Upgrade Scenario

After you upgrade your server to OES 11 SP3, the server reboots and you are prompted to configure additional features like WINS and Sites. This can be done using the DSfW Configuration Wizard.

IMPORTANT:You are prompted to configure these features only once. If you fail to configure these features during the first instance, you will not be able to configure these features later.

  1. Enter the authentication details in the login dialog box, depending on the scenario in which you are provisioning, then click OK.

    Provisioning Scenario

    Authentication Details Required

    Non-name-mapped, forest root domain

    The current domain credentials.

    Name-mapped, forest root domain

    The current domain credentials and the tree admin credentials.

    Non-name-mapped child

    The current domain credentials, the parent domain credentials, and the tree/container admin credentials.

    Name-mapped child

    The current domain credentials, the parent domain credentials, and the tree/container admin credentials.

    Additional Domain Controller

    The current domain credentials and the tree admin credentials.

    IMPORTANT:If you are installing a first-level child domain in a non-name-mapped scenario, the tree admin and the parent domain credentials are the same.

  2. Select the feature that you want to configure, then click Next.

  3. On the task list page, click Run to manually execute a task or click Run All to execute all the tasks sequentially without any manual intervention.

9.1.8 Troubleshooting

Samba cache File Corruption

After upgrading, you may encounter a Samba cache file corruption issue. Follow the instruction documented in Error Mapping SID to UID to resolve the error.

Upgrade Fails

If upgrade to OES 11 SP3 fails during the post-configuration phase, then the upgrade tool will not retry and upgrade of other OES components will continue. You must rerun the upgrade scripts based on the upgrade scenario.

Upgrade to OES 11 SP3: Use the script /opt/novell/xad/sbin/upgrade_dsfw.pl

You must also ensure that the kerberos ticket is up-to-date. To obtain the domain administrator's ticket use kinit.

kinit <Administrator Name>