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

Endpoint secV9 and Standalone computers, not showing in enterprise console

Scecconello

Hello,

I've setup and configured a Windows 2003 r3 sp2 standard server, with Endpoint v9 and Enterprise console v4.

Due to business needs, i need to allow some non-domain\non-network hosts to update via this server.

I've followed the KB regarding the installation and configuration of a standalone computer using my server as update repository, everything is fine.

I've used the standalone package on the sophos website and then change the update repository to my http://PublicIP server

But, i dont see the external hosts in the enteprise console .

What i miss ?

Searching in the KB, i've found an article about creating a self installer package for standalone computers, but it's a dead end ( page 404 )

Thanks in advance.

Stefano

:726


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

    Thanks

    Btw, i've followed the kb for the V3 and created a customized package for this kind of clients, it gets the default policy\software configuration as the lan computer, ad example the udpate path is \\SERVERNAME\SohposUpdate.

    If i'm correct i nedd to:

    On UPDATE MANAGER

    1. create a new subscription ( ad.ex ExternalClients )

    2. modify its setting to download the client for the os needed

    3. Associate it on my update server ( it's all on a single server ),

       3.a accessing on the modify option on the update server

       3.b tab subscriptions: moving the new subscription to the right pane

       3.c tab distribution: selecting the new subscription from  the drop-down end adding a new share ( \\SERVERNAME\Webupdate )

    now when i update the subscriptions, it will put the downloaded files on \\SERVERNAME\Webupdate\CID\...

    then,

    4. create an update policy ( ex. webupdate )

    5. modifying it providing the update path in a http way: HTTP://PUBLICIP/Webupdate with user\psw .

    6. create an antivirus policy ( ex. webclients )

    7. modifying it with the needed permissions

    now i should have the custom policies for my external clients, then i can follow the kb for creating a standalone package exporting the two newly-created policies .

    Is it correct or i'm missing something ?

    Thanks in advance

    Stefano

    :749
Reply
  • 0

    Thanks

    Btw, i've followed the kb for the V3 and created a customized package for this kind of clients, it gets the default policy\software configuration as the lan computer, ad example the udpate path is \\SERVERNAME\SohposUpdate.

    If i'm correct i nedd to:

    On UPDATE MANAGER

    1. create a new subscription ( ad.ex ExternalClients )

    2. modify its setting to download the client for the os needed

    3. Associate it on my update server ( it's all on a single server ),

       3.a accessing on the modify option on the update server

       3.b tab subscriptions: moving the new subscription to the right pane

       3.c tab distribution: selecting the new subscription from  the drop-down end adding a new share ( \\SERVERNAME\Webupdate )

    now when i update the subscriptions, it will put the downloaded files on \\SERVERNAME\Webupdate\CID\...

    then,

    4. create an update policy ( ex. webupdate )

    5. modifying it providing the update path in a http way: HTTP://PUBLICIP/Webupdate with user\psw .

    6. create an antivirus policy ( ex. webclients )

    7. modifying it with the needed permissions

    now i should have the custom policies for my external clients, then i can follow the kb for creating a standalone package exporting the two newly-created policies .

    Is it correct or i'm missing something ?

    Thanks in advance

    Stefano

    :749
Children
No Data
Unfiltered HTML