RAS v2 stopped updating v2.7 clients

[Ritmo2k]

Hi,
It will update v3 clients though? The 2.7 clients can update from eset to, just not my RAS anymore? The mirror is setup in RAS, not through a client on the RAS machine.

Any ideas?
Thanks,
jlc

[Marcos]

ESET Remote Administrator creates a mirror for ESS/EAV. NOD32 v2 will not update from it.

[Ritmo2k]

Well thats an easy fix, but a bizarre limitation for sure! Hopefully a v3 client can create a mirror that v2 clients can use...

Thanks!
jlc

[Marcos]

{QUOTE-> Well thats an easy fix, but a bizarre limitation for sure! Hopefully a v3 client can create a mirror that v2 clients can use...

Thanks!
jlc <-QUOTE}

If you want to create a mirror for v2 and v3 on the same computer, you'll need to install ERA to create a mirror for v3 and NOD32 v2 in LAN to create a mirror for v2.

[Ritmo2k]

Thanks Marcos,
Can't make sense of that limitation? I intend to only have one v2 client on our exchange server so i will just let it update from the net.

Appreciate the confirmation.
jlc

[webyourbusiness]

{QUOTE-> ESET Remote Administrator creates a mirror for ESS/EAV. NOD32 v2 will not update from it. <-QUOTE}

oh for crying out loud - WHY?!??!

This is insanity - it needs to be backwards compatible for mixed OS installations.... not making it so is really losing the plot...

[Ritmo2k]

Heh, not a problem here anymore...

We ripped out v3 clients completely! The list of things it was breaking on different machines was getting to long.