Endpoint Management & Virtualization BlogsRSS

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

September 25th, 2008

Filed under: Ghost Solution Suite, Compatibility, Endpoint Management and Virtualization

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

0 votes

paulsmith

1 year 8 weeks ago

Yes I have seen this issue

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

0 votes

Randall Newnham

1 year 8 weeks ago

KB article will be updated

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 votes