LukasSMSFT
@chrlie I wasn't able to reproduce the behavior. One more question: Did you reboot the machine after running the Set-ADObject command before installing the February 2023 SU? This would explain the behavior as to logic to update the serialNumber attribute was executed by the AD Topology Service and everytime the service is started. This was changed with the February 2023 SU as the logic was removed.
Yes, I did reboot the machine after Set-ADObject and prior to February SU installation. That could indeed explain why the version number was changed. I thought the change was made by the update installer, but if the service itself was the source it would make sense. Thanks.