Omnilert Desktop Alert v2: Installation Guide (Windows)

Supported Windows versions

• Microsoft Windows 7 or later is required

Installation Instructions

There are two methods for installing the Omnilert Desktop Alert v2 client application; manual and automated installation.  

Manual installation is the typical software installation: Click on the installer and install the software onto your PC. The end-user of the application must enter his/her Personal Access Code to link their PC's Omnilert app to a valid Omnilert subscriber account.
Automated installation can pass the PAC to the installer.

Download the latest installer file from the "Installers" tab in the Desktop Alert endpoint section of Omnilert.

Manual installation

To install Omnilert Desktop Alert v2 on a Windows computer, download and run the installer application using the link provided by your institution. Follow the prompts provided by Windows to install the client app. 

Please note: The installer filename may vary based on the latest version of Omnilert Desktop Alert. (You can rename the installer file if needed.)

After installing the Omnilert Desktop Alert v2, the end-user will be prompted to enter their Personal Access Code (PAC). 

They will then be logged in as their personal Omnilert subscriber and have access to the features of the Omnilert App right on their desktop.

Note: We do not recommend installing manually for shared PCs (kiosks, libraries, classrooms, etc.). Rather, we recommend installing via the automated (command-line) method for such machines so that the installation is run as an administrator and implemented for any/all users on that PC. 

Automated Installations

Unattended installation can be as simple as running a command on a PC's command line:

OmnilertInstaller.exe /PAC=PAC_CODE_HERE

Replace the PAC_CODE_HERE above with the Personal Access Code (PAC) for your subscriber.

The installer's filename can vary based on the latest version. (You can rename the file if needed.)

With no additional switches, the application will install without any PAC pre-assigned. The subscriber would then need to log in with their Personal Access Code (PAC) . (Note: There are options to allow you to supply the PAC to the installer outlined in detail below.)

Windows installer command-line switches

If using a software management system (e.g. Microsoft SCCM), you will need to run the MSI installer with switches to customize the application for your environment. You can use several switches to customize the experience and installation on each PC when running the MSI installer for Omnilert Desktop Alert.

• /PAC=PAC_CODE_HERE - Insert a valid Personal Access Code into the application. (Replace "PAC_CODE_HERE" with a valid personal access code from Omnilert.) This removes the need for the user to manually enter a valid Personal Access Code (PAC) on that computer. 
  
  
• /S- Runs the Windows installer without needing any confirmations or clicks by the end user.

Passing the Personal Access Code to the Omnilert installer 

If managing the Omnilert Desktop Alert v2 client app remotely, you may assign PCs to subscribers during the installation process by inserting a valid PAC into the installation command line.

(This removes the need for the user to manually enter a valid Personal Access Code (PAC) on that computer and ensures that the desired PAC is used.)

In such a case, distribute the application with the following command-line argument:

OmnilertInstaller.exe /PAC=PAC_CODE_HERE

Replace the PAC_CODE_HERE above with the Personal Access Code (PAC) for your subscriber.

So, if your subscriber PAC is ABC1234567, then you'd use the switch /PAC=ABC1234567

By default, Omnilert is installed as a "per machine" application; all users of the PC will have access to the Omnilert app under the PAC supplied at installation. 

Shared PACs (Using the same PAC for multiple computers)

This method is most commonly used for shared PCs, such as libraries, classrooms, etc., and uses the same Omnilert subscriber for all users on that PC, regardless of their Windows profiles. 

All PCs using the shared PAC would then be targeted together, as a single unit.

To create a shared PAC:

• Create a new Omnilert subscriber to represent the shared PCs. Go to People > Subscribers and add a new subscriber. This subscriber doesn't need a phone number or email address. (This subscriber is only used for the group of computers.)
  
  
• After creating the subscriber, view their account info to retrieve their PAC.  Copy the PAC for use in your automated installation.

If you need to target groups of "shared PAC" computers independently, create a separate subscriber account (and PAC) for each logical grouping of PCs and install using the desired PAC. 

If using a shared PAC for PCs, you can use the following command to run the installer silently.

OmnilertInstaller.exe /PAC=PAC_CODE_HERE /S

Note that the installer's filename can vary based on the latest version. (You can rename the installer file if needed.)

• /PAC=PAC_CODE_HERE passes the code to the installer. Replace "PAC_CODE_HERE" with the shared Personal Access Code (PAC) from your Omnilert system.
  
  
• /S runs the installer silently, with no prompts from the end-user. 

NOTES AND BEST PRACTICES:

• If using a mass installation system such as Microsoft SCCM, be sure to select the appropriate options to place this application in the "Startup" for Windows. 
• Note that all PCs will appear as the same "user" in reports in Omnilert.
• Always test your script/remote installation processes on a small group of PCs before mass installing on PCs.
• It is strongly recommended that the PC be restarted immediately after installation to ensure the proper registry settings are set to launch this application at startup.

Updating from older installations (For systems installed previous to build 1.3.0)

We have found that taking some steps can ensure proper performance when updating this application with the latest installer.

• Always uninstall the previous version on the PC before running the new installer. 
• It is recommended to delete the desktop device from the "Device List" in Omnilert after uninstalling and before re-installing. 
• The local Windows user's \AppData\Roaming\ directory on the PC device may still contain an "omnilert_desktop_alert" folder after uninstalling.  Windows may orphan this folder and files after uninstalling. This folder can safely be removed.
• Please restart the PC immediately after re-installing the Omnilert Desktop Alert client.
• It is recommended to confirm and delete the Omnilert registry folder inside HKCU/Software/Omnilert and/or HKLM/Software/Omnilert.
  • To open the Windows Registry Editor:
    • Press Win + R to open the Run dialog box.
    • Type "regedit" and press Enter.
    • Navigate to HKCU/Software/Omnilert and HKLM/Software/Omnilert to confirm and delete the folders if they exist.