How to hold aside the GoldMine data directory and database on Undocked machine so that it can be reinstalled on the same machine or be moved to a replacement machine?

Version 1


    The information below can be used in a couple of scenarios:

    1) An Undocked machine is going to be reloaded due to general machine or Windows performance issues, general corruption, etc.
    2) An Undocked machine is going to be replaced with a new machine for the same user.



    NOTE: The information below is a high level overview of the project.  This does not contain every detail of the process but includes enough information to accomplish the task outlined int he given scenarios.

    NOTE: If the scenario is that the Undocked machine is being replaced with new machine for the same user then it is CRITICAL that:

    1) GoldMine is installed on the replacement machine to the same path as the original machine.
    2) SQL is installed on the replacement machine following the GoldMine Premium Edition Install Guide.

    1 - Do final synchronization with GoldSync server.
    2 - Ensure that recent changes made to undocked machine did synchronize to the GoldSync server.
    3 - Make backup of the GoldMine data folder usually located at C:\Programdata\Goldmine.  This path may differ on the undocked machine so please ensure the proper directory is being backed up.
    4 - Make backups of GoldMine database(s) using SQL Server Management Studio.
    5 - Ensure the same or newer SQL Server install files are being used. If there is any question please reference the GoldMine Premium Edition Compatibility Matrix.  Depending on the SQL version being installed it may be necessary to obtain a license for this, please check in advance with the  Administrator (For example if installing SQL Server Standard Edition vs. Express Edition will require a SQL license).
    6 - Ensure the same version and build GoldMine Premium Edition install files are available to use as the previous install.
    7 - Ensure the full undocked license with keycode is obtained from the GoldMine Administrator from the office the undocked machine synchronizes to.  The Administrator can obtain this by logging into GoldMine on the GoldSync server as a MASTER rights user Tools >> Configure >> License Manager >> Highlight specific undocked "U" license >> View License >> 'I agree' >> copy and send in text file to the undocked user in an email.  This is important as the license shown locally on the undocked machine is only a partial license number and required for a proper synchronization. 
    8 - Reload the Undocked machine as desired and ensure all Windows Updates are done.  In the case of a machine replacement ensure that all Windows Updates are done as well.
    9 - Install SQL Server. Please use the GoldMine Premium Edition Install Guide section about installing Microsoft SQL Server (Depending on the version of SQL being installed this may not match identically but the key items are to enable the SQL SA account, use mixed mode authentication, and follow the post installation configurations).
    10 - Update SQL Server to the latest service pack available regardless of the SQL version being installed.
    11 - Install the exact version and build of GoldMine Premium Edition that was installed on the undocked machine to the same path as the previous install/old Undocked machine.  When prompted use the license obtained from step 7 above.
    12 - When installing choose to install a new database called TEST or DEMO with demo data.
    13 - Verify that GoldMine functions on the reloaded/replacement machine with the demo data.
    14 - From the GoldMine folder backup created in step 3 above copy the following files and folders:
    Folders: Mailbox, Reports, Setup, Speller, Sync, Template, TmpLinks
    Files: all .ini files EXCEPT gm.ini and dbalias.ini, all *.bin files EXCEPT flags.bin, LicenseGMxx.bin.  ***DO NOT COPY any .exe, .dll, or .xml files if present***
    15 - Put these files into the new GoldMine data directory generally located at C:\Programdata\GoldMine and click "yes to all" when prompted to overwrite.  If a different directory/folder is being used from the previous install or machine place into the same directory/folder as previously used.
    16 - Restore the SQL .Bak File(s) to empty shells of the same name as the original GoldMine database(s) in SQL using SQL Server Management Studio.
    17 - Launch GoldMine as a MASTER user and create an alias - to the restored .bak file(s)/database(s) from the old install.  This is done in Tools >> Databases >> Alias Manager.
    18 - Attach the GoldMine database(s) in Tools >> Databases >> Open Database >> Attach.
    19 - Open the restored database(s) using Tools >> Options >> Login tab.  Change the "GoldMine database" and "Default contact database" to the restored database.  At this time GoldMine will log the user out and it is necessary to login again as a user with MASTER rights.
    20 - Ensure GoldMine is connected to the correct  restored database by looking in Help >> About GoldMine >> 'System' button >> The entries for "GoldMine Files" and "Contact Files" need to match the name of the created aliase(s) for the restored database(s).
    21 - Verify that GoldMine functions normally including opening of templates, linked documents, and email attachments. NOTE: If multiple contact set databases are used then please ensure the other contact sets open and function correctly as well.
    22 - Make new SQL backups of the GoldMine database(s) and the GoldMine folders (the default GoldMine folder locations are C:\Program Files (x86)\GoldMine and C:\Programdata\GoldMine.
    23 - Login to GoldMine as the "normal" undocked user and recheck data and verify functionality.
    24 - Attempt to synchronize. 
    NOTE: At this point it may be necessary to obtain a verification code from the GoldMine Administrator in the GoldSync office. Please follow Knowledge Article 18513 for "Verification code" error. Especially when using not the original Undocked Users License but for example the Host license just for a quick installation there will be an error about "Same serial number not allowed". Please follow Knowledge Article 17900 for "Same serial number not allowed".