techlogik

Well, it loads into the gui, and has gets to the Surface3 name in the GUI, but when I then click next, like that last screen shot, it reboots, and around in circles. So, I can't even get to or see the logs or what is going on unfortunately. On the PXE boot, it is connecting to the server, set it to Admin approval mode, and it of course is talking to it and seeing a list of images to start to download etc. It is just once I get to the gui where is all falls down. Will look at the driver injection, maybe once into the Gui, it isn't loading the drivers since they aren't there. But it will usually throw and error about the deployment share with other devices. Really what I'd like to do is be able to boot this thing up and capture an image of the C parition. But the Windows PE doesn't have the capture wizard in the image. So. Stuck on that mode now trying to create a capture image from the lite touch x64 pe image..but fails. Thx

No smsts.log file is created on the x: launch path/directions...did a search, nothing. Thx

So, maybe I'm clueless here, but when I get to the last screen shot above, and click next, it just reboots and I go in circles. So, I need to have another image/task setup to either try to capture the SF3 or already wim of a partition imported into the WDS for it to not keep looping after the computer name? I'm missing something obviously. Then it reboots and the message appears "An existing in-progress deployment was found but is not in an expected state. Would you like to ignore this in-progress etc..." Yes/No. And that is all she wrote. Thanks.

Same issue here. I had used a tutorial by Microsoft/Blog and I created a successful boot USB device. Then, started from scratch on my Deployment Server system, removed all directories, used the script from here with older references/drivers, and it now gives that same message on PXE, and my USB device when trying to connect. The USB should already have the drivers injected, but, it throws that same message now oddly as you have posted. I also added the latest giga ethernet drivers from Microsoft as you did, set it up, updated deployment etc..same error as you have TS, identical. Back to the drawing board. I'm using a microsoft docking station BTW for ethernet. I know it works with a plain vanilla WDS setup, with drivers setup manually and a standard/basic x64 iso it creates. Something on the deployment server side seemingly, but no idea what.

As another user posted on March 10th, I get this with the script after booting PXE, it can't connect to the share due to the driver not being available. But I manually added the Giga adapter for the docking station. Seems like it just isn't picking up on something after updating WDS etc.. "The following network device did not have a driver installed. PCI\Ven_11...blah" Retry or Cancel. Obviously missing something. I'm running a SF3 with latest updates/firmware from March 26 on this device, as I said with a docking station for the NIC connection. Really, I'm trying to just capture and image from a sysprepped SF3 for our company, then deploy it to the 30+ we have. Little lost here and any help appreciated on the NIC/driver issues. Thanks, great work on this BTW.