Customer support
Network installation
This page describes the network installation of our software. It applies to all products. Multi-user licenses are required.
On this page
Installation error messages
A. Installing to an RM Community Connect 2 (CC2) network or a shared Windows network server
B. Installing to an RM Community Connect 3/4 (CC3/4) network or an MSI-based Windows network server
C. Installing to network client machines by imaging one machine via third-party software such as Norton Ghost or similar
D. Installing in a thin-client Windows Terminal Services, Citrix or Remote Desktop environment
 
Installation error messages
Occasionally during the installation process you may receive an error message. Click here for more information on these messages.
 
A. Installing to an RM Community Connect 2 (CC2) network or a shared Windows network server
The following describes the installation to a shared path on a network server. In this setup the client machines will run the software directly from the network server.
Step through the following in order:
1 Log on to a network client machine as Administrator.
2 Create a shared path on the network server. Typically this will be something like 'P:\Apps' in which all publicly-accessible applications are stored. At this point you should ensure that you have full Read and Write permissions to this folder.
3 Install from the product CD to the shared path on the network server. At the network option page select the 'network server'' option. Do not activate the product at this point.
4 Download and install the latest software updates by visiting the Updates section of our website.
5 Run the software to activate it. Select 'Yes, I want to activate the product...' and enter your unlock code. If you do not have an existing unlock code you can obtain one by clicking here.
6 If you have any extension licenses (laminated cards with a serial number such as xx-XP05-xxxxxxxxxx), these should be installed now by choosing Upgrade from the Help | About box and entering the serial number for each extension license.
7 On each network client machine create a Windows shortcut that points towards the .exe file in the shared network path.
8 For tighter security you should make the shared path Read Only so that only Administrative users can modify the installation.
You can now run the software from a client machine to test the network installation.
B. Installing to an RM Community Connect 3/4 (CC3/4) network or an MSI-based Windows network server
The following describes a network configuration in which the software is held and distributed by the network server, via MSI packages, but is installed and run locally on each client machine.
Step through the following in order:
1 Log on to a network client machine as Administrator.
2 Start building a new MSI package using the MSI creation tool of your choice (such as the RM Application Wizard (for Community Connect networks only), WinInstall LE or Advanced Installer).
3 Install from the product CD to a local hard disk and at the network option page select the 'stand-alone' option. Do not activate the product at this point.
4 Download and install the latest software updates by visiting the Updates section of our website.
5 Run the software to activate it. Select 'Yes, I want to activate the product...' and enter your unlock code. If you do not have an existing unlock code you can obtain one by clicking here.
6 If you have any extension licenses (laminated cards with a serial number such as xx-XP05-xxxxxxxxxx), these should be installed now by choosing Upgrade from the Help | About box and entering the serial number for each extension license.
7 Finish building the MSI package.
8 Distribute the package by allocating it to the required machines.
You can now run the software from a client machine to test the network installation.
C. Installing to network client machines by imaging one machine via third-party software such as Norton Ghost or similar
The following describes a network configuration in which the software is distributed by imaging one machine (the "source machine") on which the software is installed locally.
Step through the following in order:
1 Log on to the source machine as Administrator.
2 Install from the product CD to a local hard disk and at the network option page select the 'stand-alone' option. Do not activate the product at this point.
3 Download and install the latest software updates by visiting the Updates section of our website.
4 Run the software to activate it. Select 'Yes, I want to activate the product...' and enter your unlock code. If you do not have an existing unlock code you can obtain one by clicking here.
5 If you have any extension licenses (laminated cards with a serial number such as xx-XP05-xxxxxxxxxx), these should be installed now by choosing Upgrade from the Help | About box and entering the serial number for each extension license.
6 Distribute the software by imaging the source machine.
You can now run the software from a client machine to test the network installation.
D. Installing in a thin-client Windows Terminal Services, Citrix or Remote Desktop environment
The following describes a network configuration in which the software runs on a server and is accessed by thin-client terminals.
Step through the following in order:
1 Log on to the server machine as Administrator.
2 Install from the product CD to a local hard disk on the server and at the network option page select the 'stand-alone' option. Do not activate the product at this point. (For installing to network drives, use the network configuration described in section A).
3 Download and install the latest software updates by visiting the Updates section of our website.
4 Run the software to activate it. Select 'Yes, I want to activate the product...' and enter your unlock code. If you do not have an existing unlock code you can obtain one by clicking here.
5 If you have any extension licenses (laminated cards with a serial number such as xx-XP05-xxxxxxxxxx), these should be installed now by choosing Upgrade from the Help | About box and entering the serial number for each extension license.
6 Ensure that each user has access to a Windows shortcut that points towards the .exe file.
7 For tighter security you should make the installation path Read Only so that only Administrative users can modify the installation.
You can now run the software from a client machine to test the network installation.
 
 
Copyright © 2015 New Wave Concepts Limited. All rights reserved.
Home | Contact Us | Terms of Use