nope, it's not fixed in this CU On Tue, Aug 4, 2015 at 6:33 PM, John Aubrey <[email protected]> wrote:
> Does anyone know if this issue has been fixed in CU1? It doesn’t appear > to be. I can only find fixes for Win10 driver issues. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jason Sandys > *Sent:* Friday, July 10, 2015 9:07 PM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > It still works fine, just not very quickly. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Andreas Hammarskjöld > *Sent:* Friday, July 10, 2015 2:35 PM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > I would say that a 12GB driver package is pretty broken Jason! J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* den 10 juli 2015 21:23 > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > Yes, it happens every time for a specific set of drivers. To my knowledge, > it’s based on the construction of the inf file from the vendor thus there > are some drivers unaffected by this. It’s not broken per se, just causes > extra time when downloading the driver package during OSD and some space > wastage in the source files. How much depends upon the inf file itself and > how many times files are referenced. > > > > J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Atkinson, Matt T > *Sent:* Friday, July 10, 2015 1:46 PM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > It doesn’t happen every single time does it? I can’t believe something > like that wouldn’t have been discovered during QA. > > > > Has there been any idea what triggers the duplication of files if it only > happens sporadically? We are putting together our plans for upgrading > because we want to start testing Windows 10, but something like this would > force us to hold off until they fix it in CU. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Roland Janus > *Sent:* Friday, July 10, 2015 4:25 AM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > Gee, just looked into the drivers for the HP Elitebook 800 G1 DM > > Source package folder goes from 400MB to 1.2GB in the package > > > > A single file in the source exists now 152 times in the package. > > Amazing that something like that wasn’t caught during basic testing… > > > > I have R2SP1 in prod. although no OSD yet, but obviously I need this to be > fixed before deploying clients > > > > -R > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Daniel Ratliff > *Sent:* Donnerstag, 9. Juli 2015 19:58 > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > Thanks Aaron for the update! > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Aaron Czechowski > *Sent:* Thursday, July 09, 2015 1:39 PM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > FYI, we’ve reproduced and identified the issue. I’m talking with sustained > engineering about getting into a future CU, but nothing committed yet. > Continuing to work through support is your best course of action right now. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Stephen Leuthold > *Sent:* Wednesday, July 8, 2015 6:44 PM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > Does anyone have updates on this issue or any other issues that would make > one hesitant to upgrade in production? > > > > Thank you, > > Stephen > ------------------------------ > > From: [email protected] > To: [email protected] > Subject: RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > Date: Wed, 8 Jul 2015 16:38:48 +0000 > > FYI > > > > > https://social.technet.microsoft.com/Forums/en-US/e6b39a1e-e66e-4223-8c94-46b62b7ebeac/sccm-2012-r2-sp1-driverpack-bug?forum=configmanagergeneral > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Mike Dougherty > *Sent:* Tuesday, July 07, 2015 6:00 PM > *To:* [email protected] > *Subject:* Re: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > This occurred in my environment when I tried to download the Windows 7 x64 > drivers for the Z230 Workstation from here: > > > > http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html > > > > I downloaded the .exe from the page, extracted it, imported the extracted > driver content into SCCM 2012 R2 SP1 and tried to create a package of JUST > those newly imported drivers. > > > > When I tried the package creation in this fashion, the driver package > source ballooned to over 12GB (vs 1 GB of extracted content) before I > forcibly stopped the process, as I was afraid our site server data drive > would run out of space. > > > > The Realtek audio driver was the worst offender (creating multiple copies > of the 183 MB folder, as there are 50 inf files in it), but it seemed to > trip over the Intel Chipset driver folders as well. > > > > I deleted the imported drivers and semi-finished driver package for this > model at that point. > > > > I then went ahead and deleted the Realtek audio driver sources from the > extracted content and replaced them with previous version of the Realtek > audio drivers available from HP for that model (which had 1 .inf in the > folder instead of 50) and re-imported everything. > > After that, package creation finished, but the final driver package was > about 3-4 GB (once again, vs. a 1 GB driver source size). > > > > I have imported and created driver packages for other HP models using the > method above and there's a 1-1 relation in size of the driver source to the > packages created prior to our SP1 upgrade. > > > > This isn't 100% scientific, but that's pretty much what I was seeing last > week. > > > > > > > > > > On Tue, Jul 7, 2015 at 3:58 PM, Underwood, Bob < > [email protected]> wrote: > > Does this happen regardless of the method used to import drivers? (i.e., > single INF versus scanning a directory for all drivers?) > > > > Can you provide a specific example of driver(s) that exhibit the > behavior? We can’t seem to reproduce the issue in our testing environment > where SP1 is applied. > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Andreas Hammarskjöld > *Sent:* Tuesday, July 07, 2015 3:22 PM > > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > As I understood it applies to all new/updated packages after SP1 was > installed. > > > > And yeah, I wouldn’t put SP1 in production… > > > > //A > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *John Aubrey > *Sent:* den 7 juli 2015 22:18 > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > Mine increased. All the older drivers and packages are about the same. I > only had one new 2012 R2 driver package I have imported since SP1 and it > went from 245 MB to 323 MB. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Miller, Todd > *Sent:* Tuesday, July 7, 2015 4:11 PM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > Is this for every driver import or does it only happen under certain > conditions? > > > > That’s big enough to stay away from SP1, I’d say. > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Daniel Ratliff > *Sent:* Tuesday, July 07, 2015 12:00 PM > *To:* [email protected] > *Subject:* RE: [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > Can confirm, MS is aware. We haven’t upgraded to SP1 ourselves, but I know > others that have and have tickets opened. > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Mike Dougherty > *Sent:* Tuesday, July 7, 2015 12:45 PM > *To:* [email protected] > *Subject:* [mssms] Configuration Manager 2012 R2 SP1 Driver Package > "Duplicates" bug > > > > I've seen this issue reported on Microsoft Connect and I've read anecdotal > evidence that Microsoft is supposedly aware of the issue, but I wanted to > reach out here to see if any can comment more-or-less officially whether or > not this is a known issue... > > > > Long story short, since updating to R2 SP1, we've found that creating > Driver Packages via the console causes massive content bloat. > > > > It seems that the process is a causing creation of a duplicate copy of the > driver source for every .inf file in a driver source folder. > > > > For example, for model of hardware X, the audio driver source content > folder has 50 .inf files in it. > > The folder containing the .inf files is 183 MB. > > When I go to create a driver package from this source, ConfigMgr creates > 50 copies of the 183MB source folder when creating the driver package (or > something along these lines). > > > > It caused me a minor freak-out last week when I was trying to create a > driver package for 1 GB worth of content that ballooned to over 12GB in the > "package" before I killed the process... > > > > Has anyone else seen this? Is MS aware of this issue? > > > > If you need me to provide more specifics, please let me know and I'll try > to help out where I can. > > > > > > > > > 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. > > > > > ------------------------------ > > Notice: This UI Health Care e-mail (including attachments) is covered by > the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is > confidential and may be legally privileged. If you are not the intended > recipient, you are hereby notified that any retention, dissemination, > distribution, or copying of this communication is strictly prohibited. > Please reply to the sender that you have received the message in error, > then delete it. Thank you. > ------------------------------ > > > > > > > > [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email > is proprietary to Medtronic and is intended for use only by the individual > or entity to which it is addressed, and may contain information that is > private, privileged, confidential or exempt from disclosure under > applicable law. If you are not the intended recipient or it appears that > this mail has been forwarded to you without proper authority, you are > notified that any use or dissemination of this information in any manner is > strictly prohibited. In such cases, please delete this mail from your > records. To view this notice in other languages you can either select the > following link or manually copy and paste the link into the address bar of > a web browser: http://emaildisclaimer.medtronic.com > > > > > > > > > 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. > > > > > > > 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. > > > > > > > ------------------------------ > > > This message is intended for the sole use of the addressee, and may > contain information that is privileged, confidential and exempt from > disclosure under applicable law. If you are not the addressee you are > hereby notified that you may not use, copy, disclose, or distribute to > anyone the message or any information contained in the message. If you have > received this message in error, please immediately advise the sender by > reply email and delete this message. > > > > > > > > > >
