Endpoint Protection

 View Only
  • 1.  SEP 11 Package Upgrade Settings

    Posted Jun 14, 2011 10:55 AM

    I want to assign a SEP 11 Client Package to a Group in the Management Console, but not download the package from the Management Server. Instead I would like to use a local file share at that site to avoid copying the package over the WAN.

    Does anyone know why the alternate location is limited only to HTTP or HTTPS? In other words, why can't I put a local server share name like \\servername\sep_packages? The alternate download location only accepts http or https at the beginning of the path.

     

     

     



  • 2.  RE: SEP 11 Package Upgrade Settings

    Posted Jun 15, 2011 01:40 PM

    It only allows you to share the package Via IIS.

    Follow this link

     

    https://www-secure.symantec.com/connect/articles/how-auto-upgrade-remote-site-clients-using-iis



  • 3.  RE: SEP 11 Package Upgrade Settings

    Posted Jun 16, 2011 02:46 PM

    Rafeeq,

    Thanks for the info. Though this is a valid solution, I still don't understand why there is no option to simply use a server share also. We have multiple locations and use DFS to replicate software to each site. According to the instructions you posted, we would now have to spin up a separate web server at each location, configure it, test it and maintain it just to install client packages. Seems like a very complicated solution to an easy problem. Why not just make the option available for using a local server share along with the option to use IIS? That way if the file server is local, it will reduce the WAN traffic the same as pulling it from a web server..?



  • 4.  RE: SEP 11 Package Upgrade Settings

    Posted Sep 07, 2011 08:43 PM

    Have you tried just making a standalone client installation package and saving that to a fileshare location? I know many do it that way and then use a 3rd party program like Altiris Deployment Solution for deploying to a large number of computers.