Stranger Update behavior

Hi,
I have updated the repo on the server from 10.2 to 10.4.
During the update i got a message about some UI layouts being unsupported suggesting that i run “DeadlineCommand.exe -MigrateMonitorlayouts” command.
The DB and Secrets were all preserved during the update. Auto update of clients is enabled.
The server was rebooted after the update.
However when my clients get auto-updated they are no longer able to connect.
The error states that the client’s protocol is ver.7 and the server’s protocol is ver.6
What am i missing?

All sorted out! The short story is the Client components on the repo needed an update as well.

The longer one - the in-place update utterly failed with random certificate and other errors and it became a clean re-install with none of that RCS and security stuff.

Interesting! When you say “security stuff”, do you mean you had to disable SSL for client authentication? (during your repo database re-install?)

What OS do you run the database on?

Just curious as I have had upgrade issues (Upgrade from 10.2.1.1 to 10.4.0.10 - Deadline Client error connecting to db - #11 by Jason_Ian_Yee) and it would be of interest for the authorities to know there have been multiple victims.

thanks!

Server 2019
I ditched SSL, certificates and went with direct connection instead of RCS.
The errors i was getting with in-place update we related to secrets configuration. It told me to run the configuration afterwards, but that didn’t work either. Hard to tell if it was an actual software issue or a user error. As far as i can tell there isn’t much to mess up, but i’m also far from having a comfortable grip on all the ins and outs of DL.

Yeah, I think I will need to disable ssl for now. Never seen this issue before so did 2 days of troubleshooting user-related issues. Now I think it must be related to the10.4 mongodb driver upgrade and/or .NET 8.0 upgrade .