You have just rolled out the Symantec Management Agent (Altiris Agent or SMA) and the client doesn't seem to be receiving any policies. After checking the NS logs, the following message appears:
RequestPolicies failed: Unexpected response from URL HTTPS://SMPServer.example.com/ALTIRIS/NS/Agent/GetClientPolicies.aspx?xml=<Request configVersion="2"><WrkstaGuid>{xxxxxxxx-CC35-41C0-A4E3-4D0E9E8F2CCA}</WrkstaGuid></Request>&compress=1&hash=1: The specified resource is not ready. This condition is temporary and will be resolved as soon as the next collection update occurs (Resource: {xxxxxxx-cc35-41c0-a4e3-4d0e9e8f2cca}) (-2147213299)
and under the Agent log:
<event date='10/17/2024 18:41:56.8960000 -04:00'
severity='1' hostName='<<COMPUTER>>' source='PackageDelivery' module='AeXPackageDelivery.dll' process='AeXNSAgent.exe' pid='3340' thread='3024' tickCount='13087000' >
<![CDATA[Error while downloading package: The specified resource is not ready. This condition is temporary and will be resolved by the next collection update]]>
</event>
ITMS 8.7.x
There is a small window of opportunity from when a computer first sends Basic Inventory and when the filters are updated. During this time, you will receive the message "The resource is not ready." However, once the Filters have been updated, you will not receive this message again for the specified agent. If at this point you are still not getting policies, you should check that you have enabled any needed policies and that you have applied them to a Filter(s) that includes the agent in question.
You can find the options for updating filter membership and policy -> filter associations by:
1) Open the Symantec Management Console
2) Navigate to Settings -> Notification Server -> Resource Membership Update
3) On Complete Update Schedule, click: Run.
This will update the membership for all Filters, Organizational Groups, and Targets
Check in the SMP Console interface to confirm that these three tasks are scheduled to run. The following are the defaults:
If you continue to experience difficulties, check the Notification Server logs to confirm that these jobs are running periodically and as expected.