Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 2134 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
    Ports 8192-8194 are open and forwarded. Policies get applied but workstation don't appear in SEC. I insllated a Linux/Ubuntu using ordinary SAV install just pointing Update Source to SEC's IP and I can see it in SEC. But Windows clients dont. Do I need special parameter to include in order to manage workstations? Primary Srv: http://public_ip/sophosupdate (working Microsoft IIS alias) Best regards, JFC
    :39271
Reply
  • 0
    Ports 8192-8194 are open and forwarded. Policies get applied but workstation don't appear in SEC. I insllated a Linux/Ubuntu using ordinary SAV install just pointing Update Source to SEC's IP and I can see it in SEC. But Windows clients dont. Do I need special parameter to include in order to manage workstations? Primary Srv: http://public_ip/sophosupdate (working Microsoft IIS alias) Best regards, JFC
    :39271
Children
No Data