Iroqouiz

Ok, so what was the solution? Please share so others with the same problem as you get a chance to solve it.

What does the log files on the client say? Go to c:\windows\ccm\logs and open appdiscovery.log, appenforce.log and execmgr.log.

Any problems with your DP? Have you added correct NIC drivers to your boot image?

You shouldn't have to click install at both locations. I've deployed all my apps to the app catalog and when I click install there it starts SC and installs automatically.

Create a GPO to add the site to everyone's intranet zone.

Can you post a screen shot of the TS?

Yes, make sure the network access account has permissions to the files. Pause the task sequence (guide here in the forum by Niall) before your failing step, press F8 when it's paused and then map the share as your NAA and try to run the bat file.

If you add the app catalog server (SCCM server if installed directly on that) to the local intranet zone in Internet Explorer, does it work then?

I'm saying this without really knowing what I'm talking about, and without researching what it really is.... but maybe a cloud distribution point?

Creating custom reports is not my area of expertise. Google might help you.

Just use a simple bat script in the task sequence.

I've now spent a couple of hours making packages of my OSD apps instead of applications. Works without a hitch so far. I'm still going to use applications when deploying to devices in a full OS, that has never been a problem for me. OSD applications on the other hand, oh brother...

Thanks a lot.

Sure you can. Do like this (was a while ago that I created this myself so I might not remember everything): 1. Create a new custom task sequence and choose your boot image of choice. If you want to evaluate any TS variables just add a "Use Toolkit Package" and "Gather" step at the beginning. 2. Add your packages to the TS. 3. Deploy the TS to a device collection but make it only available to SCCM clients (and NOT pxe). 4. Add your test machine to the device collection. Done! Johan Arwidmark had an excellent session on this years MMS, it was the "ConfigMgr Experts Panel" if I'm not mistaken. He showed how you can test scripts in a TS like this as well. Basically you make sure a "Use Toolkit Package" and "Gather" step is first in the TS. Then you start a cmd.exe with the ServiceUI so it's started as the account that's actually running the TS in a normal scenario. Very handy if you want to test scripts in a TS over and over again without having to image the machine every time.

Are there any conditions on the Install Applications steps? Like only to run the step if the image is named "x"? Upload the smsts.log, appenforce.log and appdiscovery.log files so we can have a look.

What laptop models are you using? If it is Dell then they have excellent WinPE driver packs here. http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx

Check out MDT, can make computer naming VERY dynamic. This post explains it well. http://deploymentbunny.com/2012/04/21/back-to-basic-customsettings-ini-explained/

Perhaps one of the "Software Updates - Compliance" reports in the Monitoring node?

Yeah, I'm going to start using packages as well. Too much work in troubleshooting failed app installations in OSD task sequences. Heard from Johan Arwidmark on twitter that he prefers using packages as well because the app model is not really designed to be used in TS.

Since you changed them to HTTP that implies you were using HTTPS before? Your certificate is ok?

Ok. Are your updates downloaded to a software update group? Double check. They should be listed as "Downloaded - Yes"

Ok, that sounds unlikely. If you change the deployment type to always match 1641 to Success it should never reboot. Try refreshing content for the deployment type, right click on it and select "update content".

Try to get the smsts.log files from the machines and upload them here.

WinPE 4 and 5 are using Windows 8 drivers. Are you adding those?

Check how often your hardware inventory runs, in the Client Settings. If HW runs on for instance Sunday, and a user uninstalls Dropbox on Monday, and you run the report on Tuesday it will still include that user's machine. If I'm not very much mistaken.