Peter van der Woude

MDT is not needed when using the SMP. The default Task Sequence already has the steps needed to do a capture and restore with a SMP.

Few short pointers, I would never use the same Site names again and by removing the Primary Site you also have to redo the Secondary Sites.

It is possible to run PXE on a DHCP server, but I wouldn't advise it if it's not neseccary (http://technet.microsoft.com/en-us/library/bb680753.aspx). Besides that even Microsoft say's that IP Helpers are more reliable then DHCP Options (http://support.microsoft.com/kb/926172).

There indeed shouldn't be any WSUS realated GPO's, as the SCCM client will set a local policy to point to the SUP/WSUS.

What commandlines are you using (fot starting the Batchfile and in the Batchfile)?

SCCM can also run from pretty much anywhere, I just don't get why it has to run from the 'source server'. Also, maybe you can say what your package looks like (program, commandline, location, etc.) and what it has to do.

Nope, not necessarily.

Behaviour is still the same Quote from your article: "After the SMS client has tried using its computer account and the logged on user account to connect to the distribution point, the client attempts to connect using the Advanced Client Network Access Account."

AFAIK I would say that you have to advertise a Task Sequence to a collection with the machine in it.

If it can help out others here, you can post a link.

Then you have to workaround the 64-bit redirectioning. Easiest way is a Task Sequence with a Run Command line step and select Disable 64-bit file system redirection.

That's exactly what the problem is, because then the change gets redirected to the WOW64 directory.

Is it on x86 or x64 machines?

Not totally true. A client will always first try to connect with its computeraccount (computername$), within the domain this should be enough. The Network Access Account is used for computers that are outside the domain and sometimes during OS Deployment. For more information: http://technet.microsoft.com/en-us/library/bb680398.aspx

Ok, only the 060 option is enough. Now make sure you advertise a Task Sequence to a collection with your computer in it and make sure the Bootimages etc. exist on the DP(s).

Did you now already got the 060 option fixed?

Then it first needs WDS Configured.... you could use this commandline for that: WDSUTIL /initialize-server /REMINST:"<DriveLetter>:\RemoteInstall"

060 is the only one that is really needed in this case. Normally it should be added during the installation of the PXE Service Point. If not it needs to be created manually.

Correct! That's the difference between a schedule and optional

SCCM takes care of the PXE part. Did you already take a look at this post: http://www.petervanderwoude.nl/post/ConfigMgr-2007-PXE-Service-Point-and-DHCP-Options.aspx ? When running PXE/WDS on the same server as DHCP you need to do some additional settings.

Possible, just use a Run Command Line -step. Take a look here for the commandline: http://support.microsoft.com/kb/310516

A PXE Service Point indeed needs WDS, also when you are configuring PXE/ WDS on a DHCP server make sure they don't respond to the same port (http://www.petervanderwoude.nl/post/ConfigMgr-2007-PXE-Service-Point-and-DHCP-Options.aspx).

That also happens when the Advertisements of your Task Sequence(s) ar set to Optional.

Nope, the ConfigMgr client will set a local policy to point to the SUP.

Or write a little script to recognize the OS, or use somthing like this: http://www.petervanderwoude.nl/post/Capture-User-Files-and-Settings-Offline-(WinPE)-or-Online-(FullOS)-with-ConfigMgr-2007.aspx