Peter van der Woude

Do you have the correct .NET version(s) installed?

AFAIK there is not a supported method to do this. Also, I think that adding the NO_SMS_ON_DRIVE.SMS to the new drive after the distribution point was already using the driver, is the cause of your problems... Something that might help you is this: http://www.myitforum.com/articles/1/view.asp?id=12833

You're showing all information of a good functioning software update point. To deploy the updates you've got to add them to a software update group, download them to a package and deploy them to a collection.

Do you run the console from your workstation? If so, and if your workstation does have internet, you should be able to download the updates.

Start with checking the ccm.log on the site server to see if the push action was succesfull. If it was succesfull check the ccmsetup folder on the client.

You're probably synchronizing the metadata from an upstream server, but that would still require you to download the content of those updates (either from the internet or a network share). Do keep in mind that it uses the internet connection of the machine that you;re running the console from.

In the task sequence, you can add options to a step. You could check if the task sequence is starting in WinPE, or not. That will indicate how the task sequence was started (I thought it's even a default thing at the first step).

I've done something similar one, see: http://www.petervanderwoude.nl/post/verify-local-administrators-via-powershell-and-compliance-settings-in-configmgr-2012/

I can name a key point already, your DMZ servers need to be able to resolve the FQDN of the MP. The required ports can be found here: http://technet.microsoft.com/en-us/library/hh427328.aspx

Not sure what chapter 7 step 6 is about, but are you by any change trying to deploy something that already exists on the distribution point?

I've seen this error in different situations. One was were the proxy was wrongly configured and another was were the updates were not locally stored (which is configured during the installation of WSUS).

Since R2 it's also possible to Set Dynamic Variables based on for example the default gateway. That might help you out differentiating the different machines.

Please provide more information. Like, is WSUS local, or remote? Version of WSUS? Did WSUS succesfully install?

The deadline can be found in the scheduling tab of the deployment. In combination with maintenance windows the updates should install during the first maintenance window after the deadline.

I think these blog posts by Jason should help you out (even though it's written for CM2007, it's still the same for CM2012 except for the FEP part): http://blog.configmgrftw.com/software-update-management-and-group-policy-for-configmgr-what-else/ http://blog.configmgrftw.com/software-updates-management-and-group-policy-for-configmgr-cont/

Did you also check on a client itself to see what it's doing?

All the different methods described here: http://blogs.technet.com/b/smartinez/archive/2013/09/27/top-3-configmgr-2012-client-installation-methods.aspx

Based on your current information I've got no clue what might cause this, or even what's happening... You can allways try OSDPreserveDriveLetter as it won't hurt, but based on your first information I can't imagine that it would help.

I don't know about official support, I do know that it's still operational in my R2 CU2 environment.

This is very little information... If you're simply looking for troubleshooting reports, you might want to look at the reports in the category Software Updates - E Troubleshooting.

If the installation is that sensitive I would use an old-school batch file. By doing that you can use the batch variable %~dp0 to specify the working directory. In that case the command line of you package, or application, will be the batch file.

That doesn't really make sense... Can you install the driver manually afterwards?

Really removing them, or just creating a custom start screen like this: http://www.scconfigmgr.com/2013/10/23/modify-the-windows-8-1-start-screen-during-osd-in-configmgr-2012/

Are you look for something like this: http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06

If I'm not mistaken that error indicates something like not enough storage, or memory available to complete the operation