Page Comparison

Aeon Client (v.5.2.5) Installation/Upgrade Instructions (with access to Software Center)

1. Click Start Menu

2. Type in Software Center
   
3. Click Software Center
   
4. You will see a list of applications that are available for download
5. Run the Software Center Refresh - Refresh Software Center job (from the list of applications) to ensure you have the most current list of applications
   • It may take a few minutes to update the Software Center
6. Click the software you want to install - Aeon Client V5.2.5.0
   
7. Click the Install button
8. The Software Center will display the progress of the installation
9. Once installation completes, run DBCChooser (see below).
10. Restart the computer.

Aeon Client (v.5.2.5) Installation/Upgrade Instructions (for those without Software Center access)

1. Note - the installation package will automatically uninstall any previous version instances of HUIT-provided Aeon
2. Open File Explorer and navigate to the folder containing the .exe file
   1. If the .exe file is hosted on a network drive, copy it to your C:\ drive first.
3. Right-click on the .exe file and select Run as administrator
4. A window with an orange background will open and display installation status messages until complete. When the installation has finished, the window will close.
5. Once installation completes, run DBCChooser (see below).
6. Install the 3 of 9 font.Right-click the 3 of 9 font file and select "Install for All Users"Restart the computer.

Aeon Client (v5.2.5) Installation/Upgrade Instructions (for those without access to T:\)

1. Follow instructions under "Aeon Client Installation/Upgrade Instructions (for those without Software Center access)"
2. After running DBCChooser, navigate to C:\Program Files (x86)\Aeon\Client\Print\
3. Make a backup of PrintCallslip.docx (e.g. make a copy named PrintCallslip-backup.docx)
4. Copy the provided PrintCallslip.docx into this directory
5. Navigate to Documents\Aeon\Addons
6. Copy the provided addon folders here
7. Restart the computer.

Running DBCChoser

Note that installing Aeon via Software Center or the latest manual installer will include the latest DBCChooser.

1. Open File Explorer and navigate to the C:\Program Files (x86)\Aeon folder
2. Double-click on the DBCChooser.bat file to run the utility. (You may not see the “.bat” part.)
3. When the orange window opens, enter P for Production and hit Enter
4. Enter the appropriate letter for your repository and hit Enter
   
5. The new database will be set and the window will close

Update addons

Note that this step is only necessary if you are updating Aeon; if you are installing it for the first time, this can be skipped.

1. Copy LocalSettings.xml to a separate folder
2. Delete all folders in Documents\Aeon\Addons under the Aeon user's Users folder.
3. Copy over LocalSettings.xml from where you backed it up earlier into Documents\Aeon\Addons.
4. Start Aeon, which will copy the latest addons from the T:\ drive automatically.

Installing Without Access to T:\

1. Follow instructions under "Aeon Client Installation/Upgrade Instructions (for those without Software Center access)"
2. After running DBCChooser, navigate to C:\Program Files (x86)\Aeon\Client\Print\
3. Make a backup of PrintCallslip.docx (e.g. make a copy named PrintCallslip-backup.docx)
4. Copy the provided PrintCallslip.docx into this directory
5. Navigate to Documents\Aeon\Addons
6. Copy the provided addon folders here

Important Note for New Aeon Implementations

If you are installing the HUIT-provided package for the first time after going through training with Atlas (i.e. you are implementing Aeon for the first time), you will need to uninstall any existing Aeon instances before installing the HUIT package.  In addition, you will need to delete the registry key for the sandbox database.  This setting will override those set in DBCChooser and prevent you from connecting to your production database.

1. Open regedit
2. Navigate to HKEY_CURRENT_USER\Software\AtlasSystems\Aeon
3. Delete the LogonSettingsPath entry

You can verify that your database settings are correctly updated by running SQL Alias Manager.  There should be zero entries in the left panel with "user default", and one entry with "machine default".  If there are no entries with "user default" in SQL Alias Manager, then no action is needed.