If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

CM Tool Beta

This is the Beta version of the Aptify Configuration Migration (CM) Tool. If you have any questions or problems using the tool please contact Aptify Technical Support. Your feedback is appreciated!

This topic describes how to install the Aptify Configuration Migration (CM) Tool on a server (source or destination) so users with trusted accounts in Aptify can access the system using a supported web browser.

Note that the Aptify CM Tool must be installed on both the source and destination servers. The order in which you install the tool does not matter.

 

Perform the following tasks before installing the Aptify CM Tool on a source or destination server:

  • Verify the Aptify Desktop client is installed with an active Aptify Object Repository 
  • Verify that the user installing the tool has sufficient rights to the Aptify database and SQL Server.
  • Verify the user installing the tool has system administrator privileges to both the Aptify database and SQL Server. 
  • Verify that the CM Tool setup files are NOT set to read-only
  • Verify that the Aptify installation directory where the CM Tool is to be installed is NOT read-only

Perform the following steps to install the CM Tool.

Test and Backup Recommendations

Aptify recommends that you have a current database backup available before installing this tool. In addition, Aptify recommends installing and testing the CM Tool in a test environment first.

 

  1. Download the Aptify CM Tool installation ZIP file to a folder to the server you want to install the tool (source or destination) and unzip its contents. 
  2. Browse to the location of the installation files, double-click the Setup application file.
    • You can also right-click the Setup application file and select the Run as Administrator option. On certain Windows servers, the Run as Administrator option bypasses the server's User Access Control (UAC) for the duration of the installation.
       
  3. When prompted, enter login information for the database server, specifying an installation account with system administrator privileges to both the Aptify database and SQL Server. 

    Selecting the System Administrator option when creating a user in the Aptify database (through the Aptify User Administration wizard) sets the user to a dbowner in SQL Server. It does not add the user to the sysadmin role. You will need to manually add the user to the sysadmin role in SQL Server through SQL Management Studio. If in doubt, check the user's permissions in the Security > Logins area of SQL Management Studio before proceeding with the installation.

  4.  Click OK to continue.
  5. Review the set of requirements to install. If your environment does not meet one or more of the specified requirements, click Cancel to abort the installation. Otherwise, click Next to continue.
  6. In the Aptify Directory field, enter the directory path where your Aptify Desktop client is installed.  
    • Aptify is typically installed under C:\Program Files\Aptify 5.0 or C:\Program Files\Aptify 5.5.
       
  7. In the Shortcut Name field, enter a name for the tool's shortcut. This name is used to create a Windows Desktop shortcut for this application. 
    • The name should be unique, if the name already exists, the setup program will not be able to create the Windows Desktop shortcut.
       
  8. Click Next.
  9. Click Finish to start the installation. 
    • Installation will take several minutes to complete.
       
  10. Click OK when prompted that Aptify has been successfully installed to close the installer.
    • If a problem occurs during the installation, the Aptify Installer will notify you that an error occurred. If the install is not successful, contact Aptify Technical Support for assistance.

  11. Repeat the above steps for the other server (source or destination).
  • No labels