i've mailed the product group and asked them about this, what version of
Configuration Manager are you using ?


On Wed, Sep 11, 2013 at 10:28 PM, Richard Zuraff <
[email protected]> wrote:

>  I’m waiting for a support person from MSFT to call me back on this issue
> as we are seeing it on multiple DP’s.  It’s causing issues with our rollout
> of 2012.  ****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Niall Brady
> *Sent:* Wednesday, September 11, 2013 3:24 PM
>
> *To:* [email protected]
> *Subject:* Re: [mssms] Issue with Driver Packages replication in SCCM
> 2012.****
>
> ** **
>
> i think their fix was the same assumption you came to, i'll ask the
> product group if it's a known issue****
>
> ** **
>
> On Wed, Sep 11, 2013 at 9:50 PM, Richard Zuraff <
> [email protected]> wrote:****
>
> Did they have a fix for it?  I’m not seeing anything related to a fix.****
>
>  ****
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Niall Brady
> *Sent:* Wednesday, September 11, 2013 2:22 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] Issue with Driver Packages replication in SCCM
> 2012.****
>
>  ****
>
> two people were mailing about this just last week.****
>
>  ****
>
> On Wed, Sep 11, 2013 at 9:16 PM, Richard Zuraff <
> [email protected]> wrote:****
>
> We are having issues with Driver Packages that keep failing to replicate
> due it trying to extract the files to the old SCCM 2007 format.    We have
> the option “copy the content in this package to a package share on DP”
> checked.  If I remove this it will replicate without issue.  We are also
> seeing this same issue with when we try to use prestage content as well.
> It will fail on trying to unpack the drivers to the 2007 folder structure.
> ****
>
>  ****
>
> We are running SCCM 2012 SP1 CU2.  Is this a known bug.****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
> Richard Zuraff****
>
> Automation & Orchestration ****
>
>  763-764-5097****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
> ** **
>
> ** **
>
> ** **
>
>



Reply via email to