• Decrease Text SizeIncrease Text Size

Activations (Isolated Installations)

Activations (Isolated Installations)

Delivery

  • Go to Uber > Admin > Activations and create a new Activation. The Name should identify the client/server and the Description should contain all possible notes about the installation including contact information.
  • Click 'Next' and review the activation settings. This tab allows you to deploy the isolated master with limited access, assign module groups, and set up an update notification email. The update notification email will contain a link to download updates so they can be installed manually.
  • Click 'Save' to generate the activation in Uber.
  • Reopen the Activation record and click Generate Files > 'Generate Activator'. This will generate a licensed activator file in the Centralpoint/Uber/Temp directory on the Uber server. A licensed activator is a copy of the installation package for the most recent version containing the license file for the current activation.
  • Deliver the Centralpoint.msi Installer, the licensed Centralpoint.zip Activator, and the corresonding product key Uber > Activations > Activation > Product Key to the client along with the installation instructions via email. Delete the Temp files from Uber and be cautious with this information. The combination of the licensed activator and the corresponding product key can be used by anyone to install Centralpoint without Oxcyon's knowledge.

Installation

  • Create a new 'Centralpoint' directory at the root of the drive on which you wish to install then place the provided Centralpoint.msi installer and Centralpoint.zip activator inside.
  • Double click the Centralpoint.msi installer to begin the installation process. Read and review the instructions provided in the setup wizard. Be sure to select the directory created previously as the Installation Folder. The installer will generate a basic master console (in IIS) and open a browser pointing to that web site to begin the activaton process.
  • Enter the provided Product Key, complete the activation wizard, and click 'Save' to complete the installation/activation. This process will unpack multiple files, generate databases, and web sites in IIS. It may take several minutes to complete. Upon completion you will be redirected to your full featured Master console.
  • Login to the new Master console with the credentials you entered during the activation process. Visit the Site Tree in the left nav to review the sites and consoles created during this process. You may also visit the development site on the URL or IP entered during activation. The same credentials will work in the development site's client console.

Updates

  • Master consoles without Uber access cannot automatically download updates. The Deployment > Updates module will display a link to download available updates on a device with general internet access: https://www.aranon.net/updatelist.aspx?v=8.7.21. If the server admin's email is added to the Uber > Activations > Activation > New Update Notification Email attribute they will also recieve an email when new updates are released including a link to download.
  • Once the server admin has downloaded the update(s) they can visit the Deployment > Updates module for installation instructions. They can either manually place the update package (ZIP) in the Centralpoint/Master/Temp directory on the server or use the File Upload button then click 'Move Uploads to Temp & Reload'.
  • Updates cannot be skipped or installed out of order. If more than one update is added to the Temp folder they will become available in sequential order. Updates will be automatically removed from the Temp folder after 30 days even if they have not been installed.

Activation Changes & Deactivation

  • Changes to the attributes on the Details tab and Activations > New Update Notification Email do not require deployment. All other changes require that the client installs an updated license before the changes will take affect.
  • An updated license can be generated using Uber > Activations > Details > Generate Files > 'Generate License'. Make the changes necessary to the Activations tab, click 'Save', then re-open the record and click 'Generate License'. This will generate a new encrypted Centralpoint.lic file in the Centralpoint/Uber/Temp directory on the Uber server. The 'Generate XML' button can be used to generate an unencrypted version of the file for inspection and debugging.
  • The Centralpoint.lic file can be applied to an existing master manually by the client or delivered in an update package. It should be placed at Master/Root/App_Data/Centralpoint.lic and must correspond to the Admin > Settings > Product Key (also in the web.config) in the master and all web sites.
  • Deploying a deactivated license file will disable the sites and consoles upon installation, but rolling the site back to a backup made before the deactivation will reactivate the site. It would make more sense to schedule the deactivation so a rollback would cause data loss and wouldn't be associated with the installation of the update or license file.

Private Labeling

  • Master consoles without Uber access utilize the default private labeling values located in Master/Root/Uploads/PrivateLabeling/Master/PrivateLabeling.xml. This file and the resources located in this directory can be modified manually to private label the isolated master console.
  • The customized Master/Root/PrivateLabeling/Master directory can be delievered to the client after activation and used to overwrite their local copy, or it can be embedded in the Centralpoint.zip Activator before it is delivered to the client.
  • Web site private labeling can be applied in the isolated master console in the same manner as it is in masters with Uber access.

Articles & Help Files

  • Uber articles have been removed from console home pages using the Master & Web Site Private Labeling > General > RSS Feeds attributes when Uber access is not available. Accessible RSS feeds can be added to the private labels manually if desired.
  • Help files will not be accessible on the server without Uber access. The help file window will detect when Uber is not accessible and display the URL of the help file instead of the help file itself. To view the help file the provided URL must be loaded on a device with general internet access.