roesch

Yes it fails with "Could not connect to server" message.

Thanks for your help so far, after testing for a day now the second profile still doesn't get applied. NOD keeps trying to use the default profile and therefore cannot connect to the server from outside of the network. Any other ideas? The Mirror is created with Eset FileSecurity on the server and working fine.

Thanks for the help! I will try this but have a general question. Policies and tasks are only applied/executed when the client is connected to the network, right?

I use both ERA and Endpoint Version 6

Hi there, I setup two update profiles following the instructions of this article: hxxp://support.eset.com/kb3621/ The default profile is set to update from the mirror, which is working perfectly. If the client cannot connect to the mirror it should automatically update from the internet. The policies are applied fine, but if I disconnect the laptop from the network and press "Update now" I get "Could not connect to server". So I guess the second profile is never applied? I set the Server to automatic and entered my licence username/password below. Can someone explain to me whats going wrong or how to do it? ;-) Thanks, Roesch