evasion

Success: changed details in customsettings.ini to show FQDN instead of single label domain name: JoinDomain=FQDN DomainAdminDomain=FQDN NetSetup.log shows success code now, also allow reuse of computer name works. thanks to reading this : https://learn.microsoft.com/en-us/answers/questions/2192023/window-11-24h2-cant-join-domain?page=14#answers

When replacing old computers with new, usual procedure is to image new computer with existing old computer name. That way new computer is placed in the same OU as the old one. Been like that since days of Windows XP. Now this latest version of Win11 24h2 is not happy with resolving domain name during imaging. NetSetup.log shows this: " NetpJoinDomainOnDs: Domain name is invalid, NetpValidateName returned: 0x54b". So domain join fails @ Recover from domain step. When using powershell script inserted instead of that step, it will join domain.

permissions do exist on the account used to join domain, it has delegated role. Domain security policy does allow re-use of existing computer accounts. As I said power shell script will join domain if existing computer account is re-used. "Recover form domain" step in task sequence no longer works as before if existing account is re-used.

Pretty much the same experience with 24h2 version. REcover domain TS fails (seen in logs) but script reports success, domain join does not happen if using existing computer name. No such issues with previous version 23h2. However, PS script does the trick, only problem is having to input creds manually, which is no longer "zero-touch" approach.

At long last, with some help from Microsoft, I have a solution to this specific "send as" issue. As described here, I only had to change this registry value (Office 365): Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\Profiles\Outlook\0a0d020000000000c000000000000046] "00033d1b"=hex:00,00,00,00 which changes Address Book to "Custom", and as a result everyone can now send from delegated mailbox or shared mailbox, no problems. If, this setting is reverted to "01 00 00 00" which enables Start with Global Address List, then "send as" no longer works as intended. It only took 3 months to arrive to this simple fix. Why Outlook behaves in this way, I have no idea. No need to switch to new outlook or use web mail as workaround.

re replacement, it's not a cluster but 2 hyper v servers. have set up failover, and testing currently. Yes, diagnostic work has limitations, and in case of suspected hidden firmware bug, even more difficult. All hardware tests on both cluster nodes have passed.

Mellanox ConnectX-5 adapters. Back to back on 25 Gb link. HC cluster is now only used for testing in the hope it will reveal root cause of RHS crashing. When this service which is responsible for high availability is randomly crashing, it's a game over.

not sure if I'm on the right post, but similar updates related glitch had caused lots of headaches/stress. HC cluster with 2 nodes only 2 years old, was updated in January, after engineers checked all pre-requisites. On the day updates were completed, no problems, everything ticked green. Next day, random VMs were hanging, accessible only in Hyper v manager, while their network card was unresponsive, any attempt to disable/enable in hyper v manager RDP was just not responding. Event logs pointed to RHS service, Event ID 1146. Such VMs could not be controlled, and only way to recover them was to put the node in standby, drain roles if possible, and reboot the node. So much for failover clustering. Then when node was up, the VM which was locked by RHS, would sometimes work, but had to be fixed with chkdsk, and 3 VMs had to be rebuilt using ISO, or partially restored from backups. This instability continued several weeks, sometimes VMs would lock up overnight while backups were running. Good response received from support engineers, sometimes working out of hours or weekends. In the meantime rental hyper v servers being used to host all VMS, as original cluster is unstable, even after full rebuild of 2019 datacenter OS. Anyone with helpful input welcome, because root cause of "The cluster Resource Hosting Subsystem (RHS) stopped unexpectedly" is still not known? There are some event log errors pointing to Mellanox firmware...

What a surprise this morning, "send as" works fine just as it used to before this glitch last week. GAL search also works fine as it did before. Something got fixed in exchange online in the meantime, maybe it took longer for power shell command to apply GAL update.

Yes, root cause is that GAL search scope in Outlook client is now limited to only one address book. And yet search filter in default GAL is not changed, search just stopped working Monday for no apparent reason.

I don't know how this can be fixed, if GAL search no longer works as intended. It still has the same "pre canned" filter (catch all) which is supposed to find shared mailbox which exists in offline address book, down on the list under GAL.

Same issue here. think that root cause is that Outlook cannot enumerate GAL anymore. When "sending as" from shared mailbox, you have to go to to search for your shared mailbox account clicking 2x on From button, and refresh that way, otherwise you get error as seen above. Giving "send on behalf" permissions does not help. Because GAL search works fine in OWA, it can be workaround for while until root cause is fixed. And the root cause is in Outlook client, not being able to resolve GAL search anymore. Instead having to go for offline address book is not a solution, because your default online GAL must be up to date before it syncs with offline version. It's like your offline address book is now more up to date, which is weird. For some reason new version of Outlook client (slide toggle button in upper right corner) will resolve GAL search better and be able to send as, from shared mailbox, but the shared mailbox is no longer available in left pane in new Outlook. Adding new account (shared mailbox, delegated to "send as") will fail. Reverted to old version because new one is just like half baked cake. Nice looking cosmetically, but lacking in functionality. Not to mention that email profile adjustments in control panel don't work with new version.

There is however, this anomaly: "Turn off autocorrect misspelled words" under Regional and Language options (User Configuration, Administrative Templates, Control Panel): You will have to do the opposite of what description says, to make it work. Tested and confirmed! I do not understand how designers of GPO templates pass quality control stage.

discovered that this is just as good: C:\Windows\System32\msra.exe /offerra on local network where it can be controlled with gpo.

Another test today resulting in 50% success. One user can run it, another can not. So why is it that new version is so unreliable ?