Is the client getting the advertisement policy?
1. Check the ccmexec.log for the advertisementID.
2. If the advertisementID is not in the ccmexec.log, check the ccmexec.log for errors communicating with the Management Point.
3. If the ccmexec.log shows errors communicating with the MP, follow basic connectivity tests such as pinging the MP by IP address, pinging the MP by hostname and telnetting to port 80 on the MP.
4. If the ccmexec.log indicates the client can communicate with the MP, check the Management Point to see if the policy exists using SMS Client Centre tool.
5. If the policy is not on the MP, ensure communications from the site server to the Management Point.
Is the client able to Locate a Distribution Point?
1. Evaluate the LocationServices.log to determine which management points we are using.
2. Evaluate the CCMExec.log and policy logs to make sure the client is connecting successfully to the management point.
3. Evaluate the CAS.log to determine if the content location is being returned correctly.
4. Ensure roaming boundaries are configured correctly and do not overlap with boundaries from the home site of the client.
5. Ensure the distribution point servers are online.
6. Ensure the command line for the package is correct.
Is the client able to access content on the Distribution Point?
1. Verify the computer account has access to the share by checking the NTFS permissions on the SMSPKG<driveletter>$ share as well as the individual package folders inside. These permissions may be set explicitly or through group membership.
2. If configured, verify the network access account has appropriate permissions, either through explicitly adding the account or membership in appropriate groups that already are granted rights.
3. Verify appropriate credentials by logging on as either the network access account or computer account and attempting to access the distribution point share.