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

home use for licensed sophos customers

johnd

I have deployed a test standalone installer package using the enterprise console (article 67504) with updating pointing to a web cid, sophos home installation is updating properly, the primary server details, username and password are "grayed out" which is basically exported this policy from our enterprise console. My question is what if an employee that was issued by this home install will be terminated or will not be working anymore in our company, how can I revoke the home install. Support told me that I have to manually remove the home install from the client machine, which is a pain. Any other advise on how we can reclaim this home install or somehow make their home install not to work anymore. Our network uses active directory, web cid created from IIS.

:5864


This thread was automatically locked due to age.
Parents
  • 0

    Hi John,

    I've thought about this a lot here as I'm in exactly the same situation. My thoughts are leaning towards creating a simple web-app that looks at the client ID you can see from the initial connectionrequest that SAU uses to connect to the webcid (it has the machine name in it - look in the web site logs, you can see this easy enough). By using an app in an application pool, it should be possible to lookup the client ID's in a table and redirect to nothing if they are 'blacklisted'. Next problem I have is that I set Sophos databank as a secondary update site so if it fails from my CID, it'll still update from the databank. So, I'm also toying with having an out-of-date CID and redirecting to this when blacklisted. That way, it'll update from us but remain at a fixed point and eventually after 90 days, they'll get an out-of-date security alert warning from windows. It's still in thought process at the moment but anyone out there with basic IIS app skills should be able to knock something up easy enough.

    Matt

    :5885
Reply
  • 0

    Hi John,

    I've thought about this a lot here as I'm in exactly the same situation. My thoughts are leaning towards creating a simple web-app that looks at the client ID you can see from the initial connectionrequest that SAU uses to connect to the webcid (it has the machine name in it - look in the web site logs, you can see this easy enough). By using an app in an application pool, it should be possible to lookup the client ID's in a table and redirect to nothing if they are 'blacklisted'. Next problem I have is that I set Sophos databank as a secondary update site so if it fails from my CID, it'll still update from the databank. So, I'm also toying with having an out-of-date CID and redirecting to this when blacklisted. That way, it'll update from us but remain at a fixed point and eventually after 90 days, they'll get an out-of-date security alert warning from windows. It's still in thought process at the moment but anyone out there with basic IIS app skills should be able to knock something up easy enough.

    Matt

    :5885
Children
No Data
Unfiltered HTML