Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Ghost Personal vs. Enterprise

Status
Not open for further replies.

Dreddnews

Technical User
Nov 17, 2002
83
US
One of the companies I work for requires Ghosting of computers so that we can keep them all the same. The PC's are different in hardware. I have used SysPrep to remove the hardware layer, yet when I use Ghost 2002 and create the image, upon restarting a different pc with the image placed on I get the following error: Inaccessible_boot_disk. I have read symantec's help and they state options that do not work for me with personal edition. I am wondering will it even work to have different hard drives sizes with personal or do I need to switch to Enterprise. Please help!
 
Use Ghost daily to clone W2K drives. Things to check/make sure of...
1. If using sysprep (which is NOT required), make sure it's version 1.1 or later. Version 1 will cause this error.

2. Again if using sysprep, make sure to modify the inf file properly.

3. Use Ghost Corp Ed. 6.5 or later, which solves all these problems...

Rick
MCSE (NT & 2K), A+
 
How are you making the images with Ghost 2002? I have a copy, and it will only let me put the image to another hard drive or Cd-r, which to me makes it worthless unless I want to be switching out hard drives all day.




 
I store the images on CD-R. As for using Sysprep, I am using 1.1, but I'm not quite sure how I am to edit the inf file to allow a different driver for the HD controller.
 
You might want to make sure that your BIOS are up to date. I've been arount that situation by putting the latest BIOS version on the target PC.

Mikhael
 
What it boils down to... Will my image ever work if I am placing the image on a PC that is has a different IDE controller? I will try any work around...
 
No your image must have the same controllers as the system that you are loading it on. An unfortunate limitation
 
Not quite correct Wipeout25. The whole idea of editing the inf file is to include the correct entries for the new systems IDE controller(s). Symantec's site explains this in good detail.

Rick
 
You don't happen to know the correct site to find that information for editing the sysprep inf correctly do you?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top