Question
Should I set up IP location–specific package shares for my deployments?
Answer
Setting up IP location–specific package shares is optional, but it can help distribute network load or ensure that remote computers access deployment files from a geographically closer or more optimal location.
By default, deployment files are stored in a single location and retrieved through one scanning server. The scanning server used for this purpose can be configured in the web console under Deployment > Security Options.
Although you cannot configure each Windows computer to retrieve deployment files from its own individual scanning server, you can define deployment shares per IP location. This allows all Windows computers within a specific IP range to pull files from a designated share. These IP location–specific deployment shares are also configured under Deployment > Security Options.
When a deployment uses the {PackageShare} parameter, and a computer belongs to an IP location with a custom package share defined, that share will automatically be used. Any computer not assigned to an IP location will retrieve files from the default package share defined under Security Options.
