Windows Installation

Important

Installation requires either of the following versions, based on your environment:

  • .NET Framework 4.8
  • .NET Core 3.1

NCache can be installed via an interactive Windows installer by following these steps:

  • Search for Command Prompt on Windows Start menu. Right-click on the search result Command Prompt, and select Run as Administrator. The reason for this is that NCache must be installed from an admin user.

  • Install NCache: Run msiexec.exe utility from Command Prompt to install NCache in an interactive mode as following. Please note that the .msi file may have a different name for .NET Framework installation.

msiexec.exe /I "C:\NCacheSetupPath\ncache.ent.netcore.x64.msi"
  • The following Welcome to the NCache Setup Wizard screen appears:

NCache Windows Installation Welcome screen

  • Click Next.

  • The next screen asks you to accept the license agreement.

NCache Windows Installation License Agreement

  • By clicking I accept the terms in the License Agreement, you are making a legal commitment to abide by the Alachisoft Software Agreement for NCache. You cannot proceed without accepting the license agreement.

  • Click Next.

  • The Select NCache Installation Type screen appears.

NCache Windows Installation Type

  • Select the installation type that you want (Cache Server for now) and click Next.

    • Cache Server: installs the full server product along with the local client.

    • Remote Client: installs remote client libraries including ASP.NET session modules. It also installs an OutProc local cache and client cache.

    • Developer/QA: installs standalone local cache along with restricted access to remote caches. Note the following limitations on Developer/QA Installation Type while connecting to remote caches:

      • Throttling of 100 requests/sec for each client: All such clients that are licensed under Developer/QA license will not be able to make more than 100 requests/sec to the remote cache.

      • Limited number of requests (200,000) that a client can send to remote cache: In a lifetime of client application in case it is licensed under Developer/QA license, the client will stop making requests to remote cache after it has sent 200,000 requests to remote cache. Once the client has made 200,000 requests, a licensing exception will be thrown saying "Clients running under DEV license cannot send more than 200,000 requests to remote cache."

Note

Developer/QA licensed clients can make requests to local caches without any limitation.

  • Click Next.

  • Installation Key screen appears, which asks for the installation key. (For Cache Server Only)

NCache Windows Installation Key

  • This is the key which you have received from Alachisoft Support when you registered to download NCache Enterprise Edition.

  • If you do not have the installation key, then click Get Installation Key. User Registration from the Alachisoft website is displayed. Enter all the required information and click Register or Login and an installation key is emailed to you. Enter that installation key in the above box and click Next.

  • User Information screen appears, which asks for your information. Enter all required information and then click Next.

NCache Windows Installation User Info

Note

Make sure that the email address provided is the one used during registration with Alachisoft.

  • The Select Installation Folder screen confirms the location where NCache should be installed. Keep the default location or change it if required. Click Next.

NCache Windows Installation Location

  • The Configure IP Binding and Firewall Ports screen ensures the following prerequisites:

    • NIC binding in case of multiple server IP addresses.
    • Configure NCache specific ports in case of firewall

  • From the dropdown menu, select the IP address to which you want to bind NCache services.

  • By default, the firewall will be configured for all ports used by NCache. Disable the checkbox in case you don't want to configure NCache ports with the firewall.

NCache Windows Installation Setup Environment Prerequisites

  • Click Next.
Note

Set Account to Run NCache Services dialog box is only for ASP.NET Core installation.

  • The next screen asks for user credentials with administrative privileges that are required to monitor PerfMon counters in case of ASP.NET Core installation. Enter the account name and password or use a local system account. Click on Next.

NCache Windows Installation Admin Credentials

Important

For .NET Core installation, if you choose to provide account other than the local account, you have to allow this user to login to the NCache service. See troubleshooting for more details.

  • By default, NCache service will create and start a demo cache named demoCache of topology Partitioned-Replica at the end of setup installation. You can disable this options from this screen by unchecking the Start demo cache at the end of installation. option. Click on Install when done.

NCache Windows Installation Final

  • After the installation is completed successfully, the following screen is displayed. On this screen, there is an option to Launch Web Manager on Finish which automatically launches the NCache Web Manager on your localhost after successful setup installation. You can uncheck this option if you do not wish to launch the NCache Web Manager. Click Finish.

NCache Windows Installation Success

  • If you have used an expired installation key, you will be prompted with this screen instead of the exit installation screen:

Installation Key has Expired

  • If you have a license key or extension key, you don't need to worry about this message. Just use the Register-NCache PowerShell cmdlet to activate your license or extend your evaluation period. Otherwise, contact Alachisoft Sales to purchase NCache license or extend evaluation.

  • You can refer to Getting Started to set up NCache environment.

Troubleshooting

In case of NCache .NET Core installation, if you choose to use a custom user instead of local for the required administrative rights, you need to logon that service as custom user. Follow these steps for a workaround:

  • On Windows, search for Local Security Policy.

  • Go to Local Policies -> User Rights Assignment.

  • Double click on Log on as a service. This will open Local Security Settings where you will find all users who have access to the services.

  • Click on the Add User or Group... button and add the user here.

  • Click on OK and Apply to apply these changes.

See Also

Evaluation Period Management
License Management
Command Line Installation
Network Installation with PowerShell