SCCM Driver Package contents do not distribute to DP Share

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.

How to import server driver packages with Dell Server Deployment Pack 3.0 into ConfigMgr 2012 R2

The Dell Server Deployment Pack (DSDP) is a Microsoft System Center ConfigMgr plugin that helps create boot media with Dell server drivers injected and lets you select server models and Operating Systems that you want to import driver packs for.  The driver packages can then be used for various things including being attached to Task Sequences for Bare Metal Deployment.

Install the Dell Server Deployment Pack 3.0 using the Install Guide that comes in the download package.  http://en.community.dell.com/techcenter/systems-management/w/wiki/4125.dell-server-deployment-pack-dsdp-for-configuration-manager

The install log is located at C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge\Setup.  There you can find the DSDPInstaller.log and DSDPInstallDebug.log.

You will also need the Dell Toolkit.  There are several versions available.  Read the Fixes and Enhancements, Compatible Systems, and Supported Operating Systems to find the version you need.  As long as you are using a server that is 10G - 13G and the OS is 2008 R2 - Server 2012 R2, I suggest you use DTK 5.1.  I say that having not fully tested 5.1 yet, but based on that 5.1 should support the newer 13G servers with Server 2012 R2.

DTK 4.4.1 - http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=2XKRY
DTK 5.0.2 - http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=3HYJG
DTK 5.1 - http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverid=67M0X

And you will need to make sure you have the latest version of the Windows Automated Deployment Kit (ADK), which is 8.100.26629 from 9/15/2014.  Here is the link:  http://www.microsoft.com/en-us/download/details.aspx?id=39982

To install the DTK, right click on the Packages container and follow through to Launch Deployment Toolkit Configuration Wizard.

On the first screen of the DTK wizard you will point to the EXE of the downloaded DTK.  In this picture I had the previous version (4.4) imported showing on the left and then on the right it shows what will be imported with the new 5.1 version.

Next screen lets you build a new boot image by combining the Dell drivers in the DTK with your choice of the boot image in the ADK, an existing image in ConfigMgr, or a custom image at another location.

The screen after this one lets you name and version the boot image.  This will take a couple minutes to build the boot image, which can then be seen in the Boot Images container in ConfigMgr.  Log files for this process are located at C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge.  Logs are called DellConfigWizard.log and Dell ConfigWizardDebug.log.

Next, it is time to import server and OS specific drivers.

You should be using the OpenManage System Management Tools and Documentation DVD or ISO.  This is sometimes just referred to as the SMTD.  Do not use the SUU or SBUU or any other downloads because they do not have the appropriate folder structure to work with the DSDP at this time.

Which version of the DSDP you download will determine which servers and operating systems you can get driver packages for.  Be sure to read the Fixes and Enhancements, Compatible Systems, and Supported Operating Systems sections on each one to find what you need.  Here are some links to the latest several versions.

SMTD 7.4 - Looks to support most 9G-12G servers. http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverid=PYKGK

SMTD 8.0.1 - Some 13G servers and other new hardware.
http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=MKGTT&id=102

SMTD 8.0.2 - More 13G servers and hardware.
http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=J5MT0&id=102

*Edit
SMTD 8.1 was released shortly after this was published.  It supports all 12G-13G Dell servers.
http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=XT65T
Edit*

Please keep in mind that the SMTD may not have the most recent versions if newer versions have come out since the last SMTD release date.  Download one or more of the ISOs above to fit your needs.  Do not extract the ISO.

On the first page of the wizard you can either use the top option to point to the drive the ISO is mounted as, or you can use the bottom option to point directly to the ISO.  I find the bottom option easier because you don't have to mount the ISO.

*****Do not try to use one ISO, press next to see what it has, and then click on Previous to change to a different ISO.  It may not refresh and when you go forward again you will see the same servers from the previous ISO.  If you need to change to a different ISO, hit Cancel to close the wizard, then open the wizard again, and select a different ISO to use.

Next, select the servers and OSes you want to import driver packs for and click on Finish.  This could take a little while depending on how many you mark to import.

When it finishes you will see a completion screen that tells what it imported and what may have been skipped.  There are logs for this as well.  Located at C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\XmlStorage\Extensions\bin\Deployment\Dell\PowerEdge.  Logs are called DellDriverImport.log and DellDriverImportDebug.log

Now you should have driver packages for each server and OS that you selected.  These will be broken up into the Dell PowerEdge Driver Packages OMversion containers under Driver Packages.

Before you can use the rest of the DSDP utilities, such as the Task Sequence Bare Metal Deployment Wizard, or be able to deploy the drivers in a Task Sequence or alone, there are a couple more things you need to do.

1. Boot Image.  Go to the Boot Images, right click on your new boot image and select Properties.  On the Customization tab, make sure Enable Command Support is checked.  On the Data Source tab, mark Deploy this boot image from the PXE-enabled distribution point.  On the Data Access tab, mark Copy the content in this package to a package share on distribution points.  Then click OK.

You will also have to distribute the Boot Image to the DP(s).  Do this by right-clicking on the new Boot Image and select Distribute Content.

Click Next, Add, Distribution Points (or group if you have one).

Mark your DP(s), next, next, and close.

After a couple minutes you can refresh to see if the Content Status at the bottom has turned green.  Once it has you can right click on your Task Sequences, go to Properties, and add that boot image as the one to use to start that Task Sequence.

2. Dell PowerEdge Deployment Packages. With DSDP 3.0, there are 3 packages to distribute.  PowerEdge Deployment Toolkit Integration, PowerEdge Custom Reboot Script, and PowerEdge Startup Network Setting.  Each one should be set to "Copy the content in this package to a package share on distribution points".  This is on the Data Access tab of the properties of each one just like in the screen shots above.  Make sure you check this box for each of the 3 Dell PowerEdge Deployment Packages.  Then right-click on each one and Distribute Content to the DP, just like you did with the boot image above.  Then you can fresh and make sure each one shows Success under Content Status.

3. Driver Packages.  Each one should be marked to "Copy the content in this package to a package share on the distribution point" just as you did above on the Data Access tab for the boot image and the Dell PowerEdge Deployment packages.  Then you have to distribute to your DP(s).  This is exactly the same as the last couple of steps in the Boot Image and Dell PowerEdge Deployment packages above.

-----------------
EDIT 5/18/2015: ConfigMgr 2012 SP2/R2 SP1 does resolve the issue below, but only if importing drivers using 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
-----------------

*****Caveat*****  When you distribute the driver packages, I have seen where the driver package contents does not fully distribute the first time.  You can check this by looking at the PackageID and then going to the PackageID folder in the DP Share, which will be a SMSPKGdrive$ folder.  For example, if your package share is on your E: drive, the folder will be called SmspkgE$.  Find that PackageID folder.  This folder should match the source folder.  

This screenshot shows the Data Source tab which gives you the source folder location.  You can also see that folder open where there is a total of 30 GUID folders.

This screenshot shows the DP share after the first Distribute Content and you can see that the Content Status shows Success but only 1 GUID folder is shown.

For the time being, the work-around for this is to distribute the content again by selecting Update Distribution Points.

After you Update Distribution Points, you can look back at the DP share folder and you should see the same number of GUID folders as was in the source folder above (30).

That is it.  Now you can start to use these packages in your Task Sequences, or however else you want to use them.

How to clean out old OpenManage driver packages and replace them in Configuration Manager 2012

To clean out the imported OpenManage driver bundles from ConfigMgr and replace with newer or the same versions.  This works for any version of OM driver bundles but for this example I will use the last version and latest version at the time of this writing as examples (OM7.3.2 and OM7.4).  Some of these delete folder steps may need to be done on each DP.

1. Write down the Package ID first for each one drive package, or take a screenshot.  Then delete the Driver Packages and folders.
2. Go to the same driver folders labeled as "Dell PowerEdge Drivers OM7.3.2" in the Drivers sections in ConfigMgr.  Highlight all of the drivers listed, right click and delete them.  Then delete the folder as well.
3. Remove the folders labeled as "Dell PowerEdge Drivers OM7.3.2" also from both Drivers Packages and Drivers.
4. Go to the ConfigMgr Installation location which is normally "C:\Program Files\Microsoft Configuration Manager".  From here you will go down and delete the OM7.3.2 folders for the same versions you deleted from inside ConfigMgr in the following folders.
1. "\OSD\Lib\DriverPackages\Dell\PowerEdge\"
2. "\OSD\Lib\Drivers\Dell\PowerEdge\"
5. Go to the drive where your DP Shares are located.  For example, if they are on the E: drive you would go to "E:\SMSPKGE$\".  If they are on the G: drive you would go to "G:\SMSPKGG$".  Delete each Package ID folder that you copied back in Step 1 for each Driver Package.  These folders may just be empty shells at this point.

Now the old versions are cleaned out and you are ready to import new versions.  These driver packages can only be imported from the Dell System Management Tools and Documentation (SMTD) iso.  Do not use the SBUU, CDU, or SUU iso or your drivers will not be imported correctly.

1. First, mount the SMTD 7.4 iso in Server 2012 by double clicking on it so that it will appear like a DVD drive.
2. Right click on Drive Packages and select the "Dell Server Driver package\Import Dell PowerEdge Server Driver Packages" option.
3. Select the drive letter that the OM7.4 iso is mounted it.
4. Select the server models and OS versions you want to import and let it run.
5. Right click on each driver package that you imported and go to Properties. On the Data Access tab, check the box "Copy the content in this package to a package share on distribution points".  Press OK.
6. After each of those is done, right click on each driver package and Distribute Content.  Select your DPs and then give it some time to distribute.  The amount of time will depend on # of DPs, locations, network, etc.
7. Check the Content Status for an updated date and time and green pie chart.  You can also verify distribution to each DP by going to the SMSPKGdrive$ folder and verify the PackageID folder is created and drivers are there.

********* Note here*********  I have noticed that drivers do not always fully distribute.  Your SMSPKGdrive$\PackageID folder may only have one GUID sub-folder.  In this case, just Update the Distribution Points again for the same package and make sure the content status shows success.

8. Now just go back to your Task Sequences, Edit, and on the Apply Driver Package step just add the new package.