Deployment Solution

Here is the description of the problem.

 

Currently using Altiris eXpress Deployment Version 6.9 (Build 453) Service Pack 4

We have our images on a NAS, so it is shared off our server (Call it Srv2) which hosts the Atiris and PXE services.  Recently, it was decided to have the NAS shared off of another server (Srv4) as we were seeing some issues with the share from the NAS.

The images are .gho files, so I can't use the Altiris image browser to see if there is a file opening problem, but so far, every time we try pushing an image, the response is:

 

Usage Error 10010

Cannot open image file

\\srv4\it\images\laptop\x201win764\201win764.gho []

 

Any ideas?

With the ghost executable, there should also be an executable for Ghost Explorer.  This should allow you to open the GHO file to ensure that the file is not corrupt.

I would also review any GHOSTERR log files for other clues.  Another item you might try is using the 8.3 filename format just to rule out the long file name from being the problem.

The following article should provide some insight into the error.

Error: "10000, 10010, or 10017 - cannot open dump file" while saving an image file, 

http://service1.symantec.com/SUPPORT/ghost.nsf/docid/1999010412584225&src=w

Unfortunately, this is not the correct solution.  The issue is reading from an created dump file, in this case, an established image file we have used in the past when the source location was on a Windows 2003 Server.  The images currently reside on a SAN that got its connection relocated to a Windows 2008 server.  Since then, the problem we have been seeing is that we get an unknonw 10010 error, versus the standard 10010 reference error.  The unknown being that the [] has no information, where as the normal error usually contains a Win32 or some sort of error message.

To be clear, I wasn't presenting a solution. The article states why the error code might be presented. You'll need to do the analysis on whether those areas are the cause. While the error is most likely caused by permissions on the network location, you should look closer at that article.

I did look over the article.  We did check on the permissions as it was the very first thing we did.  The article also focuses more on creating the image versus actually trying to access the image to restore onto a computer.  The current issue is our ability to access an establish image file to put onto a computer, versus taking an image from a computer and storing it on the SAN/Network.

So apparently, the PXE configuration had to be rebuilt from scratch with regards to the 'access' locations.  In this case, a new share was created for a specific location of where the files were and the PXE was then configured for the WinPE to 'know' of that pathing location.

So in the future, the WinPE would have to be rebuilt and reconfigured on PXE should the share location path of the image were to change in order for the client to be able to access the images.