Ghost Corporate Step-by-step
Symantec has been 100% useless. Their manual contradicts itself and the website. I just got Ghost CE and have been completely unsuccessful at creating an image. I wish to never visit the computer lab upstairs, but will settle for a working image. Could someone run through the basic steps? I've installed the Ghost Console on the main machine and the CLient Console on another. The main console doesn't see the other. If I can just get the two to communicate, I can get the others, I'm quite confident. But, since the Console doesn't see any others, I can't pull an image from that machine. If anyone knows of a good tutorial please let me know. If you can write one up, it would be great.
Thanks
Dan J.
Thanks
Dan J.
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
JoeW
20 years ago
Posted by:
JoeVrat
20 years ago
Welcome to the Ghost Haters Club Dan. We have the same problem of the Console not seeing the Client. (See my posting from 9/30.) We loaded the Client from the CD and from the Console and no matter how we do it the Console will not see the Client. The manual is of no help and the Symantec web site is even more useless. Plenty of people seem to have read my posting but no one has posted any suggestions.
Good Luck
Joe V.
Good Luck
Joe V.
Posted by:
JoeW
20 years ago
Posted by:
JoeVrat
20 years ago
Posted by:
beengone
20 years ago
I can give a small update as I have this working for our basic immeidate needs. Symantec is useless and they misword EVERYTHING! They just want you to pay for their $1,900 training. We should write a manual and sell it at $500 a pop. But, that would take us understanding this. . .
Anyway. So far, I am able to install the client and make it work ONLY if I install from the Ghost Console. GOing to the machine has panned out to nothing so far. Also, I don't have the machines on a domain, just in a workgroup. The manual seems to go back and forth on this saying it has to be in a workgroup to get started but later that it can automatically take them out of the domain. blah blah. I've not worked with the configurations or any other good options and have to still learn that.
Maybe someday they will rewrite the program to be useful. Maybe call the command to create an image container "create" or "save" instead of "open." Give me a break!
Anyway, hope that helps. (BTW, I"ve used it on Win 2000 and XP both pro.)
Anyway. So far, I am able to install the client and make it work ONLY if I install from the Ghost Console. GOing to the machine has panned out to nothing so far. Also, I don't have the machines on a domain, just in a workgroup. The manual seems to go back and forth on this saying it has to be in a workgroup to get started but later that it can automatically take them out of the domain. blah blah. I've not worked with the configurations or any other good options and have to still learn that.
Maybe someday they will rewrite the program to be useful. Maybe call the command to create an image container "create" or "save" instead of "open." Give me a break!
Anyway, hope that helps. (BTW, I"ve used it on Win 2000 and XP both pro.)
Posted by:
swiss
20 years ago
Boys, boys. How many clients do you run? Which version of GHOST? Ghost 6,7,8,9.
The main purpose of Ghost ist booting from a DOS disk or CDROM or via a PXE Boot DHCP/PROXY server 8Nothing to do with internet proxy server) then connect a network drive to a server. Finally start ghost and dump or pull a image from a client. The manuall for the DOS options contians everything. Take a closer look at the product and you will find it simply a perfect product.
The main purpose of Ghost ist booting from a DOS disk or CDROM or via a PXE Boot DHCP/PROXY server 8Nothing to do with internet proxy server) then connect a network drive to a server. Finally start ghost and dump or pull a image from a client. The manuall for the DOS options contians everything. Take a closer look at the product and you will find it simply a perfect product.
Posted by:
mikec
20 years ago
When you are installing the Ghost client software, it will ask you to input the name of the ghost console system. Otherwise, when I don't input the name of the console system the workstation is never seen by the console.
One more thing, a little known secret with Ghost, if you want to see if the workstation is talking to the console, (on the workstation) hold down the Ctrl Key, and move your mouse to the upper left hand screen, in a few seconds you will see the Ghost icon pop up in the system tray. Click on show debug console. You will then see if there is communication with the Ghost Console computer. (note: it takes a few seconds to report the comm with the console, so give it about 30 seconds)
HTH
One more thing, a little known secret with Ghost, if you want to see if the workstation is talking to the console, (on the workstation) hold down the Ctrl Key, and move your mouse to the upper left hand screen, in a few seconds you will see the Ghost icon pop up in the system tray. Click on show debug console. You will then see if there is communication with the Ghost Console computer. (note: it takes a few seconds to report the comm with the console, so give it about 30 seconds)
HTH
Posted by:
GYMARINES
19 years ago
Posted by:
GYMARINES
19 years ago
Posted by:
Dr. Soup
19 years ago
We have a similar problem here. The only way we have gotten the Ghost console working was to have WINS running on our network. We implemented WINS specifically for this purpose, but then the network guy decided that WINS wasn't necessary - so out of luck again.
One thing you might be able do to get around this is to have somebody at the remote site boot from a network Ghost Boot Disk. Have that person specify the IP address of the ghost server when prompted and have it set to deploy using Directed Broadcast instead of multicast. Don't actually use the console here, because that would be useless, set up the task directly in GhostCast Server. Also, you may have to specify the switch "-jaddr=server IP address"
Or like I said - WINS makes it all work nicely here.
By the way - we have a Windows 2000 network using Ghost 8.0
One thing you might be able do to get around this is to have somebody at the remote site boot from a network Ghost Boot Disk. Have that person specify the IP address of the ghost server when prompted and have it set to deploy using Directed Broadcast instead of multicast. Don't actually use the console here, because that would be useless, set up the task directly in GhostCast Server. Also, you may have to specify the switch "-jaddr=server IP address"
Or like I said - WINS makes it all work nicely here.
By the way - we have a Windows 2000 network using Ghost 8.0
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.