Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 2135 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How-To Manage "remote" clients with my main SEC?

JFC
Hello, Sorry for Noob Q. I have SEC and clients (LAN) protected and reported in the Console. But I have about 30 clients outside the office (remote location using another ISP). How to protect them and make them report to SEC? I tried to follo "... Protecting Home Users" guide but Iam a bit confused. I setup Web CID (IIS) but Iam stuck at creating package installer. Also I dont know if the clients will connect back to SEC Using: SEC 5.2 Remote locations are far away from our office so the question... Best regards, JFC (not the chicken)
:39263


This thread was automatically locked due to age.
Parents
  • 0
    I was able to create a install package. On workstation update, application control, tamper protection work OK.... but I still dont see that workstation at SEC? It seems SAV + Sophos Autoupdate got installed... no more. Is it something missing? Ports 8192-8194 are open. Using Public IP (primary server): http://public_ip/sophosupdate (alias in Microsoft IIS) Again, update is working but not showing on SEC... Regards, JFC (**bleep** I miss the chicken)
    :39267
Reply
  • 0
    I was able to create a install package. On workstation update, application control, tamper protection work OK.... but I still dont see that workstation at SEC? It seems SAV + Sophos Autoupdate got installed... no more. Is it something missing? Ports 8192-8194 are open. Using Public IP (primary server): http://public_ip/sophosupdate (alias in Microsoft IIS) Again, update is working but not showing on SEC... Regards, JFC (**bleep** I miss the chicken)
    :39267
Children
No Data