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

Sophos Enterprise Console "Reommended" change

ChristianN

Good morning,

we are using a Sophos Enterprice Console V5.1.0.1839 with no computers in the managment.

We only use this Console to download the Sophos Updates.

To Support Windows 8 we would like to change from "Windows 2000 and above" "10.0 Recommended" to "10.2 Recommended".

Does this have any effect to the older Sophos Clients in the network? Again, we haven't any computer under the computer managment tap and the Enterprice Console is not spezial configurated.

Thanks,

Christian

:36633


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

    I see - then it's as bad as I feared :smileyvery-happy:.

    I'd call it a communications challenge. And the smiley doesn't actually mean it's funny. Can't see how the clients that use the stand-alone installer can be managed - the SA is what it is and comes without RMS. 

    Let's assume there are some departments which do use SEC. Then 

    • the clients have to be installed by or from this SEC or an appropriate package
    • the clients could use "your" IIS as primary update location - but the admin would have a hard time to configure a policy which points to S009
    • version changes require a coordinated course of action

    Thus the owners of "owner-managed" clients need to know the available versions and corresponding current locations. SEC admins just need to know the available versions and are free to use whichever they want of these given they provide their own update location - but if they want to use the ("your") IIS as primary or secondary location for their clients a concerted action (and perhaps some hacking) is necessary.

    Christian

    :36905
Reply
  • 0

    I see - then it's as bad as I feared :smileyvery-happy:.

    I'd call it a communications challenge. And the smiley doesn't actually mean it's funny. Can't see how the clients that use the stand-alone installer can be managed - the SA is what it is and comes without RMS. 

    Let's assume there are some departments which do use SEC. Then 

    • the clients have to be installed by or from this SEC or an appropriate package
    • the clients could use "your" IIS as primary update location - but the admin would have a hard time to configure a policy which points to S009
    • version changes require a coordinated course of action

    Thus the owners of "owner-managed" clients need to know the available versions and corresponding current locations. SEC admins just need to know the available versions and are free to use whichever they want of these given they provide their own update location - but if they want to use the ("your") IIS as primary or secondary location for their clients a concerted action (and perhaps some hacking) is necessary.

    Christian

    :36905
Children
No Data