Awesome, thanks Stuart. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret Sent: Friday, January 9, 2015 2:20 PM To: mssms@lists.myitforum.com Subject: [mssms] RE: driver package mayhem
https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/1082184 From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Aaron Czechowski Sent: 09 January 2015 17:43 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: driver package mayhem Could one of you do me a huge favor and file this on Connect? I’m compiling a list of these sort of oddities into a bucket of things to potentially do in the future to improve the product. ☺ Aaron From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Timothy Ransom Sent: Friday, January 9, 2015 7:21 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: driver package mayhem Here is an option from Microsoft support that I use. In Driver package properties\Data Access: Select Copy the content in this package to a package share on DPs. Additional disk space is required on DPs if you select this option. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret Sent: Friday, January 09, 2015 9:44 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Re: driver package mayhem so i did the trick of adding the blank text file to each directory in the source folders, then reimported. this has worked, and some kind soul wrote a batch file for the purpose, still such an irritation, in what is a mature product. thanks all PUSHD %~dp0 @ECHO OFF for /f "tokens=*" %%G IN ('dir /ad /b /s') DO ( echo. > "%%G\%~n0.txt" ) POPD Stuart Watret Offshore - IT Ltd ________________________________ From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> <listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>> on behalf of Chris Carbone <chris.carb...@fairmountsantrol.com<mailto:chris.carb...@fairmountsantrol.com>> Sent: 09 January 2015 14:15 To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: driver package mayhem I have also seen this numerous times. Usually what fixes this is if you add the ini field under drivers and delete any duplicate ini names and THEN create a driver package the 0 byte size issue goes away. Good luck, this can be an aggravating problem. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Stuart Watret Sent: Friday, January 09, 2015 5:26 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] driver package mayhem TS was failing, tracked down to 7 driver packages with 0 bytes in size. Seen this before, thought you just updated dp's and off you go, no dice. So I have deleted all the driver packages, and the package folders (they were blank too) Re-creating a new driver pack for the hp 6005, wizard, says yes, package folder is empty. DriverCat log says, this driver has already been imported for each inf it finds. Stuck - what now, I'd delete the drivers (under drivers) but some are shared with other models that work. Is there a route forward, or ditch them all and start again............... Stuart Watret Offshore - IT Ltd This electronic mail transmission may contain confidential information intended only for the use of the individual(s) identified as addressee(s). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this electronic mail transmission is strictly prohibited. If you have received this transmission in error, please notify me by telephone immediately. ********************************************************************************************** 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. **********************************************************************************************