Some users of Captools/net may wish to install the Captools/net server suite on a server physically located at a third party "remote hosting" service, i.e on the "cloud".  This has the advantage of ensuring that the server is located in a secure location, with adequate backup power, 24/7 supervision, adequate cooling environment, access to high speed broadband, etc.

 

Before you select such a service, you should confirm that they will be able to comply with the following minimums:

 

1.) Due to the computational nature of Captools/net a dedicated (not shared by multiple users) CPU and RAM is required. We recommend servers with latest generation AMD or Intel Dual Core processors.

2.) The operating system should be MS Windows XP Pro or its successor, and should be MS Windows 2003 Server or its successor for Enterprise level installations.  All latest Microsoft windows updates must be installed.

3.) You must have a administrative logon to facilitate installation and other essential functions (e.g. items #5 through #13 below).  This should now be possible via a virtual machine even if you are sharing a physical machine with other users.  If you do not have administrative rights you will not be able to perform some Captools/net server configuration actions, including installing updates, performing Captools/net backups, re-setting the IIS.   Also, as a general rule we require that users calling for support on Captools/net have Windows admin rights.  (Note: This requirement may make it necessary that you lease a dedicated server machine).

4.) At least 1 GB of free disk space is required for installation. This will increase progressively based on database size increases and backup files being created. We recommend at least 3-5 GB of disk space for starters.

5.) The hosting service must allow you to install Microsoft IIS software on the machine.  You may need access to Windows CD or equivalent during this installation. Hence, prefer that IIS be pre-installed by the hosting company.

6.) The port 80 on the machine must be opened in the firewall.

7.) You must be able to configure installed anti-virus software to allow VB Scripts to run on the machine.

8.) You must be able to allow the Captools/net installer to install Microsoft.Net framework 1.1 if not already installed.

9.) Your hosting service must provide you with a "remote administration" software which allows you to securely access the server computer remotely and perform all functions as if you were physically in front of the server console.   Your hosting service must allow you to stop/restart all Captools/net programs and the Microsoft Windows IIS (this means that they must give you your own instance of IIS, not shared with other users).

10.) Your server must allow the Captools/net application to access and modify the Windows Registry.

11.) Your server must allow the Captools/net Installer to install MSDE (Microsoft SQL Server).  For larger installation (large amount of data) the full version of MS-SQL Server should be licensed and installed.

12.) Your server must allow the Captools/net installer to install MS-Windows "Service" type applications onto the machine. Post-installation, the server must allow those Windows Services to run even without a user logging in.

13.) For Windows Server 2003 : Must configure Windows DEP to allow Captools/net executables. Windows default setting is to allow unless it is changed.

14.) Your hosting service must provide you with a public IP address that you can connect to.  You may also have a domain name registered for ease of use (allows connecting to a "dot com" address instead of ip number e.g. "123.45.678").

15) To allow you to enable Captools/net use of secure "HTTPS" communication protocol, your server will need an "SSL Certificate". If this is not included with your service you will need to buy and install one of these yourself from one of a number of vendors (cost ranges from about $200 on up, suggest a web search for vendor).  A "self-signed" certificate may also be possibly used to avoid this cost.

16) You should be sure that there is a secure means for you to periodically obtain data backups from your remote installation in a secure fashion, e.g. through FTPS upload or a VPN.   We believe that this should be done periodically, e.g. quarterly, in order guard against inability to get your data due to either physical reasons (e.g. fire, flood, failed equipment) or legal reasons (e.g. dispute with vendor, vendor in bankruptcy, etc).  You should be sure to follow up and get these backup and store them securely once you've begun remote operations.