This section helps you understand the types of upgrade, prerequisites for upgrading, and the upgrade process.
Before upgrading to OES 2018 SP1, if the file smb.conf.oes2018-upgrade-save exists, ensure that it contains the DSfW Samba configuration. If it does not contain the DSfW Samba configuration, copy the configuration information from the smb.conf file by using the following command:
cp /etc/samba/smb.conf{,.oes2018-upgrade-save}
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.
Before running the upgrade process, ensure that time is synchronized between all the servers in the replica ring.
If you are upgrading a CDC or an ADC to OES 23.4, you must also upgrade all the other domain controllers (FRD, ADC, and CDC) in the DSfW forest to OES 23.4. Mixed mode configuration is not supported in OES 23.4.
If such a configuration is attempted, a message is displayed warning you to upgrade all the domain controllers to the same version of OES for the domain to become operational.
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
in the OES 23.4: Installation Guide.
AutoYaST upgrade enables you to upgrade to an OES server without user intervention. For more information, see Using AutoYaST for OES Upgrade
in the OES 23.4: Installation Guide.
After you upgrade your server to OES 23.4, the server reboots and you are prompted to configure additional features like WINS and Sites. This can be done using the DSfW Configuration Wizard. If you are configuring DSfW at runlevel 3, you will not be prompted to configure additional features like WINS and Sites. In this case, you must start the X server and launch the DSfW Configuration Wizard manually using the command: /opt/novell/xad/sbin/provision_dsfw.sh
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.
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.
Select the feature that you want to configure, then click Next.
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.
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.
If upgrade to OES 23.4 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 23.4: 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>