Peter van der Woude

If all the updates of your manual deployment are already downloaded via the ADR, then that will explain why you didn't had to download them (again). Are you mayb deploying the same updates, twice?

You might be running into this issue: http://support.microsoft.com/kb/2928122

Is the boot image available on a distribution point?

It doesn't do a prereq test if that's what you mean. It will just start with applying the updates you selected, just until it fails, or succeeds. Remember that offline servicing only works for operating system related updates and not for applications (like .NET).

I agree with Peter. The application model is not supposed to be used like that. One application in ConfigMgr should be one software package and the deployment types can be used to differentiate on target devices (operating systems). The detection is also done on a application level, when it detects that the application is not installed, it will install the application by using all the applicable deployment types.

With their credentials, is the machine joined to the domain? If not, that could very well explain why the client still shows as not installed.

The multiple deployment types are not designed to install multiple applications. An application in ConfigMgr should be one software package and the multiple deployment types are just to make it possible to deploy one application to multiple platforms. So create an application in ConfigMgr per software package.

The ccmsetup.log shows a successful client installation. What is the exact problem you are seeing?

Are you sure the WMI query is correct, becease It sounds a lot like the drivers are not applied at all.

What are the deployment settings (deadline, maintenance windows, etc)?

Well... that's one of those thing that doesn't work as nice as it look is a design. Both the MP and the SUP can be installed multiple time within a site, BUT you can not define which one will be used by the client. The client will pick either of them at random. With the SUP, it should be that after, I thought, three failures, it should switch to a different SUP. The easiest way to prefend this is by installng a secondary site (there goes the flat design...).

The reason is actually pretty simple, because ConfigMgr/SUP just uses WSUS. The ConfigMgr client also uses the WUA client to scan for updates and compliance, so the settings configured by ConfigMgr for software updates on the client are actually just WSUS settings. That means both ConfigMgr policies and GPO are both writing to the same registry keys to write their WSUS information. Hope this makes it better to understand, it did in my head

That's expected behavior if you are using ConfigMgr/SUP for update deployment. You will need an a client to find applicable updates. because ConfigMgr does not approve/reject updates in WSUS.

Hyper-V or VMware? If it is VMware you probably need to add network drivers to the boot image.

Is the server you point to from the GPO the same as the "real" SUP? If it is, it shouldn't be a problem. The reason why we always advice NOT to use GPO when using ConfigMgr, is because ConfigMgr uses local policies to set the exact same setting(s) and you probably know that a GPO overrules a local policy.

I would go for the second option, as the first option most likely doesn't deliver a fully functional device...

I only have something for the first half of your question, about deploying certificates: http://www.petervanderwoude.nl/post/deploying-certificate-profiles-with-configmgr-2012/

Looks like the device is not in the collection that the task sequence is deployed to.

Correct. It should show the FQDN of the SUP. Software Center shows the available updates. Depends, if the device that you are running the console on has internet, then I would use that to download the updates to the package.

Is there a firewall blocking FTP trafic?

A key part is resolving the Management Point (MP). The client needs to be able to resolve the MP. The installation is described here:http://technet.microsoft.com/en-us/library/gg712298.aspx

====================================================================================================================================================================================== >> Available via download here on the TechNet Galleries! << ====================================================================================================================================================================================== I do have to admit that this tool is already available in it's final form for over a month, but it seemed appropriate to also post here about this final relase. I think this right-click action might be very usefull for most administrators. It also took quite a while before I finally made a 1.0 version of this script/ form. Now it’s there, I also have to admit that I’m even a bit proud of it! It was a nice way of getting familiar with PowerShell and WMI. With answering a few very basic questions, I'll try to provide as much information as possible. What functionalities does it provide?This right-click action shows a lot of detailed information about the collections of which a device is a member and also about the collections that the primary user of a device is a member. A quick overview of all the functionalities comes down to the following information per tab: Tab – General; The Name, Id. Limiting Collection, Last Update and Last Membership Change of the Collections. Tab – Deployments; The Name of the Collections and the Name, Type aand State of the targeted Deployments. Tab – Variables; The Name of the Collections and the Name, Value and Type of the Collection Variable. Tab – Maintenance Windows; The Name of the Collections and the Name, Start Time, Duration, Recurrence, Schedule, Type of the Maintenance Window. Tab – Power Management; The Name of the Collections, the Name of the Non-Peak Power Plan and the Name, Start Time, End Time and Wake-up Time of the devices in the Collection. Tab – Primary User: Tab – General; The Name of the Collections, Id, Limiting Collection, Last Update and the Last Membership Change of the Collections. Tab – Primary User: Tab – Deployments; The Name of the Collections and the Name, Type and State of the targeted Deployments. What does it look like?To show the power and usage of this right-click action, I created the following small movie: Where is it available?The final version of my Collection Details Form is publicly available via the TechNet Galleries and for a direct download, via ShowCollectionDetails_v1_0p.ps1. How can it be used?To use this script as a right-click action, save the script at [sCRIPTLOCATION], make sure that the folder <AdminConsoleInstallDir>\XmlStorage\Extensions\Actions\ed9dee86-eadd-4ac8-82a1-7234a4646e62 and the folder <AdminConsoleInstallDir>\XmlStorage\Extensions\Actions\3fd01cd1-9e01461e-92cd-94866b8d1f39 exist and add a XML file to those folders as specified here: <ActionDescription Class="Group" DisplayName="Custom Actions" MnemonicDisplayName="Custom Actions" Description="Custom Actions" SqmDataPoint="53"> <ShowOn> <string>ContextMenu</string> </ShowOn> <ActionGroups> <ActionDescription Class="Executable" DisplayName="Show Collection Details" MnemonicDisplayName="Show Collection Details" Description="Show Collection Details"> <ShowOn> <string>ContextMenu</string> </ShowOn> <Executable> <FilePath>PowerShell.exe</FilePath> <Parameters>-ExecutionPolicy ByPass -WindowStyle Hidden "[sCRIPTLOCATION]\ShowCollectionDetails_v1_0p.ps1" -ResourceId "##SUB:ResourceId##" -SiteCode "##SUB:SiteCode##" -SiteServer "##SUB:__Server##</Parameters> </Executable> </ActionDescription> </ActionGroups> </ActionDescription> Questions?Please don't hesitate to drop any questions, either here or via my own blog at: www.petervanderwoude.nl

SCCM uses a big part of the existing WSUS functionality. Its uses the WUA client to scan for compliance and uses SCCM only for "approving" of updates and content.

Select TOP does not exist in WQL and there is not really an alternative... You have to find something else to filter on

Sort of... the updates will install automatically when they become mandatory and that's when the deadline is past. So by putting the deadline far away, the updates will stay available.