ecmastrean
Visitor.
633 views

WinPE Imaging Operation Failed

On several Dell models such as the OptiPlex 5060, Latitude E5450 and 5490 computers we are getting errors when computers are flagged to image that the "Imaging operation failed. Could not connect to server." However the computer just communicated with the server to see it was flagged for imaging work and the boot.sdi and winpe.wim files were downloaded. If I boot into maintenance mode and check for imaging work, sometimes I get the error, other times it begins to run the preboot script. I may also have to flag the computer again then check for imaging work once in WinPE maintenance mode for it to image. However in every case I can exit "zenworktodo.exe" and ping the imaging server from the cmd window and it gets a reply from the imaging server. So I don't understand why imaging is hit and miss. I first noticed this problem more often when I modified winpe.wim with NIC drivers for the Microsoft LAN adapter so I can image Surface Pro's. The original winpe.wim file only had the Inel I219V NIC driver for OptiPlex 5060's. I thought the two NIC drivers could be causing conflicts so I copied the original wim files with only the OptiPlex 5060 NIC drivers back to the server thinking the problem would be solved. However even after reverting to the previous winpe.wim files I still get the "could not connect to server" error more often than not. Our winpe.wim file contains the following additions:
WinPE-NetFx
WinPE-PowerShell
Intel I219V (64-bit NIC driver for OptiPlex 5060's

Any idea why zenworktodo.exe cannot consistently communicate with the imaging server?
Labels (1)
0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Re: WinPE Imaging Operation Failed

My guess is some type of timing issue.....
Maybe the NIC is taking a long time to get an IP address?


ecmastrean;2496312 wrote:
On several Dell models such as the OptiPlex 5060, Latitude E5450 and 5490 computers we are getting errors when computers are flagged to image that the "Imaging operation failed. Could not connect to server." However the computer just communicated with the server to see it was flagged for imaging work and the boot.sdi and winpe.wim files were downloaded. If I boot into maintenance mode and check for imaging work, sometimes I get the error, other times it begins to run the preboot script. I may also have to flag the computer again then check for imaging work once in WinPE maintenance mode for it to image. However in every case I can exit "zenworktodo.exe" and ping the imaging server from the cmd window and it gets a reply from the imaging server. So I don't understand why imaging is hit and miss. I first noticed this problem more often when I modified winpe.wim with NIC drivers for the Microsoft LAN adapter so I can image Surface Pro's. The original winpe.wim file only had the Inel I219V NIC driver for OptiPlex 5060's. I thought the two NIC drivers could be causing conflicts so I copied the original wim files with only the OptiPlex 5060 NIC drivers back to the server thinking the problem would be solved. However even after reverting to the previous winpe.wim files I still get the "could not connect to server" error more often than not. Our winpe.wim file contains the following additions:
WinPE-NetFx
WinPE-PowerShell
Intel I219V (64-bit NIC driver for OptiPlex 5060's

Any idea why zenworktodo.exe cannot consistently communicate with the imaging server?
0 Likes
ecmastrean
Visitor.

Re: WinPE Imaging Operation Failed

Maybe. Is there a way to build in a delay from when the winpe OS loads to when it tries to contact the server for imaging work?
0 Likes
ecmastrean
Visitor.

Re: WinPE Imaging Operation Failed

Maybe. That was my thought too. Is there a way to add a delay from when the winpe OS loads to then it checks for imaging work?
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: WinPE Imaging Operation Failed

Top of my head I don't know.....
But I'm inquiring
0 Likes
ecmastrean
Visitor.

Re: WinPE Imaging Operation Failed

Thank you for providing the updated zenworktodo.exe file as a FTF. That solved the problem of not getting an IP fast enough for WinPE imaging.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.