Last updated 23 August 2022
Introduction
EasyFMD can be installed on a standalone machine to which no one else will have access, or it can be installed on a network server and accessed from multiple client machines.
You CANNOT install two separate copies of EasyFMD on two separate machines pointing to two separate data files.
This is prohibited by the terms of the Software License Agreement
This guide will explain a peer-to-peer type installation where your EasyFMD data is already stored on one 'main' machine and you now want to access this data from one or more other client machines running EasyFMD.
If you require a different type of installation then please select a different guide from our Downloads Page
Normally to share your EasyFMD data across multiple client machines, you would install the data file on a dedicated file server.
However not all companies have a dedicated file server.
In such scenarios you can designate one machine as your 'main' machine and this in effect will act as your server.
For the purpose of this document the 'main' machine is the machine that you currently have EasyFMD installed on, in standalone mode.
Important : As long as this 'main' machine is switched on, the other client machines will be able to access the 'shared' EasyFMD data.
If this machine is NOT switched on, then the other client machines will get a connection error when they try to log on.
If you are unsure which type of installation is best for your organisation, then please contact our Customer Helpline number above and we can advise accordingly.
Steps Involved
In order to successfully install EasyFMD on a new client machine, there are two essential steps that need to be carried out in sequence, as follows :-
1) Install EasyFMD on the new client machine.
2) Check that you can see your existing data on the 'main' machine.
You CANNOT simply copy the EasyFMD folder from an existing machine to another. This will NOT work.
You must follow each of these two steps as outlined in detail below.
Requirements
Before you proceed, it is advisable that you download the latest version v24.1.0.0 of the EasyFMD installation program from
our Downloads Page
When downloading, if you are prompted to 'Run' or 'Save' we would advise that you choose 'Save', as you may need to run the installation program a number of times depending on which, if any, of the two prerequisites are already installed on your machine.
Before you can start you will need to know the machine name of the 'main' machine that EasyFMD is currently running on as well as the underlying database being used.
You can find this out by running EasyFMD on your 'main' machine and clicking on Utilities >> Tools >> System Information.
Make a note of both the 'Database' and the 'Server Name' displayed (as shown below).
You should also make a note of the 'Database GUID' displayed. We will use this later to check that the new client machine can see the same data as the 'main' machine.
Prerequisites
Before EasyFMD can be installed on a machine, 'Microsoft .NET Framework 4.8' and 'Crystal Reports Runtime' must also be installed.
If you are running Windows 8 or later, then 'Microsoft .NET Framework 4.8' will be installed already as part of the operating system.
'Crystal Reports Runtime' may or may not be installed already, depending on what other applications you have previously installed on the machine.
The EasyFMD installation program will automatically detect if either of these two prerequisites are not installed and will guide you to the relevant download for each, if required.
Step 1 - Installing EasyFMD On A Client Machine
Very Important : If you already have EasyFMD installed and working on one or more machines, then before doing the install on the new machine,
you will need to ensure that ALL your existing machines have been updated and are already running the latest version v24.1.0.0.
You CANNOT have different versions of EasyFMD on different machines. All machines MUST be running the same version.
If you do install a newer version on the new client machine, then all your existing machines may be prevented from running EasyFMD, until they have been updated to the same version.
1.1) First ensure that you are logged into the local machine as the Administrator (or equivalent).
1.2) Right click on EasyFMD-Install.exe and select 'Run as administrator' (as shown below). If prompted by User Account Control, click 'Yes' to allow the installation program to run with full administrator permissions.
1.3) The 'Welcome' screen should now be displayed. Click on 'Next'.
1.4) Read the terms of the software license agreement. If you agree, click on 'I Agree'.
1.5) When prompted 'What would you like to do ?', ensure that 'Network Install - Client' is selected (as shown below) and click on 'Next'.
1.6) At this stage the installation program will check if the two prerequisites mentioned above are installed.
If a message similar to the one below appears, then this means that the first prerequisite, 'Microsoft .NET Framework 4.8', is not installed on this machine.
If this message is not displayed, proceed directly to step 1.7 below.
By clicking on 'OK' the EasyFMD installation program will begin to download and automatically install the 'Microsoft .NET Framework 4.8' from the Microsoft website.
This may take a few minutes so please be patient. Once 'Microsoft .NET Framework 4.8' is installed, the EasyFMD installation program will automatically proceed to step 1.7.
1.7) If a message similar to the one below appears, then this means that the second prerequisite, the required 'Crystal Reports Runtime' files are not installed on this machine.
If this message is not displayed, proceed directly to step 1.8 below.
By clicking on 'OK' the EasyFMD installation program will begin to download and automatically install the 'Crystal Reports Runtime' installation program.
This may take a few minutes so please be patient. Once the 'Crystal Reports Runtime' files have been installed, the EasyFMD installation program will automatically proceed to step 1.8.
1.8) If the 'Configure Database Server' screen is displayed (as shown below), then this means that the two prerequisites are in fact installed.
The new client machine needs to be configured to use the same underlying database as the existing 'main' machine.
So choose either 'Firebird' or 'Microsoft SQL Server' depending on the database that you noted from the Requirements section at the start of this document.
Next ensure that the correct server name is entered. This should be the same server name that you also noted from the Requirements section at the start of this document.
Note : When entering the server name do NOT use UNC notation (e.g. \\MAINMACHINENAME is incorrect and will not work).
Just enter the machine name of the server without any leading backslashes or spaces (e.g. MAINMACHINENAME).
Once you have selected your database and entered the correct server name, click on 'Next'.
1.9) When prompted to select 'Destination Folder' just click on 'Next' to accept the default folder.
1.10) Click on 'Next' to accept the default 'Program Manager Group' of EasyFMD.
1.11) When prompted with 'Start Installation', click on 'Next'.
1.12) When 'Installation Complete' is displayed, click on 'Finish'.
1.13) You should now be able to run and log in to EasyFMD using your existing logon credentials, by clicking on the EasyFMD icon on your desktop.
1.14) When the EasyFMD 'Main Menu' is displayed, then you have successfully installed EasyFMD on your machine.
1.15) At this point, if you have never used EasyFMD before, then we would suggest that you click on Help >> Getting Started (at the top right) and have a read through this section of the help file.
It will take about 10 to 15 minutes, but will guide you through everything you need to know re setting the system up initially, as well as giving you a complete step by step guide to connecting to your National Hub and verifying your first pack of medicine.
Step 2 - Check Existing Data
To check that you can see your existing data, go into Security >> System Options and check that your 'License Details' and 'National Hub' settings are displayed.
Next go into Maintenance >> Input Devices and you should see the settings for any devices previously configured (e.g. the 'main' machine).
Finally go into Utilities >> Tools >> System Information and check the 'Database GUID' displayed.
If it matches what you noted from the Requirements section at the start of this document then you have successfully configured the new client machine to use the 'shared' data file from the 'main' machine.