re: Some ConfigMgr 2007 clients never install packages, report status of “Waiting on content”

YPae — Thu, 23 Aug 2012 18:22:42 GMT

Hi Clifton,

Thanks for this information. I might be in the other situation you described in "More Information".

We have AD Sites and Services' Subnet set to 9.9.0.0/16 while the phyiscal network is set to Class C level (9.9.x.0/24)

When we have intermittent weird locality detection issue on DP, we found that the system properties on each computer with the issue had both Subnet[0]=9.9.0.0 and Subnet[1]=9.9.x.0 (while boundary is defined only for 9.9.x.0. listed.)

We are NOT using Network Discovery but heavily rely on:

- AD System Discovery (Full discovery daily with 5 mins delta discovery)

- Predelivered SCCM Client on the image (or just in time delivery via OSD)

Questions:

Q1 I don't know if it is the root cause of the issue but I don't know if I have to convince AD Administrator to change AD Sites and Services configuration for the sake of matching boundary? What is the typical reason to have supernetted configuration on AD Sites and Services? Just simplicity?

Q2 As SCCM 2012 comes with Active Directory Forest Discovery, it might be better to match it anyway?

Thanks,

Young Pae

re: Some ConfigMgr 2007 clients never install packages, report status of “Waiting on content”

NEO11 — Wed, 14 Mar 2012 19:26:11 GMT

Solved !!! Hey Guys Please have another check after you check boundaries configuration

your Antivirus Application rules Or any FW on your Workstations !!!

our case was policy restricts from app rules blocked autorun.inf files in cache directory.