matthewjones

Take away the READ from Dept B. Then they cannot see/read the package.

I am majorly frustrated. I have a simple package to deploy to a mix of Win7 & XP machines. This is a single .MSI installation with a copy of an XML file post installation. The clients are getting the package directory is created {c:\windows\system32\ccm\cach\cdc000cc.412.system} However, content is NOT there. This package was set up last night at 11pm. It is now NOON and nothing is delivered... WHY!!???? This is getting critical.. Package is built: CNG_ClientInstall.cmd msiexec /qn /i SafeDeployment.msi copy CNG-Server-Info.xml "C:\Program Files\CNG\CNG-SAFE" /y Distribution points are defined and seeing the package as installed. Collection is set up: Confirmed there are 28 client COMPUTERS in the AD Group and the Collection sees them all. Advertisement is set up: General Package is picked from above. Program defined. Collection picked. Schedule Schedule is currently set to Start - No end. Mandatory Assignment - ASAP (was repeat every 2 hrs - didn't work). Priority HIGH. Distribution Points "Download content from distribution point & run locally". {Allow fallback is checked}. What are the basic steps / logs to follow to track this insanity? I need results TODAY!! PLEASE!