I'm on 2012 SP1 (no CU's) Not exactly the issue you are talking about but maybe worth mentioning....
I have found that you need to distribute new driver packages twice before the OSD TS will pick them up. I have tested this in my lab and in production. If you open the PkgXferMgr.log you will see that it fails to distribute the driver package when you first create it even though it tells you it's on the DP. A subsequent refresh then triggers the content to be copied to the library. From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Sent: Thursday, 15 August 2013 7:04 AM To: [email protected] Subject: RE: [mssms] Odd OSD issue with driver packages and content distribution Interesting... Our guys opened a ticket with Microsoft earlier today and are waiting for a response. I'll let you know what they find. Maybe I can use this opportunity to push Nomad :-) On Aug 14, 2013 3:44 PM, "Daniel Ratliff" <[email protected]<mailto:[email protected]>> wrote: I don't think so, we had a PFE on site a few weeks ago and that is what we determined to be the issue. We are evaluating upgrading to CU2 now. :) Ill check with our admins to see if I am mistaken, but I believe Microsoft told us CU2 would fix it. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ryan Sent: Wednesday, August 14, 2013 4:35 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Odd OSD issue with driver packages and content distribution We are on CU2... Do you know if there is any information documenting this issue? I don't see anything in the CU2 patch notes. On Wed, Aug 14, 2013 at 3:14 PM, Daniel Ratliff <[email protected]<mailto:[email protected]>> wrote: Known issue pre-CU2. The temp fix is to distribute your packages to all your DPs. Have to have 100% compliance before the TS will work. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Ryan Sent: Wednesday, August 14, 2013 3:45 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Odd OSD issue with driver packages and content distribution Yesterday, we finished setting up a new DP and added it to a DP Group so it could start getting content. Right after we did this, OSD stopped working and gave errors about not being able to find driver content. The error code was: Failed to find CCM_SoftwareDistribution object for AdvertID="XXXXXX", PackageID="XXXXXX", ProgramID="*" The DP it's pulling content from is not the new DP according to the smsts log. Our OSD guys disabled that driver package, and re-ran the task sequence. It failed again, same error but different driver package ID. This content exists on the DP it is trying to run from, and an hour before the task sequence worked. Our running theory is that if the content of a driver package is in progress somewhere in the world, OSD task sequences referencing it will not work until the content was successfully transferred. Has anyone else seen something like this? Have we read the situation wrong and something else is happening? I haven't been able to find anything through Google, so I'm not so sure we read this right. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ________________________________ CONFIDENTIALITY NOTICE AND DISCLAIMER The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.
