Finally got off the phone with ESET and confirmed what had to be checked/unchecked to get the config I needed and they have stated during a push deployment from the v2 RAC, you *can not* configure anymore options other then RA server and mirror server. Once deployed you then configure all the rest. In my test setup I have confirmed this to work as suggested. Problem is this: How does one stop the v3 client thats being deployed on server's from scanning edb/mdb/logs and interfering with http traffic? If you deployed this client to an MS SQL server, you could destroy that SQL install completely as it installs, starts unmodified and then waits until you deploy a config. Scanning log files and db's is very bad practice, even by ESETs own reco! Ok, who wasn't thinking in the dev team? Whats a workaround? How can you deploy it safely on these type of machines?