Ghost Solution Suite

 View Only

  • 1.  Forcing Ghost Client to talk to a specific Console Server

    Posted Mar 11, 2009 05:12 PM

    I am the Lab manager for a University and we image our lab computers once a term.

    In preparation for this I installed the ghost client onto all of my lab computers. I ran the installer using the following command.

    msiexec /i client.msi /q GHOSTINSTALLTYPE="Client" GHOSTCONSOLESERVERNAME="myghostserver" /l* c:\ghost.log

    In the ghost.log that was created the 8th to last line reads:

    Property(S): GHOSTCONSOLESERVERNAME = myghostserver

    Only 10 of the ~250 computers I pushed this installation to are talking to my Console server. The others seem to be talking to other Consoles on campus (according to info in the ngctw32.log in the Ghost program folder)

    Other than the installation switch I already tried (and that seems to have been ignored) How can I force the client to talk to my Console and my Console alone?

     



  • 2.  RE: Forcing Ghost Client to talk to a specific Console Server
    Best Answer

    Posted Mar 12, 2009 08:42 AM

    If you are laying a new image down you can take the pubkey.crt from your server and using ghost explorer replace the image's pubkey.crt with your server's pubkey.crt and when the image is restored it will talk to the server that matches the pubkey.crt. 

    To do this use ghost explorer to open your ghost image.  You can incert your pubkey.crt to the c:\program files\symantec\ghost folder.  (it can be found in this folder on the server also.)

     

    If you are needing to manipulate machines that already have the client installed like the ~ 240 that the install didn't work on you can replace their pubkey.crt with the crt from the server you want to have them talk to.  Symantec has a make shift batch file that you can modify with the computer names that will do this across the network.  

    http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/2008070209594960

    You can also use your console to push out the client using the remote client install and then these machines will have reported to the correct server right off the start. 

    You can also use the remote client install to push a new install to these existing machines and it will update the client to talk to the correct server. 

    Hope this helps

    Cheers.