Peter van der Woude

Well, the Task Sequence of Niall needs that the package directory is set a level lower (so on x86 or x64). See the commandline: C:\_SMSTaskSequence\Packages\SMA00108\scanstate.exe

MAke sure that these services are set to start automatic: Analysis Services Integration Services Reporting Services SQL Server Agent

You can deploy software without MDT, it's only used in that post to deploy software during a Task Sequence.

You don't need that on a Secondary Site.

Then you have to create a Boundary for an IP Address/ Subnet. Just make sure that you don't get machines that will fall in both Boundaries.

Or just use NET USER (http://support.microsoft.com/kb/251394)

I've seen that error, when the program was configured to run with user rights, while it needed Administrator rights.

For the client push installations, check if you can connect to the machines from the Site server. The ports that you need to check can be found here: http://technet.microsoft.com/en-us/library/ff189805.aspx

Did you also deploy the client hotfix KB977384?

Sounds like a driver issue (SCSI,SATA, etc)

Google is your friend: http://blogs.msdn.com/b/astebner/archive/2009/04/16/9553804.aspx

First thing I would look at is the Firewall.

Just create a Software Package (like in one of the guides here: http://www.windows-noob.com/forums/index.php?/forum/57-deploy-software-applications-and-drivers/) create a program with your commandline and than use that Package/Program in your Task Sequence.

I think you can achieve that goal already by using a step Capture Network Settings (http://technet.microsoft.com/en-us/library/bb680640.aspx) and later a step Apply Network Settings.

Did you then got any related errors in the eventlog.

You also need to create a recurring schedule every day, otherwise the Always rerun program doesn't have any use. Also keep in mind that Only when a user is logged on doesn't mean it will run during logon. It only means that a user has to be logged on.

But to minimize administration AND installation time I would take one image with the base applications BUT without the drivers. Just inject the drivers during the deployment as it only costs a few minutes. It saves a lot of issues, like the one you've got now.

Does %computername% reverts back to the correct computername? I would try to use the Task Sequence Variable: %_SMSTSMachineName%

What kind of DHCP are you running?

Totally different question back, why are you trying to capture all different complete systems?

There are all step-by-step in this part of the forum: http://www.windows-noob.com/forums/index.php?/forum/66-software-update-point/ If that's not good enough, then what is it exactly what you are looking for?

I think it's waiting for user input, as you are not using /q (runs Sysocmgr.exe in quiet mode (without display pages))

Take a look at this: http://support.microsoft.com/kb/222444

Does this mean that all the clients are on SP2-level?

It's the same as with Software Distribution, just use the same Program (Command line looks like: wusa.exe <updatesname>.msu /quiet).