Peter van der Woude

Nope, you still need to install SCCM 2007 R2. R2 doesn't get installed automatically, not even with a push installation from the Primary Site.

Can you add any more Boundaries, or is it only that specific IP Range causing trouble?

First of, keep in mind that you need SP2 to deploy Windows 7. Second, the Hardlink Migration which you describe (with using 3 variables) is described on my blog: http://www.petervanderwoude.nl/post/ConfigMgr-2007-USMT-40-and-using-Hard-Links.aspx There is also an extended version (similar to Niall's version): http://www.petervanderwoude.nl/post/Capture-User-Files-and-Settings-Offline-(WinPE)-or-Online-(FullOS)-with-ConfigMgr-2007.aspx

It should say something in the smsts.log then...

With the different Boundaries?

Yes, I get that you create a Standard Task Sequence, BUT you are still using a MDT related step, so you need the step Use Toolkit Package.

As the branch server in London is not a Primary, I 'll assume that it is a Secondary Site server. You can only assign clients to a Primary Site. The only thing you could do then is install a Proxy Management Point, to control the load. This means that the clients within the Boundaries of the Secondary Site will send their Inventory etc. through the Proxy Management Point.

Is the DP protected?

It means that the machine cannot contact a DP at that moment. Are al of those machines in the same Boundary? Should they use the same DP?

Is the Branch Site, also a Primary Site? Did you configure Client Push?

You still need to open the Dynamic RPC Ports, also take a look at this post: http://www.petervanderwoude.nl/post/ConfigMgr-Client-Push-Installation-and-(a)-Firewall(s).aspx

By deploying it to a User Collection.

You first need a step Use Toolkit Package, to be able to use the MDT reletad steps in a Task Sequence.

Take a look here for what WinPE 3.0 supports: http://technet.microsoft.com/en-us/library/dd799308(WS.10).aspx For specific hardware it's defenitly a trial-and-error game...

How does the rest of your Task Sequence look like?

what about your smsts.log?

Nothing to worry. A computer with a client is known to the SCCM Site, so it cann't end up as an unknown computer.

That's not possible. Using a Software Update Point is a "total package". It is possible to create a local (Branch) Distribution Point for those clients and push your Software Update Package to that Distribution Point too. In that way the clients check with the Software Update Point and download from the local (Branch) Distribution Point.

Take a look here: http://technet.microsoft.com/en-us/library/bb633276.aspx

If the computer is Discoverd by the Primary Site, then the answer is yes.

The client needs to be discovered by the Secondary Site and the Secondary Site needs to have a PMP.

Correct (see previous post about the client push).

Correct, configure Client Push at the Secondary Site. SCCM Client Center is a tool created by Roger Zander: http://sourceforge.net/projects/smsclictr/

That can be checked in the logging (ClientLocation.log and LocationServices.log) or with tools like SCCM Client Center.

A Secondary Site cannot have its own Management Point (MP), it can only have a Proxy Management Point (PMP). This also means it is not possible to assign clients to a Secondary Site, only to a Primary Site. Connecting Boundaries to a Secondary Site is only for the use of the Distribution Point (DP) and the use of a PMP (to control the network bandwith). For the Client Push take a look here: http://technet.microsoft.com/en-us/library/bb632380.aspx