Iroqouiz

Why would you have a machine that's being reimaged being a member of several other collections where apps are deployed to? And I'm not sure about this, but I can't imagine a computer picking up other deployments during and OSD task sequence. It seems highly unlikely.

Basically you need to install a SUP and WSUS to sync the software updates into SCCM. You don't need to configure any GPOs to let SCCM manage and install those updates on your client machines, if your only goal is to inject updates into an OS image with offline servicing.

How have you deployed your task sequence? To "All Unkown Computers" or some other collection?

That's probably because you don't deploy your OSD TS to "All Unknown Computers".

No, only the last app is not discovered after installation (Webroot). Fix the detection method for that and try the TS again. I for one would recommend using packages instead of applications in a OSD TS. Packages are more reliable during OSD.

Upload the AppEnforce.log file somewhere, I want to have a look.

1. Are you having these problems now? You should probably check the smsts.log file on the client to see why the TS is failing. 2. The computer needs network access during installation if you are initiating the installation via PXE. If you have a stand alone installation on a USB stick it's not needed.

Check the appenforce.log file on the client, it's at C:\Windows\CCM\Logs. My guess is that your detection method isn't working.

Most of my applications worked fine in a TS also, but some of them didn't (at random times), and I can't have that kind of unreliability. And since more people than me has had similar problems I know there's nothing wrong with my specific environment, it's just a flawed implementation by Microsoft. I'm sure the consultants told you that, but I'm telling you how it is (for many of us) in the real world. And I provided you with a solution which is going to work 99,9% of the time.

This link has to do with another issue, but perhaps try the workaround anyway? http://blog.coretech.dk/kea/automatic-client-upgrade-greyed-out/

How long since you upgraded to R2? When I upgraded it took at least a few hours, if not more, for my remote DP to report back with correct status.

Is it an OSD task sequence? Read on twitter that Johan Arwidmark (SCCM MVP) didn't recommend using the new application model in, at least, OSD task sequences. I had a bunch of different problems, not the same as you though, and I actually converted all my OSD apps to packages instead. Since then I haven't had any problems installing apps in a TS. I still use the app model to deploy apps to clients in full OS and that works great.

You can't set the date and time for individual users on the machine. If one user changes the time, it's applied to all other accounts as well (even if they're logged in).

Run the administration activity report from "Monitoring - Reports - Administrative Security" and see if someone deleted the DP by accident. I don't actually know if you can find out, but it's worth a shot.

No, UTC is coordinated time, which means it will be applied at a time regardless of time zone difference. Leave it unticked to apply at client's local time.

I think it's not working since ZTIWindowsUpdate.wsf queries the WSUS database on the SCCM server, and not the SCCM SUP where you have actually approved and deployed updates. But I could very well be wrong.

1. Yes. 2. No.

ccm.log only displays results for when you use the client-push installation method. You can enable automatic client upgrade though

Stupid question, but did you actually click the Root folder in the first screenshot? One time I had the same issue where no images were displayed, and they didn't appear until I clicked.

That does not work when the client is installed during OSD, correct? Then we can only specify MSI properties?

I needed to set the ADRs to create new Software Update Groups each time they ran and found new updates.

Hey, did you ever resolve this? Have the same problem.

SP1 uses WinPE 4, hence you need WinPE 4 (Windows 8) drivers.

Are you running SCCM 2012 RTM, SP1 or R2? For RTM you would need Windows 7 NIC/storage drivers, for SP1 and R2 it's Windows 8 drivers. All according to whatever architecture the boot image is, of course.

Try recreating them. http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/