Tweet
Problem: With Windows Server 2022 systems, when a proxy server is configured and then disabled in the operating system the once configured residual settings remain within the registry and continue to have an impact on traffic despite being disabled in the proxy settings dialog seen below. Because they are evaluated, if the proxy doesn't function some webservices are impacted. We has issues with RA, the Folder and Doc Type selection in OM Settings, and problems with connections to the OPC communication via certain behaviors. This also impacts the esig webservice and the ability to login to WFX and QRM.
Note: even if you enable the use a proxy server checkbox, erase the values out, and then uncheck the box the settings remained residually within the system.
Resolution: I was able to use sysinternals process monitor to sniff out the problematic registry keys causing the disruption to our system and clear out the values. I have developed the below clean-up script that can be ran from an Administrative Command Prompt to clean-out known problematic areas within the registry. Make sure to make a backup of the keys before proceeding and to report any new or unknown locations so that we may add them to our script.
RegCleanup.txt
Note: even if you enable the use a proxy server checkbox, erase the values out, and then uncheck the box the settings remained residually within the system.
Resolution: I was able to use sysinternals process monitor to sniff out the problematic registry keys causing the disruption to our system and clear out the values. I have developed the below clean-up script that can be ran from an Administrative Command Prompt to clean-out known problematic areas within the registry. Make sure to make a backup of the keys before proceeding and to report any new or unknown locations so that we may add them to our script.
RegCleanup.txt