MicrosoftZappBrannigan145 , if you provide some context, I can try to assist with some specific advice.
However, in general I have found this page we are commenting on now to be useful. If you are running on a fully updated environment, your application does not need to make any changes and will continue to work because the requests will be promoted to the required level before they are sent, therefor they will not be rejected by the server which expects a higher level of connection integrity than used to be normal. If you are running in a mixed environment (supported OS versions that have been patched up to current level and unsupported OS versions that no longer receive patches), then your options are to:
* get your software patched or reconfigured so that connections are made using the required connection integrity level,
* freeze your patch levels at the point before 14/Mar/2023 and disable the hardening via the registry, or
* update the environment your application is running on so it is not mixed.
What is possible for reconfiguration will depend on how the software was coded. It may be configurable from dcomcnfg if you are lucky. The connection integrity level may also be hard coded in the application, in which case you don't have an easy option in a mixed environment, and it is not a guarantee that you can fix all problems. For that you need to be running on supported environments, or in frozen or unsupported environments.
In my own personal case, our application uses a hard coded connection integrity level that is no longer high enough, but because the majority of deployments are on modern Windows versions, we don't actually have to do anything, the application is still working fine because the OS is promoting the connection integrity level to the now required level. We do have one instance of a mixed environment, so it has been frozen pre-14/Mar/2023 as it is an offline environment and it is being updated/replaced as we speak, so it will not be an issue in the new system.
