There are some things that need to be done before launching the Cloud On-Premise installer. Here is a summary of installation steps, and recommendations to make the process go smoother. Be aware of and plan for one or more PC/server reboots during the installation process.
If possible, install on a PC that is dedicated to the On-Premise product. This will avoid port conflicts between the OP components and other products, and ensure all resources can be utilized by OP, and OP isn't taking resources away from some other product.
If using Windows 10, only the Pro or Enterprise editions should be used; the Home/Standard edition of Windows 10 does not contain necessary components. Even if the OP product installs with no errors on Windows 10 Home/Standard, the product will not work correctly and Wasp will not support the OP product in that environment.
If using Windows Server, do not install on a Domain Controller. SQL Server, the Rabbit component, and IIS will expand to consume resources that will negatively impact the DC's performance.
We strongly recommend disabling or uninstalling virus or protection software that locks files while scanning. We have seen instances where services would not start, and various other installation failures due to overzealous protection software. (McAfee branded products were the problem more than once.)
1. Perform the installation logged in as a local administrator account. Do not use a Domain Admin account. If necessary, create a local user, add that user to the local Administrators group (not the Users group), then log on as this new local admin. This will ensure that the software is installed in a manner that does not depend on a domain user account.
2. If you will need to change the PC/server name to something else, perform the name change before starting the installation process. Consult your IT department for guidance if necessary.
3. Rather than installing on a temporary server, then moving the database to the final server, perform the installation on the Cloud OP's destination server.
Points 2 and 3 will avoid tedious and complicated reconfiguration steps.
4. Configure IIS as described in the article "Cloud On-Premise installation: IIS Settings Prerequisites" linked below in Related Pages.
5. Configure Powershell as described in the article "Cloud On-Premise installation: PowerShell permission configuration" linked below in Related Pages.
6. . If you downloaded and extracted the On-Premise installer folder in the Downloads folder, move it somewhere else on the local drive. e.g. the Desktop, root of C: drive, etc. (This folder should be on a local drive (not a network location), and not in the Downloads folder.)
7. While logged into the PC/server as a local administrator, right-click setup.exe, Run as Administrator. See Notes below. If you receive an installation error, reboot the PC/server, then do this step again. If you get repeated errors, take screenshots and notes on the steps you took, and contact Wasp Tech Support.
8. After successful installation, restore your initial Powershell setting (as described in the Powershell article).
9. Configure IIS performance settings as described in the article "Cloud On-Premise: IIS Settings to improve performance" linked below in Related Pages.
10. (optional) Set user-defined sa password in SQL Studio Management Studio.
a. If a PowerShell window appears with a Security warning, asking if you want to run certain files with .ps1 extension, type R, Enter to allow that. You may need to do this multiple times before the automated process continues.
b. The setup.exe installer is designed to recognize what components have already been installed, so it should be able to pick up where it left off, if the installation is interrupted or the PC is rebooted.
c. When browsing the site, you may get a an Internet Explorer security notification about https://kendo.cdn.telerik.com. This is the website for a third-party component used by the Cloud OP system and should be safe to add to Trusted Sites.