Peter van der Woude

There is no log or attachment...

Well.. that really depends on how many clients, what the load the server can handle and maybe more impartant what the business demands... I've seen settings in the range of 15 minutes until 8 hours...

AFAIK a license key is for Windows XP and the Service Packs are not under a specific license...

You already lost me when I saw the topic name, as I don't understand why anybody would still be deploying Windows XP SP1a... So the only suggestion I have is to start with at least Windows XP SP3, which is already old...

It can be done, take a look here for some more information: http://technet.microsoft.com/en-us/library/bb632332.aspx

When you've got your WIM file already you can continue with part two here: http://www.windows-noob.com/forums/index.php?/topic/1169-deploy-windows-7/ One of the reason the use a build and capture is to prevent all the manual work you are doing now to configure your WIM...

Easiest is to just kill the process that was started with your action.

It's not a requirement, it just makes it easier...

It can't find a DP for (a) the package(s), as it says: Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs So I would check if all the packages are available on the DP an if a DP is available to the client (check boundaries, etc)

You can just use the builtin task sequence steps for that. It will connect to a SMP by default. Side note: you can't use hardlinks in combination with a SMP

Nope, because that's exactly why you could get problems.. At that moment clients find two Site that "say" that they want to manage the client and that is why and where the trouble starts...

That happens if you connected the x86 boot image to the task sequence and the machine first booted with the x64 boot image...

The migration process, does not destroy any data in your SCCM 2007 environment... the only thing it does, is migrate data to your new environment... The only thing you should remember, with running them side-by-side, is that you don't get overlapping boundaries.

Good luck, but maybe more important, ENJOY!

Did you enjoy your first day?

The ports you need can be found here: http://technet.microsoft.com/en-us/library/bb632618.aspx You need at least traffic to the MP, DP and SUP. Also make sure to add a boundary for the ip range/subnet of the DMZ servers.

Besides DHCP Option 60, PXE Client, there is no need for any other option... unless it goes over VLANS, but then I would rather advise IP Helpers.

Depends.. are you running Native or Mixed mode?

Of course that's possible.. but you have to do some scripting for it.. Let the location depend on vlan/ ip range and check the ad for the first free name...

That's possible.

Reports, WindowsUpdate.log, Programs and Features/ Add Remove Programs...

It might be possible, but I can't imagine that it would be supported...

You need to get the smsts.log from the failing machine. At the moment that it failes press F8 and look for it.

Is it not just the bootorder of the VM?

Configuring WDS and DHCP on the same server indeed doesn't make it easier as they both listen on the same port. Reading your december-post, you had the DHCP part working.