Ghost/Altiris Issue: Unable to Use Ghost Client on a Machine Previously Imaged by Altiris
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
About Endpoint Management Community Blog
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments
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.
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.
cant locate attached doc
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
~SysPanacea - Remedy for PC problems.
If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.
Link to article
Arjain,
Here is a link to that article:
http://caselaw.lp.findlaw.com/scripts/printer_frie...
Thank you,
Randy
Can also use diskpart
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.
Thanks
Thank you Randall and misterka
~SysPanacea - Remedy for PC problems.
If a forum post solves your problem, please flag it as a solution. If you like an article or blog post vote for it.
Would you like to reply?
Login or Register to post your comment.