Hi,

It is not possible for Ghost to detect new computers and install the client, but in system of this size, having a group policy in the Domain would be a better solution. Ghost client can be installed silently using command line. There were some posts in the forum about this method.

Would that be a solution for you? Other option is looking at some kind of a remote execution script.

Krish

Command line is the best option i think,, i'm using active directory so i can make a group policy.

Which line do i have to add and where?

I installed client in image. When I install new computer in network it appears in console automatically...

I don't know if this is a proper way but it's works...

Thank you but no, i have to make an inventory for making images for alle computers so i need to know all hardware. Before i can start i need to install client on every system and place them in ghost.

Ok then using AD to distribute is easiest way. If you installed gss with defaults you can find msi package from folder C:\Program Files\Symantec\Ghost\ClientInstall (you dont need to do any scripts just a basic msi insallation policy)

But do i have to add them manually to the ghost console after installing the client on the machines?

In default settings client connects automatically gss. So they will pop up in your default machine group...

So if i'm right, you say , If I install ghost remote client on a machine,,  the machine will show up in default machine group.. Is that right?

Yes

If not, there is firewall blocking connection.

Well, i tried,, but when i install the client manually i can give op the computer name of the ghost server. Without filling in the computername it won't connect so the only conclusion is i need to repackage the client MSI to make in an filled in autoinstaller?

Weird, this has worked when i test it. Could somebody comment who knows what is needed to automatically find GSS server?

Are the client and server in same subnet?

Hi,

If you install without any parameters, it will connect to the first console it finds. In case if you have more than one Console, it may connect to the wrong console.


client.msi supports setting the property GHOSTCONSOLENAME (and the install path INSTALLDIR). You can install it with a command line similar to,


msiexec /i <path>\client.msi GHOSTCONSOLENAME="<name of console machine>" /qb


it will set the Console name in the client installation. You can find more info in manual page 588 "Installing from Command line"

Krish