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

Ghost/Altiris Issue: Unable to Use Ghost Client on a Machine Previously Imaged by Altiris

Created: 25 Sep 2008 • Updated: 11 Mar 2009 • 6 comments
Randall Newnham's picture
+1 1 Vote
Login to vote

I ran across this issue when a customer called in about it. The alterations that Altiris does to the MBR interfere with using the Ghost client on that machine afterwards.

It creates an error message: "Error 15210: NTFS signature, should not be FAT32".

What we found to resolve the issue was to reinitialize the MBR through use of GDISK or FIXMBR.

Created document number 2008091609500360: "Error 15210: NTFS signature, should not be FAT32" occurs when using Ghost on a machine that previously had an Altiris image deployed to it.

In that kb article, I attached (in the Internal Notes section) a link to a legal case between ALtiris and Symantec (when they were different entities) wherein the alteration to the MBR by Altiris is described. Altiris-side people may already be aware of this, but this was new to me.

Thank you,
Randy

Comments 6 CommentsJump to latest comment

paulsmith's picture

Yes I have seen this issue and found that just running fdisk /mbr before running the ghost.exe takes care of this.

0
Login to vote
Randall Newnham's picture

Yes, I should have included that as well. I focused on GDISK primarily because it is bundled in the Ghost software and included on our Windows PE boot media. I will add this to the kb article I created.

0
Login to vote
arjain's picture

Hi Randall,

i can't locate the atatched document refered in your article.
Kindly let me know where it is shared

Thanks
arjain
www.syspanacea.com

~ SQA Manual - Crafting tomorrow

If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.

0
Login to vote
Randall Newnham's picture

Arjain,

Here is a link to that article:

http://caselaw.lp.findlaw.com/scripts/printer_frie...

Thank you,

Randy

0
Login to vote
misterka's picture

add a text file named diskpart.txt to your boot disk or image.

it should contain:
select disk 0
clean

then you can run:
diskpart.exe -s x:\diskpart.txt

I've found this is the quickest way for me to run it in a job.

+1
Login to vote
arjain's picture

Thank you Randall and misterka

~ SQA Manual - Crafting tomorrow

If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.

0
Login to vote