Option 1: (The Easiest)

Choose the time that is best in the 2 month transition window where you wish to use the New User Interface in your live production environment and just apply it.

Option 2: You are gifted, ambitious, and don't mind installing an additional reporting server so the New User Interface can fully function with both versions being available for a 2 month period of time.

The paths and scope of every install can be different. You have to perceive the differences when following the instructions.

  1. Install the Aeries Reporting Service on any additional server in the same scope and domain as the existing Aeries web server/Aeries reporting server. (The reporting service cannot be doubly installed on the same machine it is already on) Please refer to the Aeries_Planning_and_Installation_Guide.pdf and the server needs to have Message Queuing and a recent .NET framework 4.5.2 or higher
  2. This new reporting server also needs to have the machine account of the web server permissioned to read/write to the filestore. See Permissions_Needed_for_Aeries_Web_Imports.pdf page 6
  3. Apply the AeriesNewUIReportingUpdate.ZIP to your newer second Aeries reporting server. 
  4. Create a copy of your current AppSettings folders.
    • If using a Sandbox Database for the New UI, update your copy of the AeriesNetConnections.Config to point at it instead.
  5. Change the AeriesReportingConfig.Config to have its remote message queue point to your second Aeries Reporting Server.
  6. Create a NewUI web app in IIS with its AppSettings virtual directory pointed at the alternate AppSettings folder you just configured
  7. After testing that it works and prints, publish the New UI URL to the users who you want to check it out and use it.

Examples of the Custom Text used in our hosted environment can be downloaded here...


While the following result is nice, self hosted customers would be undertaking the journey to accomplish this themselves. Naturally the custom content extensions feature can be used for other purposes by self hosted districts in the future.