I thought to put a complete article about DS Site Server configuration but very soon realize that putting all the information in one document will make it bulky and bit unmanageable for any future additions. To serve it better I thought of putting in parts. And yes your suggestion and inputs are very much required and appreciated :)
In this first part I am trying to cover some important information related to Deployment Site Server configuration [applicable till ITMS 7.1 SP1a MR1 (DS 7.1.2316)]:
1. Symantec Management Platform/Notification Server performs all the functions of site servers, including task services, package services, and deployment SBS/task services. A Notification Server handles all the communication between itself and clients/site servers/SQL database.
2. Site Server is the intermediate server to share the load of NS by running all or any of supported service as Monitor Service, OOB Service, Task Service and Package Service in the same subnet or in a different subnet. In addition Deployment site server can also be configured on a Site Server.
3. Package service is deployed so that packages are stored locally at a site and rather than download packages from the NS, clients will get it from the site server within their site. This has special advantage in slow network or in WAN environment.
4. Task service is to serve the task from NS to clients and doesn't consume much bandwidth, but increases the scalability of the solution.
5. Deployment Site Server can be installed on a Site Server running both Task and Package services to set up the site server to function as a deployment server, so that clients can boot to PXE, load an Preboot environment like WinPE/LinuxPE, and receive DS specific tasks to be performed on the production OS or in Preboot environment.
6. Firewall/vLan/DNS/DHCP limitations on NS and in network should be taken care before DS installation for PXE/name resolutions to work properly.
7. For DS Site Server; server OS are preferred over desktop OS like Windows XP/Windows 7 because of higher concurrent connection limit.
8. Package Service configuration on NS setup is optional [Not recommended unless very specific need, say for testing purpose] and Deployment Site Service get configured/installed during DS installation itself. So if there is no Package Server is existing in the network than NS takes care of serving all required package to computers; including DS packages and DS PXE/SBS requests.
9. Site Server could be in same subnet as NS for load balancing purpose.
10. Site Server could be in different subnet to serve the packages and DS PXE/SBS requests to specific subnet computers.
11. Site Server must be configured with Task Service and Package Service installed to support DS Site Server [Small reference for PS IIS7 required components: https://www-secure.symantec.com/connect/blogs/required-iis7-settings-package-server-only-image-presentation].
12. If any Site Server with Package Server is configured; than only this existing Package Server will be able to serve the DS packages. Although PXE/SBS services will still work from NS.
13. If a Site Server with Package Service is configured than unless this is not fully ready with packages; no other Site Server will get installed because every next Package Server will look for packages from the first Package Server
14. Best Practice for DS Site Server configuration is to install First Task Service followed by Package Service and when Package Server is completely ready than Site Server component
15. All deployment solution specific packages [default count 8] will be in “Invalid” state unless Deployment Site Server component is installed on Site Server and SMAgent configuration status is updated after default duration of 1 hour or if update is done manually.
16. All DS clients under a specific Site Server should point to this same Site Server for Task Server.
17. An early executed task or job specific to Site Server client will fail if specific DS packages are not replicated/ready at DS Site Server.
18. After DS Site Server is ready; large size images can take long time to replicate on DS Site Server and early executed task with such specific image will fail for client/s under this specific Site Server.
19. DS related newly added Deploy Anywhere/Preboot drivers can take up to 8-12 hours to replicate to Site Server [Workaround: - https://www-secure.symantec.com/connect/blogs/deployment-solution-7x-replication-newly-added-drivers-site-servers ]
20. DS related client Backup images will not replicate to other Site Server and will be stored only on the specific Site Server. [Workaround: Resource Import Tool can be used on Site Server in such specific need]
21. DS specific package replication on Site Servers can be controlled from the NS console for the individual packages.
Read Part 2: Deployment Solution 7.x: DS Site Server Configuration Part 2