Ghost Solution Suite

Is there a way to move all my settings (ie: tasks, groups, DOS templates, etc)  for the Ghost Console on one computer to a different computer?

Thanks for your help,

Ryan

The product contains a collection of utility scripts to do this kind of thing, you can read about the backup script here, and the latest version of the scripts are available from Google Code, the most convenient form being in a zip collection you can download and expand to replace the old out-of-date versions that are bundled with the GSS product.

Copy the Priv and Pub keys and the DB?  Isn't that the process???

One of the things we do at GSS install time is a process similar to the public-key creation, but for within the server machine - create uniquely named accounts and passwords for the GSS server and console to use to access the database, instead of relying on hardcoded passwords or leaving the installation default DBA password for the Sybase database in place. The database account credentials are stored in a particular place and there's a very specific procedure for moving those along with things which the scripts manage, including differences between GSS versions.

Indeed, the reason I originally wrote these scripts was that after GSS 2.0 released with this enhanced security, I developed the manual procedure for exporting this and it was complex enough that it needed automating, which I did while on a bit of vacation time I was forced to take once the release has settled down. One of the additional reasons I sought (and was eventually granted, although it took over six months) approval to release these as open source was that it demonstrated how to gain scripted access to the console database through this additional security.

Of course, the scripts also work around issues such as UAC problems which complicate the process of moving things from place to place, and on the backup side they use the SQLAnywhere database backup tools to obtain a copy of the database so it can do all this without taking the GSS service down during the process.

Once I had all this in place, and the scripts could safely snapshot the state of a running system, they then allowed me to write more example scripts which did maintenance on the GSS console database to fix errors left behind due to oversights in the console itself, since those could often be resolved those in the field through script without needing new code (which I wasn't the primary maintainer for - the console and the database schema were the work of Slawek Kajetanowicz who was my main co-creator for the GSS management environment, and who like me wrote, extended and maintained our part of GSS from 1998 through 2009).