The_wee_fella

Hi all I have successfully completed a migration from V5 to V6 I did have some initial issues which are partly due to unclear documentation and partly due to me not digesting the information but in general it works reliably Here are a few key points 1. Internet access. Unless you create offline repositories or go for the full blown Apache HTTP Proxy installation all installation steps require internet access to ESET servers Agent - Offline Install library required Eset Endpoint - Offline Install library required Activation - Check out some of your licences to an offline activation licence on the RAS Signature Updates - Set up an update mirror on a computer/server with ESET Endpoint or file security and access the internet then us ethe client to create a mirror for others to update from I initially objected to this and created a mirror for updates but decided to go full internet I only manage 80 computers, almost all laptops, so when out of office I was happy for them to get updates directly from ESET rather than from my mirror which I would have to expose to the internet fro access. This particularly applies to our globe trotting staff. I did however open port 2222 on the CISCO firewall and allow the machines to report in to the ERAC via a publicly registered DNS name. For particular machines that I did not want to have internet access I used our proxy service to block them from all but ESET and some Microsoft background services 2. ESET remote administrator name on the certificate and agent policy I was having trouble getting agents to communicate particularly from outside of the office ESET support helped me identify the problem which was:- The communication between the Agent and the RAS is protected by a certificate that you create on he console . You MUST use the same RAS name in the Agent policy as you have entered in the certificate I had registered the local computer hostname for the server in the certificate then changed the name for the agent to be the externally registered DNS name creating a mis-match. The good news is that in your certificate you can register multiple names for the RAS for it to accept e.g. IP address Local host mane Fully qualified domain name e.g hostname.domain.local External DNS name Actually in the end I just used the External DNS name for both internal and external connections for consistency and registered that DNS name in our internal DNS Hope that makes some ones learning curve faster than mine Cheers