Ghost Solution Suite

 View Only
Expand all | Collapse all

Moving the console

  • 1.  Moving the console

    Posted May 24, 2006 11:02 AM
    We are in the process of replacing the PC that is currently running our Ghost Console, what files do I have to move over to the new PC so I don't have to setup the machine groups, tasks, etc again? I've done this a few years ago and I remember only having to move a couple of files and everything was all set to go. Any help would be appreciated, thanks.


  • 2.  RE: Moving the console

    Posted May 24, 2006 05:17 PM
    If you use the same version of ghost console on your old and new machines, you only need to copy one file cross, SYMANTECGHOST.db. I've tried before and it worked.

    Alan


  • 3.  RE: Moving the console

    Posted May 24, 2006 05:27 PM
    That helped, thank you, but the console is still registered for 0 client connections, is there a way to get this back or do I have to register my licenses again? Thanks again.


  • 4.  RE: Moving the console

    Posted May 24, 2006 06:00 PM
    The important licensing information is contained in the database (for all existing releases - this is something that may change in the future, but for now it's true. Provided that you moved the database successfully, I'd expect that to move fine.

    You should also move the PUBKEY.CRT and PRIVKEY.CRT files from the original server install, since they are part of how the clients indentify the server they are associated with.

    Moving the database is also something we made a little harder in GSS1.1, because we randomized the database usernames and passwords a little. If you're using GSS1.0 or Ghost Enterprise 8 then you can copy the files but for 1.1 there's some addition process discussed here:
    http://forums.veritas.com/discussions/thread.jspa?threadID=63051


  • 5.  RE: Moving the console

    Posted May 25, 2006 08:53 AM
    I followed the instructions but when I go in to the registry editor and navigate to the HKEY_LOCAL_MACHINE\Software\Symantec\Symantec Ghost\ key there is no NGServer key to export.


  • 6.  RE: Moving the console

    Posted May 25, 2006 08:58 AM
    If you are having problems dealing with Ghost DB passwords please leave your email in the thread and I will send you a script that allows you to do the following:

    1) with no arguments, it retrieves the current user account name and password used by the Ghost Console to access the configuration database.

    2) with one argument, it sets the password for the user account used by the Ghost Console to access the configuration database

    3) with two arguments, the first being the string "dba", it will allow a password to be set for the built-in DBA user account that some existing users may have code that depends on.

    In Ghost Solution Suite 1.1 and above, this user account is disabled at installation time for additional security; running this script allows it to be re-enabled.

    Mr Fabietto
    http://spaces.msn.com/fcerullo


  • 7.  RE: Moving the console

    Posted May 25, 2006 09:44 AM
    Will this help transfer the licensing information from the old console server to the new one?


  • 8.  RE: Moving the console

    Posted May 25, 2006 05:42 PM
    > I followed the instructions but when I go in to the
    > registry editor and navigate to the
    > HKEY_LOCAL_MACHINE\Software\Symantec\Symantec Ghost\
    > key there is no NGServer key to export.

    On the original machine, if you run the ngserver application at all after exporting the credentials it will wipe this area of the registry out (that's a safety feature to avoid a situation where they can be grabbed by anyone inappropriate). However, as administrator you can re-run the application with the "-export" switch at any time to have another crack at grabbing the credentials yourself.


  • 9.  RE: Moving the console

    Posted May 26, 2006 08:23 AM
    I'm logged on as the administrator and tried the instructions again and still no ngserver entry. I'm not running ngserver again that I know of.


  • 10.  RE: Moving the console

    Posted May 26, 2006 12:26 PM
    I went back in to the console and now everything is working fine, I'm not sure what happened but I'm back up and running. Thank you to everyone who helped.