Network Error in Client Full System Restore

Question

Hi,
I've been attempting, as a test, to restore a full system backup to a client computer using a boot flash drive. When I attempt to do so, I get a "Unknown Network Error" at the point where the client has attempted to contact the server, been unable
to and offered the opportunity to enter a name or an IP address. When I enter either one, I immediately get an "Unknown Network Error". There's no error number or other specific identifying informations.
Details:
The client computer is a UEFI motherboard PC running Windows 7 Professional. It connects with no difficulty whatsoever on a normal basis to the Windows 2012 R2 Essentials server. It gets backed up every night by the server over the network with no problem.
When I boot from the Network Client Computer Restore USB key, everything works fine except that it is unable to find network drivers. When given the chance to load missing drivers, I use the "Drivers for Full System Restore (from the full system backup)"
on another USB key and they are found just fine.
Then when we get to the point of searching for the server, it appears to look for 30 seconds or so, then a dialog comes up asking whether to search again or if I want to enter a IP or name. Searching again doesn't yield results, and when either an IP or
the server name is entered, I get the "Unknown Network Error".
I feel certain there must be some logging that is either available or could be turned on if I knew how. I feel concerned that I would not be able to restore my client computer if something were to happen. Any ideas would be greatly appreciated.
Jeff

Answer 1

Hi Justin,
Thanks for your response. I'm sorry that I didn't see it sooner - I guess I assumed I'd get an email if there was a response...
Anyway, at the time when the error occurs, the OS is not running. We have just booted via PXE over the network and started the "Full System Restore" Wizard, so it is not possible to "ping" the server. However, the fact that we successfully
booted via PXEs tells me that basic connectivity exists to the server, because otherwise the PXE boot wouldn't work.
Thanks for the pointer to the logs - I'll check them.
What I have done since I last updated was to do a few experiments. I added a Windows 7 boot image and install image with the Windows Distribution Service, so that on PXE boot I'm given 2 options - a Full System Restore and a Software Install.
I also roped another PC into service, one that is running from BIOS rather than UEFI. On that PC, both the System Restore and Software Install via PXE boot work fine. This tells me the server is at least nominally working, and that the problem is related
somehow to the specifics of the PC being connected. Could be server setup still, could be something on the PC.
On the computer with the UEFI, neither Full System Restore nor Software Install works. However, there is at least a clue in the error response from the Windows Setup - I get a lengthy error message that essentially says that \Windows\Boot\EFI\bootmgr.EFI
is corrupted. I'm not clear whether at this point we are referring to a file extant on the PC or one that is being downloaded that's being claimed to be corrupted.
This took me down a path in which, to eliminate variables, I changed the boot drive on the UEFI system from MBR to GPT. No joy. Also broke up my mirrored drive and changed the SATA from RAID back to AHCI. Also no joy. But everything I am reading is leading
me to believe that the problem has to do with the fact that my target PC has a UEFI BIOS. I continue to investigate - and will look through the logs you mention.
Jeff
Update 8/24/2014
Made some progress yesterday. I'm now able to use Windows Deployment Service to deploy Windows 7 over the network to the UEFI computer. I had to do two things to get that to work.
Turn off driver signing in the UEFI bios. That got me past the error screen complaining about a corrupted driver (which I'm pretty sure I don't have). But then it got hung up saying it couldn't find a driver for the network.
To fix that, I added the driver package to the boot image using the tools in the Windows Deployment Service applet.
After that, it found the server just fine, allowed me to authenticate, and would have proceeded to install Windows 7 if I hadn't aborted.
I then added the exact same driver package to the Full System Restore boot image, but it made absolutely no difference. Exactly the same symptoms as reported previously.
So, where am I and what do I know?
I can do both a Remote Windows 7 install and Client Full System Restore using Windows Deployment Services on an X64, BIOS based computer.
I can do a Remote Windows 7 install to my X64 UEFI based computer.
When I attempt a Client Full Restore to the X64 UEFI computer, I get all the way to the Full System Restore Wizard, which tells me that it can't find network drivers (even when they've been installed to the boot image). It finds network drivers when provided
via a USB key, but then when the Wizard looks for the server, it's unable to find it. When a manual option is presented, and I enter the server's IP address, I get an "Unknown Network Error" popup message, and I can't proceed further.
On the UEFI computer, I've tried all combinations of Compatibility Support Module (CSM) settings, but they make absolutely no difference to the Full System Restore process.
I've also tried converting the boot disk from MBR to GPT, didn't make any difference.
I "unmirrored" my mirrored RAID drives and changed the SATA bios from RAID to AHCI. Made no difference.
So, at this point I'm kind of stuck. I'm out of ideas for things to try for now. I did look at the logs as suggested, but didn't see much of anything relative to WDS. Possibly logging has to get turned on?
As always, any help or ideas would be much appreciated.
Jeff