Peter van der Woude

It will use the packages that are advertised to a collection where the computer is in.

Take the machine out of the domain and make sure that the IP Address/ Range is added to the Boundaries of the Site, so the machine can still get the Advertisement.

You need the following steps (like it say's on my blog): •Join Workgroup - This step is necessary when the Reference Machine is joined to a domain •Prepare ConfigMgr Client - This step is necessary to clean the ConfigMgr Clinet on the machine •Prepare OS - This step is necessary to Sysprep the machine •Capture the Reference Machine - This step is necessary to do the Capture

You need to Sysprep the machine first before you are able to capture the machine... There is a step Install Deployment Tools that you can use to copy the sysprep package. When you are trying to capture a W7 image it already has the sysprep package. Take a look at this post: http://www.petervanderwoude.nl/post/How-to-create-a-Capture-Only-Task-Sequence-with-ConfigMgr-2007.aspx

Did you copy sysprep to the machine (c:\sysprep)?

Think about it like this: When you setup ConfigMgr, you set it up to manage clients. Then ask yourself the question, which clients does it has to manage? When it's only there to manage clients from the AD, then it's enough to use the AD Site as a Boundary for your ConfigMgr Site. But when you need to manage clients that are not in the AD, you have to figure out where they are. This could indeed be a IP Range/ Subnet. When that's the case then use that as Boundary (too).

I just looked at the links profided by Niall and they show x86, x64 and ia64 versions of the updates

A unistall guide would work exactly the same as a install guide. The only difference would be the commandline of the program.

The clients will only get advertisements when they are within the Boundaries of the Site.

I mean the Boundaries that you use for your Site (Site Settings > Boundaries). It is possible that you use your AD Site for that, but the question is: Does the reference machine fall in that Boundary after it is Build?

The easiest way to do this is during the Build and Capture of the image. Build your reference machine make the changes in the admin profile and use a sysprep.inf during syspreping the machine (http://support.microsoft.com/kb/959753). By using UpdateServerProfileDirectory=1 (XP SP3) in your sysprep.inf it will copy the admin profile to the default user. Take a look at the link how it works with your OS.

Is the reference machine still within the Boundaries of your Site after the Build?

We need more information for that. Like the speed links between the branches and the HQ, like the number of clients, like the parts of SCCM you are going to use etc.

Go to Site Settings > Component Configuration and open the Software Update Point Component Propterties. Go to the tab Sync Schedule and there you can define the schedule to sync.

When you capture an OS you should do that when it is joined to a WORKGROUP. You should join the computer to a domain during the install Task Sequence with the step Apply Network Settings.

1. When you just captured a reference image of the computer, you have a syspreped version of your OS on the computer. So it still needs the information like date/time etc. I wouldn't consider it as your first deployed computer... 2. You can add drivers to the Driver Package or install them as a Software Package. 3a. It will get DHCP from server 3b. It will get the computer name supplied by you when adding the computer to SCCM 3c. Has to be supplied by yourself after installation 4. you could use USMT for userdata. See also: http://www.petervanderwoude.nl/post/ConfigMgr-2007-USMT-40-and-using-Hard-Links.aspx

Little correction here... The architecture of the laptop does matter. When you boot your laptop (or computer) it boots already into WinPE before it is in your Task Sequence. At this point it will pick a bootimage based on the architecture of your laptop (or computer).

Suggestions for what?

Did you use the Vista driver? And into which bootimage(s) did you inject it?

So if I understand you correctly you want to use the custumized WinPE version as an OS Image, instead of a bootimage?

I do think that it is a driver issue. Almost all cases when then client reboots before it is able to load the Task Sequence, have to do with drivers. So just add the correct Vista NIC driver to the bootimage(s) and I am almost totally sure that it will work.

What is your goal with adding this custumized WinPE image?

Then skip the step of re-partioning and re-formatting the disk. By doing this it will just wipe the OS partion and leave the second partition intact.

It's not needed to set a GPO for that. When you enable the Software Updates Client Component then the SCCM Client will set a LOCAL policy that points to the right direction. Besides that you can always do a RSOP to check all the used policies on a client.

Before the computer gets into the Task Sequence it already boots into WinPE. Here it picks a bootimage based on its architecture, which in this case was probebly x64. You do not have to delete the computer from the AD. If it already excists it will stay in the same OU