Migration - Lucity Config

Jonathan Semones -

  1. Access the location of your old Lucity Server share.
  2. Make a copy of the Config and Reports folder.
  3. Open the location you are moving the Lucity Config to.
  4. Create the Lucity Server share.  It should be called LucityServer.
  5. Share this folder
    • Share Name: \\<servername or aliasname>\ LucityServer
    • Security:
      • Administrators - Share should have an Active Directory Group or a set of Lucity Administrators that has Read and Change permissions.
      • Services User - Share should include the user that runs your services
        • If following our suggestions it should the the <domain>\Lucitysvc user.
        • The user you use must have Read and Change permissions to the share.
      • Desktop Users - If you have desktop users you should have an active directory group that contains all your Lucity users
        • This group must also have Read and Change permissions to the share

  1. Within the LucityServer folder create a folder named Lucity.
  2. Paste the Config and Reports folders from step 2 in this folder.
    • Location: The path to the Config folder will now look like this: \\<servername or aliasname>\ LucityServer\Lucity\Config
    • Security: 
      • Administrators - This folder should have an Active Directory Group or a set of Lucity Administrators that has Modify, Read & Execute, List folder contents, Read and Write permissions.
      • Services User - This folder's permissions should include the user that runs your services.
        • If following our suggestions it should the the <domain>\Lucitysvc user.
        • The user you use must have Modify, Read & Execute, List folder contents, Read and Write permissions to the folder.
      • Desktop Users - If you have desktop users you should have a windows group that contains all your Lucity users
        • This group must also have Modify, Read & Execute, List folder contents, Read and Write permissions to the folder.

  1. Within the LucityServer folder create a License folder.
    • Security: Admin and/or Lucity administrator should have Modify, Read & Execute, List folder contents, Read and Write permissions.
    • Only used when performing Lucity Server and Lucity Desktop installs and when running client maintenance.
  1. Place a copy of your LicenseCodes.xml in the License folder.
  2. Within the LucityServer folder create a LucityInstall folder.
    • Security: Admin and/or Lucity administrator should have Modify, Read & Execute, List folder contents, Read and Write permissions.
  1. Place a copy of the Lucity Install media within this folder.
  2. Within the LucityInstall folder run the Setup.exe.
  3. If you are not upgrading during this migration
    • Run the Server/Database install for your current version.
      • When prompted for the Config folder point it to the Config folder on the new server.
      • During the Client Maintenance portion of the install point to the new SQL Instance (if you migrated your database too)
    • Run the Lucity DSN Utility on each machine with Lucity Desktop installed and point to the new config folder. (this tool is found in the desktop install's bin folder and will repoint Lucity Desktop to the Lucity Server and SQL databases.).  It can be run silently as part of a script, so they can push the change out through active directory.
      • Note: You probably should run it on one machine and then check to make sure you can log into Lucity
    • Uninstall and reinstall any of the following that you have: Lucity Services, Lucity Web, Web Citizen, REST API's.  During these installations be sure to point to the correct SQL Server Instance and database.
    • Note: If you are upgrading at the same time just install the new versions.
  1. If you are upgrading at the same time
    • Run the Server/Database install for the version you are upgrading to.
      • When prompted for the Config folder point it to the Config folder on the new server.
      • During the Client Maintenance portion of the install point to the new SQL Instance (if you migrated your database too)
    • Install the upgraded Desktop Install on each machine making sure to point to the new Config folder location
    • Upgrade all of the various web installs making sure to point to the correct SQL Server Instance and Database.  During these installations be sure to point to the correct SQL Server Instance and database.
  1. The process is complete.

 

Have more questions? Submit a request

Comments