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]> 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]] *On Behalf Of *Ryan
> *Sent:* Wednesday, August 14, 2013 3:45 PM
> *To:* [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.
>
>


Reply via email to