All driver packages need to be at least version 2 to always work correctly in auto-apply driver tasks. This is a known issue that is the result of the implementation of content distribution in general – it’s not a bug, just the result of certain design choices. Simply make sure you update your driver package after you initially deploy it to the DPs (there’s no need to add a comment or make any changes, just right-click it and choose update DPs). This has actually been this way since ConfigMgr 2007 RTM.
J From: [email protected] [mailto:[email protected]] On Behalf Of David Crist Sent: Monday, April 7, 2014 12:42 PM To: [email protected] Subject: RE: [mssms] driver package size is 0 Are you Auto applying the drivers in the task seq? or are you applying them in the task seq. When you go to Distribute those only the Applied drivers will be showing any size distributed. Auto apply do not. I found this out when making standalone media and the auto applied drivers from my production task seq never showed up as being distributed with the task seq, but the applied did. I made a copy of the production task seq and just deleted all the auto applied driver action to applied driver action. Then redistributed it and worked fine. Dumb on my part, it makes sense that stand media alone would not be going to the DP anyways for the auto applied drivers. David Crist From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Timothy Ransom Sent: Wednesday, March 05, 2014 8:59 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] driver package size is 0 I will after completing all driver packages – still having same issue on the original package for Dell Latitude E6520. From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Nash Pherson Sent: Wednesday, March 05, 2014 10:34 AM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] driver package size is 0 Tim, Would you write this up on Microsoft Connect and then post the link? I’ve got a couple customers that have seen this behavior before and they would all vote for the feedback item. http://myitforum.com/myitforumwp/2013/12/02/giving-feedback-on-microsoft-connect-for-configmgr-2012-help-yourself-help-the-community/ Thanks, Nash From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Timothy Ransom Sent: Tuesday, March 4, 2014 4:04 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] driver package size is 0 OK, created a second driver package, it was successful and shows correct size in Content Status. I will delete first package and try again. Thanks Daniel. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, March 04, 2014 6:53 PM To: '[email protected]'; '[email protected]' Subject: RE: [mssms] driver package size is 0 This happening in all packages or just 1? If just one then check the source directory, double check permissions, etc. -Daniel Ratliff -----Original Message----- From: Timothy Ransom [[email protected]<mailto:[email protected]>] Sent: Tuesday, March 04, 2014 06:22 PM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] driver package size is 0 Added comment and update DPs – no change. So frustrating! From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jeremy Sihassen Sent: Tuesday, March 04, 2014 6:00 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] driver package size is 0 Already seen it from time to time. Try to add a comment on the package and update the distribution point. Jeremy. Le 4 mars 2014 23:57, "Timothy Ransom" <[email protected]<mailto:[email protected]>> a écrit : Hi, Hope someone has seen this before. I have repeatedly tried to add a driver package in SCCM 2012 and each shows successful but the package size in Content Status shows 0. Thanks, Tim ********************************************************************************************** GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential information protected by state or federal law. The information is intended only for use consistent with the state business discussed in this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action based on the contents is strictly prohibited. If you have received this transmission in error, please delete this email and notify the sender immediately. Your cooperation is appreciated. ********************************************************************************************** ********************************************************************************************** GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential information protected by state or federal law. The information is intended only for use consistent with the state business discussed in this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action based on the contents is strictly prohibited. If you have received this transmission in error, please delete this email and notify the sender immediately. Your cooperation is appreciated. ********************************************************************************************** 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. ********************************************************************************************** GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential information protected by state or federal law. The information is intended only for use consistent with the state business discussed in this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action based on the contents is strictly prohibited. If you have received this transmission in error, please delete this email and notify the sender immediately. Your cooperation is appreciated. ********************************************************************************************** ********************************************************************************************** GDOL CONFIDENTIALITY NOTICE: This transmission may contain confidential information protected by state or federal law. The information is intended only for use consistent with the state business discussed in this transmission. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action based on the contents is strictly prohibited. If you have received this transmission in error, please delete this email and notify the sender immediately. Your cooperation is appreciated. **********************************************************************************************
