Peter van der Woude

They are both in the same domain? When you extend the AD you do it for the whole domain, not for one DC...

When you are going to use PXE, you need WDS

Correct, you don't need the MDT Tools for a Hard-Link Migration.

Where is the Hard-Linking in this TS? To use Hard-Links in a TS you need to create three Task Sequence Variables: 1. Name: OSDStateStorePath Value: %_SMSTSUserStatePath% 2. Name: OSDMigrateAdditionalCaptureOptions Value: /nocompress /hardlink 3. Name: OSDMigrateAdditionalRestoreOptions Value: /nocompress /hardlink See also: http://www.petervanderwoude.nl/post/ConfigMgr-2007-USMT-40-and-using-Hard-Links.aspx

Correct, when your program is set to "when no user logged on". Then it will only run when no user is logged on.

Do the clients download from the correct DP?

Are you running in Native Mode or Mixed Mode?

When do you have the problems? Is it when the clients try to install the package or when you are distributing the package to the secundairy site?

That script is meant for Windows Update... See also: http://myitforum.com/cs2/blogs/rtrent/archive/2007/11/14/microsoft-deployment-new-feature-windows-update.aspx

Check if your Site Boundaries are set up correctly. See also: http://technet.microsoft.com/en-us/library/bb681005.aspx

I think that, that is because it doesn't know the variable computername in the Task Sequence. See this link for information about Task Sequence Variables: http://technet.microsoft.com/en-us/library/bb632442.aspx

No it will not prompt for anything. It will just wipe the partition instead of formatting it.

Remove the step Format and Partition Disk from your Task Sequence. Now the Task Sequence will only Wipe the partition on which you want to install the OS.

Does that only shows under Site Systems? Because when you install the PXE Service Point it does create a SMSPXEIMAGES$ share and DP, but that doesn't show Site Systems... So it almost has to be a manual action...

I assume that it is indeed possible to create two steps of Apply Network Settings and then in the Options tab add a query that checks on the computername. I once did something simular with Laptops and PC that had to be in seperate OU's

They are indeed doing a good job off ripping the site.... I got no clue about what software would be a good fit... I did a search on Google and it found a lot. So enough choices, but still no clue what would be a good fit... Sorry

The way they act is indeed kinda lame.... Maybe you can disable right clicking on the site? But that will harm everyone.... So, I think, the best option is indeed to mark all the screenshots...

That is not an error it is just a warning that doesn't influence installing SCCM. Just click Ok and the installation will continue

The best, and I think, the only way is by creating multiple collections. There is no other way to control which clients are getting the advertisement...

It works, because it already finished the step of building your OS. It errored in the step Setup windows and ConfigMgr on [LOG[Executing command line: "\\DCO000X.CLIPX.LOCAL.COM\SMSPKGD$\CLX00008\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot]LOG]!><time="10:01:07.932+-120" date="09-18-2009" component="OSDSetupWindows" context="" type="1" thread="492" file="commandline.cpp:805"> <![LOG[Process completed with exit code 31]LOG] Check the package CLX00008

You probably have to add a NIC driver to your bootimage

Take a look at this article: http://technet.microsoft.com/en-us/library/bb693546.aspx

Are you trying to deploy Windows 7 with SCCM 2007 SP1?

Keep in mind that when you create a BDP instead of a Secundary Site with a Standard DP your clients can NOT download with BITS... Maybe this link gives some more information: http://technet.microsoft.com/en-us/library/bb693570.aspx

As far as I know I would say that it is not possible. Because you manage your Secundary Site from your Primary Site. Your Secundary Site only forwards information.