wds error 0x80070035
I got wds setup and captured a sysprepped image from a laptop.
The I booted another one and selected the deploy image option, it then gets to about 1% of expanding the files before it dies with a 0x80070035 error message.
Anyone seen this before?
Some interesting posts on google.
Some suggest disabling IPv6 on Vista, others say it's a permissions problem accessing the share, etc.
Are you using Vista or XP?
Deploying XP from WDS on Server 2003.
WDS Slow at imagaing XP - TechNet Forums
Does this help? Our original test WDS box never worked properly and we got a different network card in it, worked fine...
Thanks for that I'll trawl through some ideas today, the server is a vm on esxi
That error means "the network path was not found" - don't know if that points you in the right direction.
When you get an error 0x8007xxxx then take the last 4 digits, convert to decimal (calc is your friend if you can't do Hex maths!) and then do a "net helpmsg <number> at a command prompt
I know that was what the message refferred too but doesn't help as the path is there and available as far as I can see.
After I am asked for a username/password it authenticates very quickly shows me the images I can select.
It moves on and the copying files completes almost immediately with a green tick.
The the expanding files goes to 1% and thats it, after a minute or so it gives me that error.
Well I got it too 8% and now it appears to be stuck there, grr.
Right this is what I've done so far.
Installed wds in native mode.
Installed XP on client and run sysprep.
Booted client into pe capture image.
Captured the system to a wim file.
Not 100% sure if it did upload it to the wds server as I also copied it across manually.
Boot identical laptop into deploy image.
Gets stuck at 1%, 2% or 8% was the furthest I got.
I then reran wds legacy setup to get the wds server running in mixed mode.
Copied server 2003 as an image.
This image then deployed on to laptop and setup ran through etc... I stopped it when it asked for cd key but this step proves that the files were deployed ok.
I've then tried to create a pe disk with ghost32.exe on it as described in the symantec support docs.
Booted laptop and selected ghost image.
Laptop boots and ghost32 runs.
Starts to restore a previously created ghost image and dies after a couple of seconds.
After this I shut down the wds services restored my pxe boot setup to as it was before which is following I think it's DmMcoy's instructions.
Rebooted laptop, boots into dos ghost disk.
Restore same image I was trying above and it completes 100% without any issues at all.