The "failing" LDAP connection during the (totally unnecessary, as you say) LUM reconfiguration also happens on about half of my OES2018SP3 upgrades. I have not found any reason yet why it sometimes happens, and sometimes not, but yes, it is luckily cosmetic.

Nonetheless this is yet another perfect example, why the whole upgrade process needs to be revisited, and needs to get rid of all those unnecessary steps, especially blindly reconfiguring services for absolutely no reason, from notoriously unreliable sources (the mentioned sysconfig files).

And yes. We really don't need to unnecessarily prolong the whole upgrade process (and as such, customer downtime) by sometimes hours for the imanager plugins. Those can be done in the background... 

I yesterday upgraded a DSfW server from OES2023 to OES23.4. There I hit several problems.

First the Edir upgade script crashed because I had overseen the line UPGRADE_FROM="OES2018_SP3" or had looked too early into the file, when it did not contain a line starting with UPGRADE_FROM. Thanks to M. Rosens input in the thead "Restart / Retry 2nd stage OES23.4 upgrade" it was quite easy to correct the entry (and some others) and afterwards run the second stage of the upgrade without errors.

Second  - after the upgade smbd did not start. This is due to the fact, that the new version of smbd tries to connect to the non existing printers and throws an error and exits. With the help of Google I added the line "disable spoolss = Yes" to smb.conf, which bypasses this problem. Since this change smbd and the whole xad services start without errors.

Third - if you are still using Netbios and the Windows browser service  - you will notice, that browsing does not really work after the upgrade. This is due to the fact, that the upgrade raises the server minimum protocol level to a value above NT1. The effect of this is, that nmbd still starts his browser process and proclaims itself as "domain master browser" and as "local master browser", but no Windows machine is able to read or retrieve the browser list from nmbd. Depending on the version of Windows, this leads either to a very reduced Network Neighborhood or to a message that no Network can be found or reached. If you want to use Netbios and the Windows browser service you can set "server min protocol = NT1"  in smb.conf, then you are at the same state regarding browsing as in OES2023. Another option would probably be, to remove or comment the lines domain master = Yes  and preferred master = Yes from smb.conf, but that I did not test. This should hinder nmb to advertise itself as master browser, so that other machines could chime in and acquire the master browser status and show a more complete network neighborhood.

Fourth - this machine has also iprint ipsmd installed. Immediately after the upgrade I could prínt. But this morning no user could print. I checked the service and it was up and running. A restart has restored services for the users - I'll see, if that remains so.

My fifth problem turned out to be a switch, which crashed or hang approximately around the time the update was applied. Of course machines behind that switch could not logon to the DFSfW server, but that had nothing to do with OES upgrades and not even touched it. But I was quite upset, as I noticed, that the machines behind the switch, which are not members of the DSfW domain, could not logon.

Now all seems fine, but the first 3 issues were quite time consuming and annoying, of which the first and the second should not happen at all.

Hi All, 

I would like share an update, OpenText has released today an Open Enterprise Server 23.4 ISO Update addressing some of the prominent install/upgrade issues. The new ISO is nowavailable in the SLD.
Here is the official link https://www.microfocus.com/documentation/open-enterprise-server/23.4/oes_readme/t4oj67lshizv.html 

Thanks, Ramesh 

At least a part of the problems shold be solved by this new ISO, so that is good news.

For me in SLD it still shows the ISO from 2023-10-19 with the checksum bfb4c847484fa7df24205fe9b618bf11d089a61175b300f61cdbedf23bcdf78f.

Any other way to get the current ISO? Because I tried to upgrade a OES2018SP3 to 23.4 one hour ago but it was missing dependencies so I aborted the upgrading process.

Any news on that ?

same here, but that wasn't what was downloaded,  it had a different SHA-265 checksum when I checked it after the download, that was also 2MB less than the original that matched the checksum you displayed

6eb493dfeb53036c26a57af8838abaf009da0e8c1953da80ee7f50d0fbfe630b

they certainly did NOT update those details on SLD, just slid the new ISO in there.

Can confirm. They only swapped the file without updating the item on the page. Sad...

Update OES 23.4 ISO is available in SLD, but it still reflects the older sha256sum. We are working on updating it.
You can download the updated ISO and compare with below sha256sum

Update OES23.4-DVD-x86_64-DVD1.iso sha256sum:
6eb493dfeb53036c26a57af8838abaf009da0e8c1953da80ee7f50d0fbfe630b

Hi all,

I'm checking with the internal OT team on the checksum issue.

Best regards