Peter van der Woude

It is not possible to deploy Software Updates automatically... You always need to create a Deployment that includes the Software Updates.

I would create a Task Sequence, that first uninstalls the old version, then restarts and then installs the new version. Keep in mind that a Task Sequence can only be advertised to computers and not to users.

You can create an unattended install and deploy that. Take a look here for the options: http://technet.microsoft.com/en-us/library/bb693561.aspx

You need to create te container with ADSIEDIT (or give the SCCM Server rights in the SYSTEM Container) Take a look here: http://www.windows-noob.com/forums/index.php?/topic/616-how-can-i-create-the-system-management-container-in-active-directory/

Well... by capturing your own WIM image you can save a lot of time with deploying your systems.

When you are not using Mandatory Schedules then you could also try this: http://www.windows-noob.com/forums/index.php?/topic/1133-setting-computername-during-deployment/page__hl__computername__fromsearch__1 Or take a look at the different options from "Modena": http://www.petervanderwoude.nl/post/User-Driven-OS-Deployment-with-e2809cModenae2809d.aspx

What do the logfiles say?

You don't have to create a new Update Package everytime. With Deployment Packages it lists all your Update Packages, so if you selected an excisting Update Package then you won't see a new line with Deployment Packages.

What is the client version?

A Software Update always has to be in an Update Package

Take a look here: http://infraops.wordpress.com/2009/12/22/sccm-sp2-r2-it-must-of-have-been-the-turkey/

Also a part of the Service Pack 2 for SCCM is: Improved Client Policy Evaluation with Faster policy processing and More efficient software distribution configured to run at user logon. So for existing user and computers it shouldn't be such a process slower as it was before.

It works for every Task Sequence the same, it doesn't matter wether the Task Sequence will install Windows XP or Windows 7. So advertise both Task Sequences to the Unknown Computer (and remove the Mandatory Schedule) and you should be fine. If it is not working, please provide some more information about the settings of the Task Sequence and Advertisement.

By using the Step-By-Step from Niall (anyweb) you can select from all different Task Sequences x86 and x64 (that are advertised to the collection). What is it exaclty that you want to achieve? Do you want to pick from everything, or that there has to be a difference between x86 and x64? Does it has to be with the Unknown Computers?

Do you maybe also use a step Capture Windows Settings?

That's possible, you could run a script or command for that.

Does the machine get a good IP address? Can it connect to domain at all?

SCCM will only put the client in the correct OU, when the client is not allready in the AD...

Then you have to create something like with the Forefront Updates (see link I provided before). Just keep in mind that it is not recommended and personally I would never create a automatic Approval for Security Updates.

So you want to keep using WSUS for the updates and not use a Software Update Point from SCCM. Well... just not integrate WSUS with SCCM, so don't configure a Software Update Point in SCCM. This way you can just manage your updates through WSUS.

Then what is your question? Because before you said this: The answer will still be, that if you want WSUS integrated with SCCM to function properly you should NOT configure a GPO... I think this can help, there is a Technet article about deploying Forefront Updates with a shared WSUS environment here: http://technet.microsoft.com/en-us/library/dd185652.aspx And I have to say that it works, because I use it myself. And NO there is not a seperate GPO needed.

Nope.... you have to add them manually to a Deployment (tricky), but I would advise to create a new Deployment.

When using WSUS integrated with SCCM, you shouldn't set any GPO for that all. SCCM will set a local policy for that.

I think you should use a step Apply Driver Package, because by doing this you can specify which Mass Storage driver it has to use.

The only way to do this is (like you already suggested yourself) to not put the update in the deployment.