An update to part of two other posts I made.
***EDIT 5/12/2015: ConfigMgr 2012 SP2/R2 SP1 does resolve this issue, but, at the moment, only if you import drivers with the builtin driver import wizard.***
***EDIT 5/26/2015: We now have a fix for the issue with Dell Server Deployment pack v3.0. Please see this new post, http://bradsjumpbag.blogspot.com/2015/05/fix-for-dell-server-deployment-pack.html***
Back in How to Import Driver Packages with DSDP 3.0 into SCCM 2012 R2, I had mentioned near the bottom that Driver Packages may have to be distributed to the DP share twice. First time when you run the Distribute Content operation the content may not fully distribute. Or, the packageID folder may not even be created and the distmgr.log shows an error "SetObjectSecurity failed; 0x80070002".
This is not Dell specific. I downloaded and tested a couple of driver sets from other vendors also and they did the same thing. I downloaded their packages, imported them into their own Driver Packages using the builtin SCCM import wizard, not other vendor tools. Then when I hit Distribute Content I saw the same issues.
SCCM 2012 R2 Service Pack 1 is set to be released this week, most likely on Thursday, 5/14/2015. And there was a slide from Microsoft Ignite that mentioned 24 fixed bugs and design change requests in Driver Management alone. One of them was "Content won't get to DP if imported drivers are added to a new package and the checkbox "Update DPs when finished" is unchecked." Hopefully that is the same bug and the fix for it will be available this week.
No comments:
Post a Comment