Joe

Greetings: I'm having some challenges with an OSD deployment of WinXP SP3 using SCCM and MDT2010. The machine will PXE boot and deploy the WIM I've created with XP in it. It seems, though, that nothing that I speicfy in the task sequence is acutlly used in during the build. For example, I've specified the product key, and the domain to join (with a username/password that is valid). If I don't put these settings in the sysprep.inf in my settings package, it will not join the domain nor put the product key in. I've got quite a few more tasks for it to complete, but it looks like it's bailing out of the task early and causing problems. I've examined BDD.LOG and SMSTS.LOG and there are no errors. I also see no reference to the username that I have specified to join the domain with. Is there another log file stashed somewhere? I've specified an SLSHARE in my CUSTOMSETTINGS.INI to redirect the logs to a server -- is it possible something isn't getting copied over? It really seems like all that is happening is that my WIM is getting deployed and sysprep.inf from my setting package is getting copied over. Other than that, no other changes are getting applied. Any help locating the proper log (or log entries if they aren't an error!) would be greatly appreciated! Thanks!

We are using MAK. I assumed I had the right key becuase I could manually enter it after the machine is built and activate it without problems. Thanks.

Greetings: I've got a weird problem where an R2 build fails through OSD every time I add the product key to the deployment task (SCCM with MDT doing OSD). If I remove the key from the task it works fine -- I can then add it to the machine with slmgr.vbs /ipk %key% so I know the key is valid. Any thoughts?

Any ideas at all? I'm hoping it's something simple I'm overlooking...

I've attached the log to this message. I stop the service, deleted it, then started it up and initiated a PXE boot. I did not hit F12 to boot into the WDS menu. It seems to be recognizing the client: Is it not receiving the advertisement properly? Another thing I noticed -- the GUID is wrong. It should be 564D6785-5A53-DC34-D819-0C7CB5BC7E1D.

Both DHCP options are unchecked -- Do not listen on port 67 and Configure DHCP option 60 to 'PXEClient'. I believe this is default. I'm pretty sure I'm not prompted to hit F12 for the SCCM task. I only see the options that were present on the WDS server before I added the PXE role in SCCM. It also takes a while to actually PXEboot which makes me think SCCM isn't responding and WDS is picking up the request. I double checked the boot -- it waited about 7 seconds before the PXE started. If I hit F12 I'm given the boot menu from WDS, if I let it go it continues on to boot to other devices. I've double checked the mac. I've recreated the computer with the mac, with the GUID, with the mac AND the guid -- same result. Is there a log I can check to see if SCCM is passing on the client or not answering at all?

I have WDS installed and the router is forwarding request directly to the WDS server. I'm trying to "upgrade" the environment to use SCCM for OSD. I assigned the PXE role to my WDS server, added the boot images, added the Operating System installation files, created my collection and imported my computer into the SCCM. I then created a task and advertised it to the collection where that my computer is in. I set the delay on the WDS server to 7 seconds and the delay at the SCCM console (on the WDS servers PXE role) to 0 seconds. This should allow SCCM to answer PXE requests for hosts with jobs, but still move on to PXE boot for other utilities that we have available (such as data recovery, etc) via the WDS server. What happens is that "it" never seems to answer requests for the advertisement. The machine will PXE boot, but it displays the menu from the WDS server instead of the booting to the boot media I've specified in the task.

I've got WDS and SCCM installed on separate boxes. I installed MDT on my SCCM server and installed the PXE role on the WDS box. I'm having some problems getting a machine to PXE boot properly. I'm not sure if I need to use the PXE filter. It's my understand that is just for unknown clients? Is that the case? I tried to install it through the MDT start menu option, but I get an error message telling me that I need to "Please fix all errors before continuing". It doesn't give me any other error messages so I'm not sure what to fix! There is nothing in the event log and no error messages show up in the trace logs during a PXE boot. In regards to this filter -- I'm assuming it needs to be installed on the SCCM server, not the WDS server. Is that correct? Thanks in advance for any help.