GetPackageInfo requests from clients returns empty or wrong package servers list
search cancel

GetPackageInfo requests from clients returns empty or wrong package servers list

book

Article ID: 165173

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

Computers are not pulling packages from their local Package Server; instead they are pulling packages from the NS, or another Package Server that is not part of their site. No error messages but below verbose logs might be observed:
The resource is not contained within any sites. Returning the NS codebases only.

Or in Altiris Profiler code tab for GetPackageInfo, an entry "ClosestSites" with value of  sites which returned package servers list belong to.

Environment

SMP / ITMS 8.0

Cause

When sites are created, SMP expects that each IP;s subnet in GetPackageInfo request xml belongs to a site which it will return a list of package servers in that site. If IP's subnet(s) or super scopes in client request are not included in any site, SMP return the closest site based on the IP's subnet and it's relative super scopes. It can happen that, a super scope is included within a site, which is accordingly picked by NS.

Resolution

Insure than all your subnets are assigned to sites, and each site has a valid package server.

This behavior is under review by EPM development team and might change in future releases.