package servers replication time

Update schedule can be found by looking at the scheduled tasks on the notification server.
The task name is "NS.Package Distribution Point Update Schedule.{29a2b641-222a-43b0-830c-a25c59e93fe4}".  The default is set to every 10 minutes, but you may want to take a look at yours just to make sure it has not changed.

You can also update the package servers manually by navigating to the package and clicking the "update distribution points" button.

Depending on which NS Version you are running, 6 or 7, the default package path on the package servers can be a little different.

From the documentation:

NS 6
'installation path\Altiris\Altiris Agent\Package Delivery\{Package_GUID}\cache'

NS7
'installation_path\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\{Package_GUID}\cache'

A little more about package replication in the NS6 environment here: https://kb.altiris.com/display/1n/articleDirect/in...

RS

Thanks for that information. The issue i have is that i configured a package server which is located in a branch office, connected via 2Mb WAN link.

When the replication started it attempted to replicate around 6GB of data, which i dont want. I am wondering if there is a selective way to choose which packages are replicated?

I am trying to cancel the replication as its consming bandwidth thats requirted for other services.

Thanks for your help.

Colin.

If you are concerned about bandwitdh, set throttling options on your package server's Agent configuration policy. Use the the Bandwidth/Throttling settings. You can force it to throttle regarldess of connection speed:

i was able to find that option regarding bandwidth throttling - thanks again.

Is there any option to select which packges can be replicated?

The first comment is not quite right. The Distribution Point Update only updates the snapshot file on the NS, it does not do the replication out to package servers. The NS Agent on the package server has to do a configuration request in order to see any snapshots that were updated with the Distribution Point Update on the NS.

Only when the PS's NS Agent does a config request will the PS actually download the updated or new source files.

You can set the schedule in the Agent Configuration Policy for All Package Servers. But that is only "once every hour"... not "every hour on the 5's". So you won't know *exactly* when they'll get "replicated" to, but you will know that it will be within the time frame you've specified (within the hour if you set it to check in every 1 hour).

Thanks for this additional info.

Colin.

I must have misinterpreted the info from the guide:

Updating the distribution points for a package
The distribution points for a package are the locations at which the package is
stored, such as package servers or UNC source locations. Information on each
package is contained in an XML file that is stored with the package. This
information must be updated each time the package is modified. Notification
Server and package servers use this information to provide the appropriate files
when a managed computer requests the package. The package information is
updated on a schedule, but you can perform a manual update when appropriate.
For example, if you have changed a package you can manually update the
distribution points for the package to update the package information on all of
its distribution points immediately.

Thanks for the clarification