I have read the article you shared but I am still not sure how to approach this without losing access to WAN agents. My main concern is regarding the proxy chaining. will have to be upgraded manually somehow)Īnd 10 Apache HTTP Proxies that are set up in each remote office where we have limited Internet/Satellite access (each proxy runs on a dedicated server, which will also have to be upgraded manually somehow) PROTECT's Apache HTTP Proxy (will be uninstalled/upgraded during the v9-v10 upgrade)ĭMZ Apache HTTP Proxy (runs on a separate server. Just to summarise, we will have to consider 3 proxies here: How to test this best, just to make sure that the current proxy chaining config will still work once PROTECT has been upgraded? I am therefore assuming that we will immediately lose access to the WAN agents once we start the PROTECT upgrade, is this correct?Īre you suggesting to create these new Bridge policies in advance (while we are still on PROTECT v9 and while the Apache Proxy is still running)?Ĭan we apply these new Bridge policies to WAN agents that currently use Apache Proxy policies, before we start the PROTECT upgrade? Rootkit detection and cleaning module 1033 Ĭryptographic protocol support module 1082 Īs mentioned in the article you shared, the PROTECT Apache HTTP Proxy component will be uninstalled during the upgrade. The ESET Service (ekrn) is up and running.Īntivirus and antispyware scanner module 1605.2 We have rebooted all the affected servers but the error did not clear. The first server started reporting this on Friday after a reboot. Hello, we noticed that real-time file system protection is non-functional on about 15 servers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |