Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Unable to access file error at end of imaging job

Created: 16 May 2013 | 10 comments

I got two demo PCs from Dell.  A laptop and a desktop.  Ran the laptop up yesterday and it made it 100% through the imaging process and then errored out at the end saying it was unable to access a file.  Tried a few things then put a different HD in it and it imaged and finished fine.  Assumed it was just a bad drive.  Just ran the new desktop up and it did the exact same thing.

These two are the first two we have gotten with the UEFI stuff in the bios, which I know nothing about yet.  I set it to legacy mode and both imaged and finished fine with the second HD that didn't come with them from Dell.  Is there something in there that "locks" the drive that may be causing my image not to work?  We use a Linux image invoker instead of win PE but I've never seen this before and the fact that they are the fist two UEFI systems and they both did the exact thing has me puzzled.

Operating Systems:

Comments 10 CommentsJump to latest comment

Thomas Baird's picture

Well, I don't know where it fails, but I do know that DS (both versions) don't yet support UEFI.

Thomas Baird
Enthusiast for making things better!

 

David Zell's picture

I have it set to legacy.  It has to be something that the PC did to the drives or the drives themselves though b/c in both systems they  imaged fine when I put different stock drives in them.  They are all just normal SATA drives though.  The failure occurs right after 100% of the imaging file transfer finishes.

Thomas Baird's picture

Is DeployAnywhere enabled?  If it is, turn it off and try again just in case.  Also, look at the imaging logs (ghosterr.txt and/or the logs in program files\altiris\altiris agent\logs) to see if there is a reason given.  It sounds like something we do post imaging and it may be solvable.

Thomas Baird
Enthusiast for making things better!

 

David Zell's picture

DeployAnywhere is not enabled.  The only log file I can get to is the one I attached to the first post.

Thomas Baird's picture

RDeploy?  Ghost is better, especially for newer OS's.  hmmm...  That log is on the server.  The other logs are on the client.  That said, I'm making an assumption on what version of DS you have.  What version DO you have?

Thomas Baird
Enthusiast for making things better!

 

David Zell's picture

It is something to do with something Dell did when putting Win 8 on it because after I did a DOD wipe on the drive it imaged fine.  Again, I don't know how UEFI and secure boot and all that works yet, but I still suspect it has something to do with it.

I have 6.9.

Thomas Baird's picture

Interesting.  DS 6.9 couldn't find the drive...  hmmm...  I'll ping around.  That really is interesting.  Thanks for posting that.

Thomas Baird
Enthusiast for making things better!

 

jbeale53's picture

I have a Lenovo X1 Carbon that was pre-loaded with Win8.  I couldn't PXE boot or anything until I switched it into legacy mode in the BIOS, but I still can't get it to image - image deploys, but it won't boot at all.  

I just now realized that the drive was partitioned with GPT instead of MBR.  I booted into WinPE and cleaned all the partitions off, and I'm trying to image it again now.  But I think the root of your problem has to do with the drive being partitioned with GPT instead of MBR, which would explain why your DOD wipe seemed to fix it.  I've been doing a lot of looking aroudn for ideas on how to get it back into MBR mode automatically, but I havent' found anything yet.  I'll post here when I do.

captcomputer's picture

I know in our imagin process we use DiskPart to Clean the drive, Set a partition, and then make the drive Active before laying down the image.  You may try going that route to see if that doesnt get you a better result.

We have imaged a Lenovo X1 Carbon and dont have an issue.

Now we do have an issue imaging a machine that was previously Win7 and the using that same process to lay down XP.  We have to image it twice to get to the end result.

 

Indrek_K's picture

It is quite regular thing I see.

Issue is that these computers come with Win8 installed or was installed.

So they have GPT partition, instead MBR as Win7. (Win7 can only handle the GPT part with virtualized MBR part, GPT was introduced because of the new ADF)

So easiest thing would be: PXE the client (assuming it ha only 1 HDD) diskpart select disk 0 clean