Issue deploying "bad drivers" package

[CakeM1x]

I need to install two HP drivers (graphics and fingerpoint) and I wanted to list both programs under one package(6560b drivers). The source files are in "Drivers/6560b/graphics" and in "Drivers/6560b/fingerpoint" so I point the source directory to "Drivers/6560b/". When I create the programs I then point it to "fingerpoint/fingerinstall.exe". When I try to push the package it just hangs on "waiting for content". Is it not possible to do it this way? If I point the source directory to "Drivers/6560b/fingerpoint" it will work but then I need to create a whole new package just for the other "bad driver" and I don't want to do that.

 

I've had multiple programs in a package before without any problems but all the files were in the source directory. Any help would be appreciated.

 

Also any advice on what logs to look at for issues with "waiting for content" hangups?

[waingro]

Under the program properties click Browse and point to the executable that way - then append your command line switches. That will ensure you don't have a typo causing an issue. HTH.

[CakeM1x]

That's what I always do. I've recreated and tested this multiple times. It looks like it is the graphics folder that it is mad at. I looked in the computers ccm cache and it isn't downloading all of the content. Are there any logs I can check to see what is causing the issue? I've googled and some mention bin files are an issue with sccm?

[Peter33]

Hi Cake,

 

bin file are blocked by your IIS by default. You have to modify the mime types on all IIS on all distribution points and allow bin files to be transfered. Therafter retart the IIS. Otherwise you can also disable the local caching for this package as workaround.

[CakeM1x]

Hi Peter,

Thanks for the input. I already have bins listed under mimes on the site. I selected "run program from distribution point" in the advertisement and it worked. It doesn't work if I have "Download content from distribution point and run locally". Does this help any?

[Peter33]

Hi Cake,

 

i would suggest to to check the IIS logs on your distribution point. There are several more file types. I don't remember them all now, but we had to white list some more. I think conf files are being blocked also by default. You should see the trouble makers in the logs.

[CakeM1x]

I assume you mean the logs in %SystemDrive%\inetpub\logs\LogFiles correct? What are some key words to search to find what file types it didn't like? Only see HEAD and GET before the filepath names. Don't see anything with error or fail.

[Peter33]

Hi Cake,

 

 

have a look a this link. This was helping to solve the caching problems for me when ran into the same issue.

[CakeM1x]

That did the trick! I had to allow .resources and .config. Thanks a lot Peter.