In few occasions we received the question from customers asking the requirement we have to always have a Package Server (PS) for each Symantec Management Platform (SMP) server in a Hierarchy.
The following is an explanation (from engineering) for why we need a PS for each SMP in a Hierarchy, how to set this up, and how to get around it if you're not interested in package replication in your Hierarchy.
There is a requirement that states that a Package Server must exist within the same Site as the SMP. This does not necessarily mean that the Package Server must be deployed within the same subnet as the SMP. So long as there is at least one Package Server deployed within the whole environment (doesn't’t matter which subnet) it can be manually assigned to the site that contains the SMP subnet, thus fulfilling the hierarchy setup requirement. These steps are outlined below under “Steps to manually assign a Package Server to the SMP Site.”
The reason a Package Server needs to be limited to the SMP site is so that certain Package Servers can be dedicated to download replicated packages across the Hierarchy, as most commonly it would be undesirable to have all Package Servers doing this.
Keep in mind that if you do wish to replicate packages and distribute them, the Package Server you assign to the SMP child site must be able to connect to the Package Servers in the Parent SMP site. If you don’t care about package replication at this point and just wish to setup Hierarchy, you can happily use the below manual assignment method. Also note that if you manually assign a Package Server to the SMP site this Package Server will be given as a possible source to any Agents/Package Servers that exist within this Site.
Additionally, once a Hierarchy is set up, you could actually break the manual package server assignment and the Hierarchy would remain intact. The steps for manually breaking the package server site assignment are outlined below under “Steps to un-assign a Package Server from a Site that is manually assigned.”