Package Server Storage Management: Configuration and Monitoring

Products

IT Management Suite

Issue/Introduction

This article provides the configuration steps for both the primary and custom package storage locations, along with methods for monitoring the status of large-scale storage changes and best practices for managing disk space.

Environment

ITMS (IT Management Suite)

Symantec Management Platform (SMP) and solutions that utilize Package Servers (e.g., Software Management, Deployment Solution)

Resolution

Setting	Details
Location in SMC	Settings > Site Server Settings > Package Service > Package Server Settings
Default Path	`<Symantec Agent Installation Directory>\Package Delivery`
Relocation Process	When changed, the PS moves all existing packages (including those previously spread across other drives) to the new single custom primary location.

Configuration Steps:

In the SMC, navigate to Settings > Site Server Settings > Package Service > Package Server Settings.
In the left-hand pane, navigate to the specific Package Server (Site Server) you wish to configure.
Under Primary file storage location on Windows OS, select the Custom option and enter the desired local path (e.g., Q:\New folder for packages on remote PS).
Click Save changes to apply the policy.

Prerequisites for Relocation:

Before applying a custom primary location, ensure the new location meets the following requirements:

It must be on a fixed media (e.g., a hard disk drive).
It must have sufficient free space to accommodate all packages currently stored in the default and any rotated locations.
It cannot be a Windows Known Folder or any of its subfolders.

2. Configuring a Custom Package Destination Location

This per-package setting allows you to move specific, typically large, packages to separate drives, overriding the primary location setting.

Setting	Details
Scope	Per-package setting, used for specific large packages (e.g., DS images).
SMC Location	Manage > All Resources > Default > All Resources > Package > Package Server tab.
Monitoring	Storage usage for these packages is NOT included in the Package Service status in SMC.

Configuration Steps:

In the SMC, navigate to the desired package (Manage > All Resources > Default > All Resources > Package).
Right-click the package and select Actions > Edit Package.
Click the Package Server tab.
Check the option Use custom package destination location on package servers.
Enter the custom path (e.g., D:\Additional Storage for some SW packages on PS). You can use %COMPUTERNAME% in a UNC path for scalability.

3. Monitoring Package Relocation Status

When the primary storage location is changed, you can monitor the relocation process from both the Package Server and the Notification Server.

Package Server Status Keys

The following Windows Registry keys on the Package Server machine are used to manage and track the automatic retry process for relocation:

Registry Key Path	Value Name	Type	Description
`HKLM\SOFTWARE\Altiris\Altiris Agent\Package Server\`	`Package Storage Relocation Maximum Attempts`	`REG_DWORD`	The maximum number of automatic retries allowed (default is 3).
`HKLM\SOFTWARE\Altiris\Altiris Agent\Package Server\`	`Package Storage Relocation Attempts Done`	`REG_DWORD`	The number of relocation attempts already performed.
`HKLM\SOFTWARE\Altiris\Altiris Agent\Package Server\`	`Package Storage Relocation Interval (min)`	`REG_DWORD`	The interval in minutes between automatic relocation retries (default is 15 minutes).
`HKLM\SOFTWARE\Altiris\Altiris Agent\Package Server\`	`Package Storage Relocation State`	`REG_DWORD`	State flags indicating the overall status of the relocation.

Notification Server Inventory Event

The Package Server reports the relocation status to the NS using the "AeX AC Package Location Status" inventory event. This event includes several fields to track progress and diagnose issues:

Storage path (c0): The new location targeted for relocation.
Last relocation status (c5): The state flags indicating the status of the last attempt.
The event also includes metrics like the volume's Total size, Free size, and Size used by PS.

Manual Retry: If relocation fails for some packages, the Package Server maintains availability via Junction Points and schedules retries. An administrator can also manually trigger a retry from the Symantec Management Agent (SMA) interface on the PS when the "Retry Package Relocation" link appears.

With ITMS 8.7.3 Release, the following improvements were done in order to identify Package Server Health:

Information regarding System Health: Package Server Health

Information on "PSInformation" section on Package Servers

4. Best Practices for Managing Storage

Use Dedicated Drives: Configure the Primary Package Location to a dedicated, high-capacity disk, separate from the system drive, to prevent OS instability due to full disks.
Enforce Unique Subfolders for Custom Locations: CRITICAL: When configuring a Custom Package Destination Location, always specify a unique subfolder for each package (e.g., D:\DS_Images\Package_A). Failure to do so may result in the entire directory being deleted when a package is removed or the custom location is cleared.
Manual Cleanup for Custom Locations: The Package Server does not automatically clean up files in custom-specified locations. Administrators must manually monitor and clean up unneeded packages in these locations to free up space.
Check Total Usage via SMA: To see the total size of all managed packages (including those in custom locations), check the Total Size value under the Package Server tab of the Symantec Management Agent (SMA) on the PS machine.