Step 1: Create a Windows virtual machine

Log on to your Amazon console.
From the console dashboard, choose Launch a Virtual Machine.
The “Choose an Amazon Machine Image (AMI)” page will display a list of basic configurations, called Amazon Machine Images (AMIs), that serve as templates for your instance. Select the AMI for Windows Server 2016 Base or later.
- If you are planning to connect more than 500 clients to this server, we recommend using SQL Server as your database.
On the Choose an Instance Type page, you can select the hardware configuration of your instance.
- If you are planning to connect more than 500 clients to this server, we recommend a VM with 4 CPUs and 16 GB of memory.
Choose Review and Launch to let the wizard complete the other configuration settings for you.
On the Review Instance Launch page, choose Launch.
When prompted for a key pair, select “Create a new key pair“

Warning: Don’t select Proceed without a key pair. If you launch your instance without a key pair, then you can’t connect to it.
When you are ready, select the acknowledgment check box, and then choose Launch Instances.
A confirmation page lets you know that your instance is launching. Choose View Instances to close the confirmation page and return to the console.
Important: On the Instances screen, you can view the status of the launch. It takes a short time for an instance to launch. After the instance starts, its state will change to “running” and you will see the Public DNS name and IPv4 Public IP for this VM. You will need this info for your client deployment.

Launching your AWS Windows instance using RDP

In the Amazon EC2 console, select the instance, and then choose Connect.
In the Connect To Your Instance dialog box, choose Get Password (it will take a few minutes after the instance is launched before the password is available).
Choose Browse and navigate to the private key file you created when you launched the instance (step #7).
Select the file and choose Open to copy the entire contents of the file into the Contents field.
Choose Decrypt Password. The console displays the default administrator password for the instance in the Connect To Your Instance dialog box, replacing the link to Get Password shown previously with the actual password.
Record the default administrator password, or copy it to the clipboard. You need this password to connect to the instance.
Choose Download Remote Desktop File. Save the .rdp file and run it.

Step 2: Configuring your VM to Accept CurrentWare Client Connections

Log on to your Amazon console.
From the navigation menu, look for Instances.
Click on your VM instance.
On the Description tab on the bottom of the screen, look for security groups and click on launch-wizard.

In the Security Group page, select Edit Inbound rules button.
Add the following ports:
- Type: Custom TCP
- Port Range: 8990-8999
- Source: Anywhere
Repeat the same configuration for port 1433-1434.

You’re all set! Your AWS VM instance will now accept traffic from your CurrentWare Clients.

Step 3: Installing the CurrentWare Server

Once you’ve set up your AWS virtual machine and configured it to accept CurrentWare traffic, it’s time to install the CurrentWare Server.

Installing the CurrentWare Server & Console

Step 4: Deploying the CurrentWare Clients

With the CurrentWare Server installed, you are ready to deploy the CurrentWare Client to your computers and have them connect to your CurrentWare Server. There are several ways to deploy the Client.

Note: during your client deployment, make sure you point your clients to the server using the static public IP address or public DNS name of your virtual machine.

Related:

New to CurrentWare? Get Started Today!

“I chose CurrentWare for the solid product that gave more options with a lower price tag, high accuracy, and solid customer support.” -Vincent Pecoreno Network Administrator, Viking Yachts

Getting Started