Peter van der Woude

The Capture Task will create a WIM of the current installation of your machine. So when your current installation already includes some applications, then your WIM will have them too.

Good to know that, that did the trick

Well... what I am trying to say is that your configuration (SCCM 2007 SP1 with Server 2008 R2) is not supported... It is possible that the Management Point errors are being caused by this configuration. I would advise to install SCCM 2007 SP2.

The first thing I would say is that this is not a supported configuration for a Primary Site.... When you want the server OS to be 2008 R2, then you need SCCM SP2. Take a look here: http://technet.microsoft.com/en-us/library/cc161823.aspx and here: http://technet.microsoft.com/en-us/library/ee344146.aspx

Did you try to manually connect to the remote WMI and the admin$ ??

Give the service the Startup Type - Automatic (Delayed Start)

Make sure that the useraccount, that you use for installing the client, is local administrator on the client machine.

What you could do is installing the SCCM Console on the MDT Server and then create the integration. Its probebly only going to be complicated when creating a MDT Task Sequence in SCCM and the Task Sequence wants to create some MDT packages...

Why not using the integration with SCCM to deploy virtual Apps?

Why would you want to seperate SCCM and MDT???? Besides that you need to install MDT locally to be able to make the integration with SCCM.

The client installation account needs to be local admin on the client machine. When you are using the CLient Push Installation, you can use a Client Push Installation Account.

1. You do NOT need to configure anything in WDS. 2. Did you add the Bootimage to a Distribution Point?

When I'm looking at your picture I see that you made at least one typo by typing the nslookup... You did: nslookup 192.167.255.1 instead of: nslookup 192.168.255.1

Did you configure DNS correctly? Can you restart the DNS Service?

Did you take a look at the SMSTS.log?

It should be a WIM file (.wim). You can create a WIM File by using a Build and Capture Task Sequence (Ts). Let the TS run on a machine and it will create a WIM file, this WIM file then should be used in a normal Install TS

You also might want to take a look at this post: http://blogs.technet.com/mniehaus/archive/2009/09/22/running-powershell-scripts-as-part-of-a-task-sequence.aspx

And your script is in the root of the package? I don't think you need to use ".\" then in front of your script. To be sure take a look here: http://technet.microsoft.com/en-us/library/ee176949.aspx

What is the location of the script? A package, a networkshare?

It all has to do with Company Policies... There are a lot of different options, like a GPO for those laptops that enables Automatic Updates again, or Internet-Based Client Management (http://technet.microsoft.com/en-us/library/bb693755.aspx), etc..

Do you already have a primary site running? Or did you had one installed before?

I haven't tried to sequence Office 2003 yet, but I wouldn't know why it couldn't work. Keep in mind that an application as Office is often used by other applications, this could cause problems if your Office is created in a "bubble". So make sure that all of your (or your users) scenario's get tested really good.

These are not errors, but just warnings. They could cause failures, if you are running in Native Mode. Besides this do you get other errors or notification?

USMT 4.0 works for Restoring and Capturing Windows 7 and also works for Capturing Windows XP.

We need more information then this... What steps are running in your Task Sequence? Does it gives an error? If so at what point? What do the logfiles say? etc...