Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 1636 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

WEB Cid. Message Relay via ISA 2006

StarRefrigerati

I was wondering if anyone could assist me on publishing an internal web cid on ISA 2006 Server for remote clients to update from

I would also be looking for help on using Message Relay to allow remote clients to contact the internal enterprise console if possible. I have seen the article on using a DMZ, but I dont have a DMZ here Thanks in advance

:2224


This thread was automatically locked due to age.
  • 0

    Hello

    had to look up what ISA 2006 is so I don't know about it's peculiarities but I guess what's been said in this forum about WebCIDs should be usable.

    First question is how you get the configuration to your remote clients (are they already deployed or do you plan to do so? How?). And are you using SEC4? As for the Message Relay I think configuring message relay computers might be the article you want.

    Christian

    :2225
  • 0

    The remote clients would be deployed via the internal network(VPN maybe) and then out in the wild they will receive updates from Sophos, but as said it would be nice if they could report to the EM. V4 is being used. Thanks for the reply. I have had a read through the message routing but I am struggling with the concept. I will give it another go

    :2226
  • 0

    You could use an updating policy with the primary location UNC (which would be used when the clients are "inside" or connected via VPN) and the secondary http (although http might be faster than UNC via VPN).

    If you configure RMS in your WebCID to use the Message Relay once the clients have updated from it they will always use the relay (whether outside or inside). Assuming the ISA can also be used from the inside this should not be a problem. 

    "Message Routing" can be confusing at first because it involves also configuring a CID and configuring RMS. The former is also used when you want to install default policies (e.g. for unmanaged computers) or want to use scanning options which can't be set using the console the latter e.g. of you want to "move" clients from one management server to another.

    Christian 

    :2236
Unfiltered HTML