How to install Package Service

book

Article ID: 179747

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

 

Resolution

Question
You want to install package services to a machine running the Symantec Management Agent and need instructions.

Answer

How to setup a New Site Server with Package Services

Definitions:

A Package is a group of one or more files that can be delivered to a managed computer. Packages are often for Software Delivery

A Site Server with Package Services is a file server with additional software installed to allow Symantec Management Agents (agents) to download packages. At smaller remote sites, package services may be installed one file server to reduce network load. At larger sites, package services may be installed on multiple file servers, for load balancing and continuity. A computer with package services can make packages available via HTTP/HTTPS (which requires Microsoft IIS) and/or via Windows file sharing.

Prerequisites:

The following are required of a computer to become a site server running package services.

  • The Symantec Management Agent (agent) must be installed, preferably the latest version
  • The computer must be managed by the Notification Server (NS) for which is to become a site server
  • A basic Inventory must have been run after IIS was installed, this will update its inventory data on the Notification Server (NS)
  • The computer must be running a supported version of Windows OS
  • In order for packages to be via HTTP/HTTPS, then the IIS must be installed

 

To configure this computer to be a site server with package services:

Note: If you have not configured sites and subnets, see Overview of Site Services with Notification Server 7 (52567)

  1. In the Symantec Management Console (SMC)
    1. On the menu bar: select Setting > Notification Server > Site Server Settings
  2. In the Site Management screen:
    1. In the left-hand pane,
      1. Navigate to: Site Management > Site Servers (if desired)
      2. In the toolbar: select New > Site Server
    2. In the Select Computers dialog box
      1. In the left hand column, select the computer that you wish to make a site server,
      2. In the middle, click the ">" icon,
      3. In the right-hand column, note that the desired computer is now listed
      4. Click OK
    3. In the Add/Remove Services window,
      1. Check Package Services
      2. Click Next
      3. Click OK

To assign this site server to a site

Note: You only need to do this to have a site server serve a site which it does not already belong.

  1. In the Symantec Management Console (SMC)
    1. On the menu bar: select Setting > Notification Server > Site Server Settings
  2. In the Site Management screen:
    1. In the left-hand pane,
      1. Navigate to Site Management > Site Servers
      2. Click on the new site server
    2. In the right-hand pane, in the detailed Information section
      1. Set View to Sites
      2. Click New
    3. In the Select a Site window
      1. Select the site which this site server should serve
      2. Click OK

Enable the Package Service Upgrade Policy

  1. In the Symantec Management Console (SMC)
    1. On the menu bar: select Setting > Notification Server > Site Server Settings
  2. In the Site Management screen:
    1. In the left-hand pane,
      1. Navigate to Site Management > Settings > Package Service > Advanced > Windows > Windows Package Server Agent Upgrade
    2. In the right-hand pane, in the top section
      1. Set the policy to On

Now, this upgrade policy is enabled, so when the NS is upgraded, and the upgrade includes an upgrade to the Package Service components, then these components will be deployed to all site servers with Package services.


What Happens Next?

At this point the computer is on-track to become a Package server and to be setup to run Package on some client computers. These steps will all occur in due time, but each step can be done more quickly if necessary. Here are the basic steps.

  • NS runs resource membership update
    • Now the data on the Site Management screen is reflected in the corresponding computer filters and policies

  • Agent on this computer checks in for new policies
    • Now this computer knows it should become a Package server

  • The agent runs the process to install the Site Server and Package Services components.
    • Now the computer has installed the necessary software

  • Agent on the computer sends basic inventory to the NS
    • Now the NS knows that this computer is operating as a Package server

  • Agent on this new packager server checks in for new policies
    • Now Package Server knows what packages it should download

  • Package Server download packages, as time permits
    • Now package server has the packages

  • Later, when an agent on a managed computer requires a package
    • The Agent asks NS where to download the package
    • NS responds with name of local package server
    • Now agent know where to download the package

  • Agent downloads the package from package server