Video Screencast Help

Ghost Boot Partition

Created: 27 Jun 2007 • Updated: 22 May 2010 | 28 comments
Total newbie here so RTFM might be an appropriate response.
 
I stumbled upon Ghost Boot Partition and it looks like it would save me the trouble of walking around to each PC and booting it from a USB Floppy in order to run Ghost client so I can multicast from the Ghost Server.  I found instructions on how to create the GBP image -- which I did -- and, um, now what?  What do I do with this image?  If I push this image to a PC won't it overwrite C: in favor of the new image?  If it resides in it's own partition on the HD, how to I get the client PC to boot to that partition rather than Windows?    :-?
Discussion Filed Under:

Comments 28 CommentsJump to latest comment

Triple Ace's picture
Hi WJason ,
 
 
You don't have to use Ghost Boot Partition at all.
Install Ghost Client on your client machines, from the Console (Remote Client Install).They are going to use Virtual Partition ,when Client machine needs to be rebooted to DOS,for image creating or cloning tasks.
When the client machine starts in virtual partition ,it uses a template that contains the DOS network drivers that match the clients computer NIC.This template is sellected automatically by Ghost when Console first detects the client machine.
 
Here is the link that may help you :
 
http://entkb.symantec.com/security/output/n1999102709342625.html
 
Cheers
WJason's picture
Thanks for the tip.  :-)
 
I've tried using Remote Client Install from Ghost Console and all I can get out of it is "Logon error".  I can use Windows Remote Desktop to log into the machine with no problem.  But the same credentials don't seem to work through Ghost Client.  :-|
 
Perhaps I'll try installing the Ghost Client manually.
 
Jason
WJason's picture
OK, I was able to install Ghost Client manually (copied Client.msi to the target machine and ran it).  I found the target using Ghost Console on the server; but it says the client "might not have the correct template" and the task (to restore an image to the target) fails.
David.P@TAMU's picture
Sounds like it is talking about the NIC driver template.  In the console, double click on the client in question.  The Client properties window will appear.  Click on the "Client" tab.  There is an option labeled "Network Settings when using Virtual Partition"  The "suggested template" may be wrong you may have to check it out and set it manually.
WJason's picture
I changed the NIC driver to be specific to the target machine, but it still doesn't work.  I'd like to change the user name but can't figure out how to do that.
WJason's picture
Hmm...I'm wondering if having Novell on the target computer is causing the "Logon error" reported by Ghost Console.
WJason's picture
I tried installing Ghost Client on a system which did not have Novell installed.  I still get a connection error.  I've set Windows to accept remote connections and indeed Remote Desktop has no problem accessing the target.  I'm thinking this is another of Ghost's features that simply doesn't work.
David.P@TAMU's picture
WIth regard to the username error...
 
Is this error coming from a task execution and a step fails?  Is the console displaying the message ? 
 
How/Where does the message come up and what were you doing/trying to do when you got that error.

Message Edited by David.Poprik on 07-02-200711:21 AM

WJason's picture
I installed Remote Client manually and then created a task to re-image the target.  The task starts....and runs forever.  I have to cancel it to get it to stop.
 
So, going back to just a simple Remote Client install:  I've turned on File and Print Sharing on the target.  Allowed remote connections on the target.  Have not installed Novell on the target.  I have a null password set for the local administrator account (for testing only).  From Ghost Console on the server I select Remote Client Install...  and browse to my target.  I add the target to the list giving the username "administrator" and no password.  Click Start.  I get "Connecting..." then after a minute "Cleaning up..." then a pop-up with "1 client failed to install."  I click [View Log] and normally I see "Connection error".  Today, I got
"7/2/2007 @ 1:51:50 PM   \\HPtargetname
Failed to install:
 \\HPtargetname  (20): Add logon right: Error when opening security policy - the computer might be running Windows 95, 98, ME or XP Home, or the specified account does not have sufficient administrative rights on that machine"
The target is in fact running XP Pro.
David.P@TAMU's picture
Im assuming you set a local admin password and tried it with that pass?  For the username are you doing builtin\administrator or *machinename*\administrator ?
 
I don't think the method of client install will change the inherant behavior of a tasks execution though.  Isnt logical for it to behave any differently no matter how you got the client on there.
WJason's picture
I set the local admin password to null.  When I add the machine to Remote Client Install, Ghost Console pops up a window asking for a user name and password.  I type in "administrator", leave the password blank and click [OK].  Remote Client install continues to fail.
David.P@TAMU's picture
I understand you set it to null.  For instance, using the "Autoadminlogon" registry entries doesnt get you in a machine when the password is a null.  Perhaps there is some issue with a null password.  Also, I was asking if you are doing a domain\username type of method like builtin\administrator or COMPUTERNAME\administrator with the console rather than just "administrator" for username.
cmg's picture
Make sure the Firewall module on your interface is not activated, or you have the proper port opened for the client.
Reg's picture

there is an issue when the admin pw is null when trying to do a remote client install.

put a pw on the admin account on the target pc and try to do the remote client install again

Reginald Robinson's picture
I can get remote client install to work by either disabling the xp firewall or enable file/print sharing. I have not tried it with null passwords as that is not my practice...testing or not.
 
my problem is after the remote install completed successfully for 2 clients....i could see them. I used one to create an image but then realized the reference machine was flawed and needed to modify the application. I did that and rebooted the client. When it came up...or since it came up....Ghost console cannot see the clients even though they are there.  I tried to run and inventory and it never completed. I deleted the tasks, and the machines...uninstalled the client from both, rebooted both. When the came up i reinstalled the client remotely and it succeeded. My problem is now i cannot see them at all in the console. What gives. I have tried cleaning the registry changing the names removing from the domain and nothing will cause it to appear...but i can install it remotely.
jVern's picture
I found that a password for the administrator account is mandatory when installing the client.
 
Another thing to make sure of is to turn off simple file sharing by going to My Computer>Tools>Folder Options and unchecking the "use simple file sharing" option at the bottom of the list.
 
Regards
Barista's picture

I stumbled across this thread, and wanted to find out some more :-)

I have tried several times without luck to use SGS 2.5 with client install. Everytime I need to ghost a new image or something like that, I get failed to virtual partition.
I have tried installing latest drivers for NIC and whatnot, so I figurered I´d rather install a ghost boot partition, but got stuck the same place at the thread starter.

How do you install a ghost boot partition???

In you would like to know more of the hw, it´s Dell Inspiron 9150/XPS400 without WOL :-(

ghostly's picture

I just spent an entire weekend trying to get this software to do anything. I can get the client installed remotely, but anything else fails. All I've been trying to do is start learning how to use this. I tried to simply run the backup task from one client on my home network. I've been reading everything I can find and have tried all of the different PreOS selections, added NIC drivers, basically trying everything nine ways to Sunday. The documentation is probably the poorest I've ever seen telling you nothing but what any simpleton could figure out with out a manual, and the knowledge base isn't much better. So far I'm quite unimpressed...

G-3Manticore's picture

hi ghostly,

what exactly was the error-message?

greetings

alexander emmer

ghostly's picture

First let me apologize for my initial post. I was rather digruntled by that time. The thing is I get no error messages. At first I was using WinPE and it would go as far as rebooting, starting the script then just hang there. After about a half hour, and Ghost telling me the task failed, I would just restart the machine. I started using PCDOS and it's not finding my DHCP server for some reason which I know is working. I've turned off all firewalls and my router (Linksys) isn't blocking anything I know of internally. I might work with it a little more I just wish there was more in-depth documentation.

G-3Manticore's picture

Can you give me your current version of Ghost?
Did you recompile the WinPE /WinPE 512 image, containing all network and mass storage driver?

greetings

alexander emmer

ghostly's picture

I'm not sure which version it's at (I'm at work now) but I ran LiveUpdate untill there were no more updates so it should be current. I recompiled a number of times after adding my nic driver. Even uninstalled and reinstalled the client afterward. Tried the dos driver and ndis driver with pcdos which is where i get no dhcp server found either way. Maybe it's nic itself causing the problem but there's no errors to point me in that direction. I did read about turning off plug and play os in the bios so I might try that. Getting stuck on such an intregral part of using ghost is just depleting my desire to learn and recommend it.

G-3Manticore's picture

Do you try PXE-Boot?
Are you using Ghost via Console, or do you use boot media, to start up the ghost-clone process?
Where is the Ghost-Console installed and where is the agent installed (OS).
Tell me the steps, how you proceed, when you want to clone a PC.

greetings

alexander emmer

ghostly's picture

I haven't tried PXE booting. I installed Ghost Console on a secondary server (2003), installed the client on a desktop remotely from there which went without a hitch, then I've just been trying to run the backup task from the server that I created for the default machine group it's in.

G-3Manticore's picture

There is nothing wrong so far ^^.
Can you give me the error message in ghost console, when the task stops?

greetings

alexander emmer

ghostly's picture

As I said, there is no error message. I finally got it to work. I'm not sure yet which of a few things I changed fixed it. Changed default options to Unicast, changed to Non Plug an Play OS in client BIOS. and something else I don't remember right now. Now I can spend another week fiddling around figuring out which thing allowed it to work....

G-3Manticore's picture

First of all, good job that this is working now.
Tell me, if you know something more about it.

greetings

alexander emmer

ghostly's picture

OK, I couple things I've figured out the hard way. It seems to be the setting in the BIOS of "non plug & play os" that corrected the problem with pcdos not working. During that whole process, I realized having multiple drives and many gb of data was causing time outs when using WinPE. (Must be reading data on all drives or something before it starts) I went back to basics and put an old drive in and loaded a basic install of XP with no other drives connected and WinPE works now, kinda. It completes the backup but when it's done it just goes to a blinking curser on the client instead of rebooting. Also the Console task doesn't complete and says failed athough the backup is actually completed. I'm gonna be out of 30 day trial period time before I get a simple backup to work properly. %>\