Revision 6.28
Last updated April 2024

Latest changes: 
- Added server regional setting requirement Previous changes:
- Removed Windows Server 2012 and 2012 R2 As its EOL in October 2023 - FTPS requirements added - Firewall exclusions and Windows features - Modified process under: Preparing a new Minfos Client - Update minimum .NET version to 4.6.2 from Minfos v7.8.1 onwards - Removed ngrok.exe from firewall server exclusions
- Minfos Database migration options and limitations
- Added Note for database migration limitations to same or later OS releases only
- Added section: Hardware vendor pre-packaged service conflicts - Updated the firewall list
- Added hard drive encryption recommendation
- Restrict F: and H:
- Added Wi-Fi recommendation
- Update client user and server user permissions

- Updated Antivirus and Firewall exclusion list
Updated information regarding physical disks/arrays under Hard disk setup for Server station specifications of the Minfos Server station.
- Updated Migration process to include Migration Preparation section.

This document defines the minimum and recommended hardware and software requirements for installing and running a Minfos system in an Australian pharmacy.

If you do not meet the Minfos hardware and software requirements, your Minfos software will not be supported.

Please ensure that you refer to the current version of this document, which is available:

  • On the Minfos Help Centre
  • Directly from Minfos, on request

This document is designed for:

  • Australian pharmacy owners and staff who use Minfos systems.
  • Hardware vendors who install Minfos systems in Australian pharmacies.


Before your Minfos installation

Choosing your hardware vendor

Hardware vendors who install Minfos systems must be experienced with Microsoft networking and should be Microsoft Certified Professionals (MCP).

Our partnered hardware vendors

Partner Name

Primary Service Area

Website

Accelerate Group

National

accgroup.com.au  

Altitude it

Western Australia

www.altitudeit.net.au

Chemist POS Direct

East Coast 

Western Australia

South Australia

www.posdirect.com.au

GZD

Queensland

gzd.com.au

Total Networks

Tasmania

www.totalnetworks.com.au

TP Solutions

South Australia

www.tpsolutions.net.au


Pharmacy responsibilities

Before your Minfos installation, you must ensure you have:

  • An active broadband internet connection. See, “Internet connection” section for details. 
  • A wireless access point, if your pharmacy intends to use wireless scanners with the Minfos software.

Hardware vendor responsibilities

Compliance

Your hardware vendor must ensure all hardware complies with at least the minimum requirements provided in this document.

Any installation or configuration that has to be completed by Minfos will be charged to you at standard rates determined by Minfos.

We do not warrant that Minfos software will run correctly on hardware or software that do not comply with the minimum system requirements specified in this document. Minfos reserves the right to refuse or to charge for software support for issues arising from non-compliant hardware or software.


New installations

If there are any concerns about the compatibility of any of the hardware components used, or questions about the requirements defined in this document, your hardware vendor must check with Minfos prior to the Minfos installation.

All hardware must be installed, tested and operational by the close of business on the day that the Minfos system is to be installed. A hardware technician must be available after the pharmacy’s closing time to connect and implement networking on all workstations, in conjunction with Minfos staff.

Your hardware vendor must test the connectivity between the Minfos Server and workstations to ensure that all potential connectivity issues have been addressed before the Minfos trainer or installer arrives. These issues may include:

  • Firewalls.
  • Antivirus software.
  • Sharing permissions.

A technician from the hardware vendor must be on site for at least the first half-day of trading after installation, to address any configuration faults that might not become apparent until the system is in full use.

It is both your responsibility and the responsibility of your hardware vendor to ensure that the backup device in the system is fully operational and that it has successfully performed a backup on the first day after Minfos is installed, and then on an ongoing, daily basis, see “Backup options” for more information.

Network setup

Before installing cabling in your pharmacy, you should carefully consider where each computer will be positioned in the store.

Network switch

The entire network, including the link from the server to the switch, should be 1 GP. See, “UPS” for power supply information. 

The network switch must be connected to an Uninterruptible Power Supply (UPS). Connecting the switch to a UPS is essential in order to prevent corruption to the database in the event of a power failure.


Network cables and connectors

Your network cables and connectors must comply with the following standards:

  • All cabling must be:
    • Installed, tested, and certified by an AUSTEL-certified installer.
    • A minimum of CAT5E, although CAT6E is recommended.
  • A maximum of 36 cables should be bunched together. Each bunch must not be more than 150mm wide and the cable ties must be loose.
  • No courtesy loop should be used at the patch panel.
  • Leave one metre for faults and corrections.
  • Krone type plugs must be used for all network connections. These plugs must be placed in relative proximity to the workstation (for example, not in the next counter bay over).
  • Appropriate ducting must be used to protect any exposed cabling.
  • Network cabling must be placed a minimum of 300mm away from AC power.
  • Wherever a workstation’s wall plug is placed, allowances are to be made so that any cable connection to this socket will not be disturbed (for example, it should not be placed the front of the counter bay or on the face of the kickboard).


Wi-Fi

Minfos Mobile App requires a Wi-Fi connection to the store server.  Stations also can have Wi-Fi connections to the stores VLAN.

To help keep the network as secure as possible we would recommend 2 Wi-Fi Access Points:

  1. Private VLAN (SSID 1) for all business related assets/devices.
    1. Each device on this Wi-Fi to be registered and approved for access to the stores network.
    2. Full (or appropriate) access to the stores business network.
  2. Public VLAN (SSID 2) for all personal or non-business devices.
    1. Used for non-business usage (e.g. personal staff devices).
    2. Used for internet related access.
    3. Rotate Wi-Fi password periodically.


If staff personal devices are allowed on the stores private network, this opens a security risk of potential threat vectors entering the network.  We recommend the private network to use business-only assets.


Phone lines

All phone lines must be installed, tested, and certified by an AUSTEL-certified installer.


AC power

All AC power sockets and cabling must be installed, tested, and certified by a licensed electrician.

Power outlets supporting the computers, peripherals and network must be placed on a dedicated circuit that is preferably filtered or surge protected. This dedicated computer power system should be connected to its own circuit breaker rated at 16 amps.

A minimum of two free power sockets must be installed in all workstation areas to allow for additional peripherals to be added in future.


Backup options

Minfos Cloud Backup Service is our preferred backup solution for Minfos data. This offsite backup provides reliability, security and faster data recovery in the event of data loss. For non-Minfos files, other offsite backups can be organised through your hardware vendor.

Alternatively, external hard drives and memory sticks are acceptable backup media. Every backup device must have a minimum of 300 GB of space to record at least two weeks’ worth of backups.

Nightly backups must be removed from the pharmacy and stored at a secure, offsite location. If a database has no offsite backup, you are at risk of losing all data.

The following path must be backed up:

  • F:\MINFOS01\DB\BACK\*.*
Volume Shadow Copy Service (VSS) is not compatible with the Minfos Database. If you have VSS enabled, please ensure that all Minfos folders are excluded from the service.


Internet connection

A broadband internet connection must be installed and operational before the Minfos installation date.

You must have a minimum of ADSL2+ with a minimum of 50GB upload/download capacity. However, the internet connection speed you require will depend on the types of services you intend to use (for example, loyalty, Minfos Cloud Backup).

Please speak with your hardware vendor to determine a suitable internet connection.


Antivirus and Firewall

To help protect your system, we recommend antivirus to be installed on the server and on each workstation computer. It must be configured to automatically download updates and new virus definitions.

Antivirus exclusions

Minfos requires that the following data folders be excluded from antivirus checking. These folders contain only Minfos data files. Excluding them can help to improve performance and reliability.

Server exclusions

  • F:\MINFOS01\DB
  • H:\MINFOS01\DB
  • H:\MINFOS01\DATA
  • H:\MINFOS01\MNET
  • H:\MINFOS01\NEWSOFT
  • H:\MINFOS01\RCVE

Client machine exclusions

  • C:\MINFOS01\COMS
  • C:\MINFOS01\RCVE


Firewall and Antivirus exclusions

Firewall and antivirus should be setup to help prevent unwanted intrusions into your system.  Minfos requires that the following firewall and antivirus exclusions are in place. These exclusions are required to allow Minfos to communicate with services. If the Back Office is configured on the server, both the exclusions grouped below will apply to the server.

Minfos will automatically update Minfos related Windows firewall rules.


Server exclusions

  • Application/Process: H:\Minfos01\WCSDB5.exe
    • Inbound
      • Local Port: 9000 TCP and UDP (Local Network)
      • Local Port: 4434, 4436, 4438 (Local Network)
    • Outbound
      • Any (Local Network)
  • FTPS Communications
    • Inbound
      • Local Ports: 4439 (Local Network)
      • Local Ports 38000 - 39000 (Local Network)
  • Service/Process:  Minfos Remote API Service %localappdata%\MinfosTunnelClient\tunnel-client.exe
  • Service/Process:  pktriot.exe
    • NEW from Feb 2023
    • Outbound Destinations
  • Service/Process:  ngrok.exe (decomissioned)
    • This is no longer required and can be removed from firewall settings
    • Outbound Destinations
  • All Applications/Processes
    • Outbound Destinations
      • *.minfos.com.au
      • amazonaws.com
  • Application/Process: C:\Minfos01\InstrumentationService.exe
    • Inbound
      • Local Ports:   80, 8080 (Local Network)
    • Outbound Destinations
      • Remote Port: 4434 (Local Network)
      • *.minfos.com.au

Back office machine exclusions

  • Application/Process: eRx service (C:\Minfos01\eRx\Erx.ScriptExchangeAdapter.StandardAdapter.exe)
    • Outbound Destinations
      • Remote Port: 3440
      • *.erx.com.au
  • Application/Process: Medisecure service (C:\Program Files (x86)\Medisecure\MedisecureAdapter)
    • Outbound Destinations
      • Remote Port: 2056
      • *.medisecure.com.au
  • Application/Process: Minfos Backoffice Service Manager (C:\Minfos01\MinwEpService.exe)
    • Outbound Destinations (Applicable only if store is configured for loyalty)
      • *.<loyaltyservicedomain> on port 443

Allowed applications

Minfos applications must be allowed to access the network. After updating Minfos, you will need to allow network access to any updated Minfos applications.

Minfos users on the backoffice machine, must be given local administrator rights to the station to ensure that Minfos utilities (for example: eRx, MediSecure, PBS Online) can be installed and will work correctly.

IP schema

Minfos supports TCP/IPv4.

The following diagram shows an overview Minfos pharmacy setup.

 


Minfos Server station and component IP addresses

  • 192.168.1.1 – Minfos Server station
  • 192.168.1.1 – DNS
  • 192.168.1.1 – DHCP


If you are not using a Windows Server please ensure DNS and DHCP is enabled on your ADSL/Router. See “Windows serverless workstation setup”.


Router/switch IP address

  • 192.168.1.254


Multi-store FTP set up

Hardware vendors can directly manage FTP settings for Multi-store. For further information and instructions please refer to Manage FTP settings for Multi-store.


Minfos Server station

Your Minfos Server station should be located in a safe place in your store, with an uninterruptable power supply. This area must be well-ventilated to prevent the server from overheating, and must be kept secure to prevent unauthorised physical access to your pharmacy’s data.

Server station specifications

This table provides the minimum, preferred and optimum specifications for your Minfos Server station.


Optimum

Preferred

Minimum

Suggested capacity

Over 8 clients, or 300 scripts or equivalent retail sales per day

Up to 8 clients or 300 scripts or equivalent retail sales per day

Up to 3 clients or 50 scripts or equivalent retail sales per day

Suggested workload

Built for robustness. Same as Preferred, including heavy integration usage. E.g. Robotic dispense.

Minfos with additional third applications to aid in daily business function. 

Minfos only running on system.

Processor

Intel® Xeon® E5-2609v3

Intel® CoreTM I7 6th Gen (x64)

Intel® CoreTM I5

RAM

32 GB

16 GB

8 GB

Internal mass Storage

4 × 300 GB SAS 

RAID1

2 × 256 GB SSD *

120 GB or higher

Operating system

Windows Server 2022 64 Std/Essentials

Windows 11 Pro 64-bit

Windows 10 Pro 64-bit

Network adaptor

1Gb Ethernet **

1Gb Ethernet **

1 Gb Ethernet

Storage controller

Smart Array B140i RAID Controller or equivalent

Mirrored RAID Controller

 

UPS

1KVa+ with monitoring software

700VA+ with monitoring software

 

*See “Hard disk setup”.

**Remote card recommended for hardware vendor remote support


If additional applications are intended to run on the server, additional capacity is required. Please be aware that you may experience performance issues if additional applications are installed on a server that cannot handle the load.


You can run the Minfos Database as either a:

  • Dedicated server
  • Shared server

Dedicated server

The dedicated server setup is where the Minfos Database is running on its own dedicated server, with all other Minfos and third-party applications running on client machines.

The following are some of the advantages and disadvantages of running a Windows Server operating system on server hardware as a dedicated server.

Advantages

  • Secure location of the server machine, preventing theft and damage.
  • Additional security.
  • Better management of network resources.
  • Engineered to manage, store, send and process data for 24 hours a day.
  • Greater stability and performance. 
  • File server capability that is easier to upgrade and expand.
  • Repository for other databases for centralized backup.


Disadvantages

  • High price.

Shared Server

A shared server permits the database and backoffice functions to be running on the same machine. For small stores, Dispense and Till may run on the same machine. Machine resourcing will need to cater for the additional applications running on the same machine.

The following are some of the advantages and disadvantages of running a Windows operating system on desktop hardware as a shared server.

Advantages

  • Small pharmacies with minimal space can utilise a single machine for multiple functions.
  • Consolidate backoffice functions and server to run on the backoffice machine.
  • Affordable.

Disadvantages

  • Prone to user error, for example, accidentally shutting the database down while trading.
  • Microsoft connection and user licence limitations.
  • Greater risk of virus infection.
  • Poor network management.
  • Performance and stability issues.

Hardware Vendor pre-packaged Service Conflicts

Some server hardware come packaged with vendor specific services as part of the operating system.  Minfos has identified conflicts between some of these vendor services and the the operating systems services.   For Minfos to operate without issues, some vendor specific services will require disabling.


HP: Please disable the following services (if installed) as it conflicts with MSDTC:

  • HP App Helper HSA Service

  • HP Network HSA Service

  • HP System Info HSA Service


UPS

The server is to be connected to an Uninterruptible Power Supply (UPS). This can be the same UPS as the network switch.

Note: 

  • Best Practice to have UPS monitoring software installed on the Minfos Server
  • If the UPS application is not running as a service please ensure it is running in elevated mode (right-click > Run as Administrator).

The UPS monitoring software must monitor the level of power remaining in the server’s UPS in order for the server to be able to shut down the database, close any open files and shut down if the power runs out.

It is the responsibility of the hardware vendor to test and certify that the UPS monitoring software is operational. In the event of a power outage, the pharmacy must close all Minfos applications that connect to the Minfos Database.

Region Settings

On the server, we require the following:

Region Settings > Language for non-Unicode programs

  • Current system locale:  English (Australia)
  • Beta: Use Unicode UTF-8 for worldwide language support: Unchecked 

Hard disk setup

On the server, we strongly recommend a minimum of a RAID 1 setup must be used across all drives.  Please speak to your professional hardware vendor for more information. Minfos requires logical drive letters be assigned to local partitions. 


Shared or networked drive mappings are not supported.

The physical drives should be set up into three partitions, as shown in the following table.

  • Best Practice to avoid partitioning a single physical disk into three separate drives without a RAID setup.
  • Disable disk caching on serverless setup, see ”Windows serverless workstation setup”.
  • Disk Encryption to be enabled.
  • Restrict the H: and F: to be only shared on the private VLAN or PHARMACY domain users, not 'Everybody' on the network.
  • Recommend H: & C: drives to be separate physical disks/RAID array channels (See note below drive table)

 

 

Optimum

(4 HDD)

Preferred

(2 HDD)

Minimum

Logical drive letter

Use

RAID1 

(Array number)

Mirrored RAID split into 2 partitions

Single Disk (*)

C

Server operating system

1

1

1

F

Minfos backups

1

1

1

H

Minfos program files and database

2

2

1

(*) Note: MSMQ and EDB (Microsoft ESENT DBs) compete at times for disk I/O and can trigger performance degradation due to higher than normal disk queue length/disk response times when on same physical disk/RAID array channel.

Server operating system

The following server operating systems are supported, all on 64-bit architecture:

  • Windows 11 Pro
  • Windows 10 Pro 
  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022

Note: Windows Server 2016 Essentials supports up to 25 workstations.


You must have the appropriate number of Windows user licenses for the workstations in your pharmacy. Ensure that:

  • Windows updates are kept up-to-date.
  • The server is kept up-to-date with service packs and patches.


This table outlines the standard configurations on the Minfos Server.

Server name

Name the server minfos-fs#
(where ‘#’ is the server number; for example, minfos-fs1)

Internal TCP /IP

Must be static * (192.168.1.1)

Active directory name

For example, chemist

Admin password

Record this on site

If you are not using a Windows Server please ensure DNS and DHCP is enabled on your ADSL/Router. See “Windows serverless workstation setup”. It may be necessary to allocate fixed IPs via MAC addresses using DHCP instead, depending on the level of functionality provided by the ADSL/Router.

The servers administrator credentials may be required for Minfos support.  This can be entered into the Minfos Screen Connect tool which stores these credentials in an encrypted format so that Screen Connect can use the credentials if they are required.  We do not require a physical copy of the credentials.


Windows Server user account

Log into the Windows Server as the default administrator or as a user with administrator-level access. This user account will be used to install and run the Minfos Database (wcsdb5.exe is required to run with elevated permissions).


Services

Ensure the Microsoft Message Queuing (MSMQ) service is installed and enabled on the server.

Note: We recommend installing only the MSMQ service. Do not install other services under MSMQ services.

Windows Server setup

This section provides the requirements for setting up the Windows Server.


Windows Features to be enabled

Listed is a number of Windows features that Minfos installs during setup.

  • IIS-WebServerRole
  • IIS-FTPServer
  • IIS-FTPSvc
  • IIS-FTPExtensibility

Login script

On the Windows Server browse to the Net logon directory and create the following batch file to run on start-up. The Net logon directory can be found in C:\Windows\SYSVOL\sysvol\pharmacy.local\scripts.

You must apply the login script for all users.


Please ensure that the following information is included in the login script.

net use f: \\SERVER-NAME\F
net use h: \\SERVER-NAME\H
net time \\SERVER-NAME\ /set /yes

The first two lines are used to allocate drive names that must be shared as and H drive, and must not be given aliases, for example, “Minfos Backup”.

The last line is used to synchronise the time on all workstations with the server.

Active Directory organisation unit

On the Windows Server operating system, in the Active Directory tree schema, create an organisation unit named “pharmacy.local”.

DNS

  • DNS must be set up on the Minfos Server station with a forward lookup to the ISP.
  • A static entry must be added to the DNS server reflecting the IP address of the server; 
    • for example,  minfos-fs1 192.168.1.1


DHCP

  • The DNS option must be added with the address of the DNS server; for example, 192.168.1.1
  • The router option must be added with the address of the router; for example, 192.168.1.254


Domain

All workstation computers must be added to the Active Directory domain.


Users

On the Active Directory domain controller, create an organisation unit named PHARMACY and assign users to the OU.


Minfos Client Machine Permissions

Standard user may run the Minfos Client.  Folder permissions required for the Standard user:


PathPermission
C:\MINFOS01

Read, Write, Modify

H:\MINFOS01\*

Read, Write, Modify

H:\PRFTILES\*

Read, Write, Modify


Minfos Client will require Elevated permission during a software update.
Multiple UAC prompts will appear during a software update on the Minfos Client if running as Standard user.



Minfos Server Database Permissions

  • The Database is required to "Run as Administrator".   With elevated permissions (e.g. Default System Administrator)


Permissions for files and directories on the server

Create the following paths:

  • F:\MINFOS01\DB\BACK
  • H:\PRTFILES
  • H:\MINFOS01

After these paths have been created, allocate the following access to the PHARMACY organisational unit:

Path

Permissions

F:\MINFOS01

Read, Write, Modify

H:\ (root directory)

Read, Write, Modify


Windows serverless workstation setup

If you are running a non–Windows–server operating system, the following changes are required.

Before you start

The following changes are required in order to improve performance on the serverless environment, and enhance the database recovery in the event of a failure:


Disable disk write caching on all hard disk drives

Follow this procedure to ensure all data is written to disk in case of power outage and to prevent data loss

1. My computer > System Properties menu > Device Manager > Expand Disk drives.

2. On each disk drive, right-click > Properties > Policies tab > Un-check Enable write caching on the device.

Enable Background Services

Follow this procedure to ensure Minfos Database requests have equal priority to foreground applications.

My computer > System Properties menu > Advanced system settings > Performance Settings > Advanced tab> Click Background Services option button.

Windows registry changes on serverless operating system

Follow this procedure to ensure that all workstations can connect to the Windows serverless workstation at all times.

1. On the serverless workstation, open regedit.exe.

2. Navigate to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters.

3. Set “IsDomainMaster” to True.

Windows registry changes on client machines

Follow this procedure to ensure that only the Windows serverless workstation running the database is the Domain Master.

1. On each client workstation, open regedit.exe.

2. Navigate to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters.

3. Set “IsDomainMaster” to False (default).

Windows Firewall on client and server machines

Should be set to either Home or work (private) networks.

NetBIOS changes required on all computers in the serverless LAN

NetBIOS names identify computers on the network. NetBIOS broadcasts locate computers and shared disks and folders on the network and allow them to appear in My Network Places and Network Neighborhood.

A Windows Server is designed to manage the network and computer identification.  On a serverless LAN, the following NetBios and Node Type changes are required to allow networked computers to properly identify each other.

Enable NetBIOS over TCP/IP

1. Start > Control Panel > Network and Internet > Network and Sharing Centre.

2. Click Local Area Connection, or the name of the local network connection.

3. Properties > Internet Protocol Version 4 (TCP/IPv4).
Note: If TCP/IPv6 is installed it should differentiate the two versions of TCP/IP

4. Properties > Advanced… > WINS.

5. NetBIOS Setting group box > Enable NetBIOS over TCP/IP.

6. Click OK, to save these settings.

Set Node Type to Mixed

1. On each workstation, including the serverless workstation, open regedit.exe

2. Navigate to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NetBT\Parameters

3. Right-click > New > DWORD (32bit) 

4. Name: NodeType

5. Data: 00000004


Migrating to a new server

When upgrading your server, we recommend that your hardware technicians follow the steps in this section to ensure your transition is as smooth as possible.


Server Migration options

Windows currently has some limitations (based on the Windows database engine that is packaged with the Windows Operating System) on the environment the Minfos database can migrate to.  This is due to the Microsoft esent engine version which the Minfos Database runs on is not backwards compatible when migrating to older Operating Systems. 


Note: Minfos recommends having a Windows 10 Operating system (temporary server option) available on the network in the event of Server failure.  This provides the option to migrate to a Server 2022 after the Server hardware issue is addressed.
* Windows 11 does not migrate to Server 2022

Listed below are the Database migration options (from operating system A to operating system B) available:

Migrate FromMigrate To
Server 2012 / R2Server 2012(R2) / 2016 / 2019 / 2022 - Windows 10
Server 2016Server 2016 / 2019 / 2022 - Windows 10/11
Server 2019Server 2019 / 2022 - Windows 10/11
Server 2022Server 2022 - Windows 10/11
Windows 10Server 2022 - Windows 10/11
Windows 11Unable to migrate from Windows 11 at this stage
Warning:  Migrating the database to an earlier Operating System version may not support the database migration.  Please ensure you are migrating to the same Operating System version or later. For example: Migrating from Windows 10 to Windows Server 2019 (or older) is not supported. Windows Server 2022 will be required to support the migration.

Server Migration Steps

In this section we have referred to the servers in the following way:

  • Old Minfos Server/Database: This is the system that is currently running and will be superseded
  • New Minfos Server/Database: This is the new system that will supersede the old Minfos Server


In this section:

  • Migration Preparation steps
  • Step 1: Run a manual backup of the old Minfos Database
  • Step 2: Set up the new Minfos Server
    • Retrieve information from the old Minfos Server
    • Set up the new Minfos Database
  • Step 3: Log into the new Minfos Database
  • Step 4: Migrate to the new Minfos Server
    • Backup the old Minfos Database
    • Copy data from the old Minfos Database to the new Minfos Database
    • Configure the new Minfos Database
  • Step 5: Update configuration files on Minfos clients
  • Step 6: Check that the new Minfos Server is set up correctly
  • Step 7: Take the old Minfos Server offline

Migration Preparation steps

Please be aware of the following steps which will require action after the server migration is complete:


Step 1: Run a manual backup of the old Minfos Database 

On the old Minfos Server:

1. Close all Minfos applications on all workstations except for the backoffice machine.

2. On the backoffice machine, leave the Minfos Launch Pad open, then close all other connections to Minfos, including PBS Online.

3. On the Minfos Launch Pad, click the Special menu, and then click Back Up Database. The Backup database window is displayed. 

If the Connections text box shows:

  • More than 0 connections, this means that Minfos (or a Minfos utility) is running on one of the pharmacy’s computers 
    1. Locate and close the Minfos program or service that is still running.
    2. Close the Back Up Database window then re-open it to refresh the connections, until there are “0” connections.
  • If “0” connections, check the Continue check box, then click Okay, to backup the old Minfos Database

Step 2: Set up the new Minfos Server

Note: We recommend that the new Minfos Server is set up before taking the old server offline.

Your hardware technician is responsible for setting up the new Minfos Server environment appropriately so that it runs efficiently for your store. See, “Minfos Server station” for hardware requirements and recommendations.

Retrieve information from the old Minfos Server

On the old Minfos Server:

  1. Log in as an administrator.
  2. Get the latest Minfos build:
    1. Download the latest Minfos software release—Minfos Launch Pad > File > Minfos Software Update > Yes.
    2. The SOFTUPD.exe package is located in the folder H:\MINFOS01\MNET\SOFTUPD.exe.
      1. You can copy the SOFTUPD.exe to the new server in the same location.
  3. Copy the following files and folders onto an external storage device:
    • F:\MINFOS01\DB\BACK\* (All files and folders). This is the latest Minfos backup and contains the following folders: 
      • CLAIMS 
      • FMT 
      • LABELS 
      • new
    • H:\MINFOS01\MNET\SOFTUPD.exe This is the latest Minfos software release that you downloaded in the previous step
    • H:\MINFOS01\dseback.dat
    • H:\MINFOS01\Multistore\* * Only required if your store is part of a Multistore group.
    • H:\MINFOS01\vcredist_x86.exe 
      • Microsoft Visual C++ 2010: vrcredist_x86.exe file version: 10.0.40219.1
  4. Write down the server’s MinfosNT value (also referred to as station number):
    1. On the server’s desktop, right-click the Computer icon, then click Properties.
    2. Click Advanced system settings, then click Environment Variables….
    3. Write down the value for MinfosNT, located in the System variables group box.

Set up the new Minfos Database

On the new Minfos Server:

  1. Add the same MinfosNT value as the old Minfos Server:
    1. On the server’s desktop, right-click the Computer icon, then click Properties.
    2. Click Advanced system settings, then click Environment Variables….
    3. In the System variables group box, click New….
    4. In the Variable name text box, enter “MinfosNT”.
    5. In the Variable value text box, enter the value you wrote down from the old Minfos Server, then click OK, to add the MinfosNT number.
  2. Create the following database folders:
    • H:\Minfos01\DB
    • F:\Minfos01\DB\BACK
  3. In the H:\MINFOS01 folder, paste the following files that you copied from the old Minfos Server:
    • H:\MINFOS01\MNET\SOFTUPD.exe
    • H:\MINFOS01\MinConfig.exe
    • H:\MINFOS01\dseback.dat
  4. In the F:\MINFOS01\DB\BACK folder, paste the folders that you copied from the old Minfos Server:
    • CLAIMS 
    • FMT 
    • LABELS 
    • new
  5. Copy all of the files in F:\Minfos01\DB\BACK\FMT and paste into H:\Minfos01\DATA.
  6. Copy the folder F:\Minfos01\DB\BACK\LABELS and paste into H:\Minfos01.
  7. Run Minconfig.exe and ensure the following information is correct:
    • Name / Address
    • ESE Database Locations and options
      1. Database: H:\MINFOS01\DB
      2. Backup: F:\MINFOS01\DB\BACK
    • Note: If you have issues running Minconfig.exe, run vcredist_x86.exe, then try running Minconfig.exe again
  8. Run H:\MINFOS01\MNET\SOFTUPD.exe and extract to H:\MINFOS01.
  9. Run H:\MINFOS01\Minw2d.exe.
    All Minfos files and folders are created and WCSDB5.exe starts automatically. Note: If WCSDB5.exe does not start automatically, start it manually.

    When prompted, restore the database, then confirm that the date and the time of the last dispensed script are correct.
  10. Create a shortcut for WCSDB5.exe on the Desktop and rename it “Minfos Server”.

Step 3: Log into the new Minfos Database

On the new Minfos Server:

1. Run minw2.exe.

2. Log in using the pharmacy’s credentials.

3. To set up a new client, or modify an existing one, follow the steps in “Preparing a new Minfos Client”.

Step 4: Migrate to the new Minfos Server

The migration process involves copying the most-recent data from the old Minfos Database to the new Minfos Database.

Note: Migrating the pharmacy’s data must be performed outside of trading hours.

Backup the old Minfos Database

This backup is only required if the pharmacy has traded since the last backup you performed in “Step 1: Run a manual backup of the old Minfos Database”.

If the pharmacy has not traded since the backup, you do not have to back up the database again. Continue to the next procedure.

Note: To backup the old Minfos Database see, “Step 1: Run a manual backup of the old Minfos Database ”.

Copy data from the old Minfos Database to the new Minfos Database

1. On the new Minfos Database, delete the contents of the following folders:

  • H:\Minfos01\DATA
  • H:\Minfos01\DB
  • H:\Minfos01\LABELS
  • H:\Minfos01\LOG
  • H:\Minfos01\XML
  • F:\MINFOS01\DB\BACK

2. Copy the .config and .log files from the old Minfos Database to the new Minfos Database:

  • H:\MINFOS01\*.config 

These files contain various configurations for eRx, Robotic Dispense, and other integrations.

  • H:\MINFOS01\*.log 

These files are important to keep as history of the database’s activity.

Tip: Large files can be zipped and renamed.

3. Copy the contents of the following folders from the old Minfos Database to the new Minfos Database:

  • H:\MINFOS01\LOG  

        This helps to ensure that log files are kept with the database, for diagnostic purposes.

  • H:\MINFOS01\XML 

        This folder contains previously downloaded claims reports and other third-party files.

  • F:\Minfos01\DB\BACK

        This folder contains the backup of your old Minfos Server Database.


Configure the new Minfos Database

On the new Minfos Database:

1. Copy all of the files in F:\Minfos01\DB\BACK\FMT and paste into H:\Minfos01\DATA.
2. Copy the folder F:\Minfos01\DB\BACK\LABELS and paste into H:\Minfos01.

3. Run Minconfig.exe and ensure the following information is correct:

  • Name / Address
  • ESE Database Locations and options

4. Run Minfos and check that all of the data is correct:

a. On the Desktop, run the Minfos Server (WCSDB5.exe).

b. When prompted, restore the database, then confirm that the date and the time of the last dispensed script are correct.

c. On the Desktop, run Minfos Launch Pad (minw2.exe), then confirm that all users can log in and the data is correct. For example, check that the script history, sales history, and stock order history are correct.

5. Check that the software and the database schema are synchronised:

a. Close the Minfos Launch Pad.
b. Run H:\MINFOS01\MNET\SOFTUPD.exe and extract to the default location.

c. On the Minfos Database window, click Update.

6. The Minfos software is updated. Ensure all client machines are connecting to the new server. Minfos requires the F: and H: to be mapped to the new server’s F: and H: drives.

Step 5: Update configuration files on Minfos clients

If the new server has a new machine name or a slight configuration change in MinConfig.exe, the configuration files on each Minfos clients must be updated. 

1. To update the configuration files on Minfos clients:

On each client machine, run command-prompt and run the following commands:

CD c:\Minfos01
Copy h:\Minfos01\dseback.dat
Copy h:\Minfos01\*.cfg

2. Run the Minfos Launch Pad (minw2.exe).

The Minfos software may update automatically on launch before you can log in.

Step 6: Check that the new Minfos Server is set up correctly

Before the new Minfos Server can go live, check that you can:

  • Scan and dispense an e-script
  • Scan a product and sell a script at the till
  • Perform a stocktake
  • If the pharmacy uses Loyalty, ensure you can perform a loyalty sale at the till

Step 7: Take the old Minfos Server offline

Your hardware vendor can advise you of the best way to decommission your old Minfos Server.

Step 8: Post migration

See section above: Migration-Preparation-steps

Also see: COO: Change of Server.


Workstations

This section defines the minimum and recommended system requirements for Minfos workstations.

Note: All workstations must be added to an Active Directory domain or workgroup.

Till stations

 

Recommended

Minimum

Processor

Intel® CoreTM i5 2.0GHz+

Intel® CoreTM i3 2.0GHz+

RAM

8 GB+

4 GB

Hard drives

250 GB SATA SSD

250 GB 7200rpm

Video adaptor

Must be capable of displaying minimum of 1024 × 768 True Colour (16 bit)

Monitor

15″+ TFT touchscreen

15″ TFT Display

Interfaces

Multiple USB 3.0 Ports

PS/2

USB 2.0 Ports

PS/2

Network adaptor

1Gb Ethernet

1Gb Ethernet

Operating system

Windows® 11 Professional 64-bit

Windows® 10 Professional

Microsoft .NET Framework

Version 4.6.2 or higher

Version 4.6.2

Note: Till must have a printer named Docket

Tablet stations

 

Minimum

Processor

Intel® AtomTM CPU Z2760 1.80GHz 

RAM

2 GB

Hard drive

50 GB

Display

1024 × 768

Interfaces

USB 2.0 Ports

Operating system

Windows® 10 32-bit

Microsoft .NET Framework

.NET 4.6.2


Dispense stations

 

Recommended

Minimum

Processor

Intel® CoreTM i7-7700

Intel® CoreTM i5 2.0GHz+

RAM

8 GB+

4 GB

Hard drives

250 GB SATA SSD

250 GB 7200 rpm

Network adaptor

1Gb Ethernet

1Gb Ethernet

Video adaptor

1600x900

1024 × 768 True Colour (16 bit) *

Monitor

22” monitor

Standard LCD display *

Interfaces

Multiple USB 3.0 Ports

USB 2.0 Ports

Operating system

Windows® 10 Professional 64-bit

Windows® 10 Professional 

Microsoft .NET Framework

Version 4.6.2 or higher

Version 4.6.2


* If you are running the Minfos Packing Module, Update Manger, or functioning as a Multistore Head Office, recommended is required as a minimum.


Backoffice and multistore headoffice stations

Minfos requires a backoffice station as the designated administration and reporting machine, which runs all third-party applications. The backoffice station is an integral part of your Minfos system and is a central go-to point for the Minfos support team.
For the backoffice and multistore headoffice station’s recommended hardware, see “Dispense stations”.

The backoffice station is designed to be the central location where all third-party applications are to be installed.


Barcode scanners

 

Minimum

Recommended

Hand Held

Motorola LS2208  (1D Scanner)

Zebra DS4608  (2D scanner)

Desktop

Honeywell MS7580 (2D Scanner)

Symbol DS9208  (2D scanner)

Other brands of scanners can be used (for example, many pharmacies use Symbol or Honeywell scanners); however, specific models should be tested for compatibility with the Minfos software before purchase.

Scanners are to accept the following barcodes, including all relevant expansion codes and check digits:

  • 2D   - QR code required for e-prescription
  • EAN-8
  • EAN-13
  • UPC-E
  • UPE-A
  • Code 128 C 
  • Interleaved 2 of 5

 Minfos recommends that the scanner has auto Carriage Return enabled for after barcodes are scanned.

Setup your Barcode Scanners

Zebra DS4608
1. Plug in the USB device.
2. Enable Enter Key / Line feed on the device:

  1. Use the Quick Start Guide Page 8 
  2. Scan the ADD AN ENTER KEY barcode to program


Symbol DS9208 
1. Plug in the USB device.
2. Enable Enter Key / Line feed on the device:

  1. Use the Quick Start Guide Page 1 (bottom) 
  2. Scan the Enter Key (Carriage Return/Line Feed) barcode to program 

 

Cash drawer

We support most standard cash drawers with USB and RJ12 connections.

Wireless stocktake scanner units

Minfos supports the following scanner models:

  • Honeywell EDA51 / EDA52
    • The Minfos App - Honeywell can be purchased from the Google Play store is supported on this hardware.
Other Honeywell models may be used, however, they should be tested for compatibility with the Minfos software before purchase.
  • Zebra TC25
    • The Minfos App can be purchased from the Google Play store is supported on this hardware.
Other Zebra models may be used, however, they should be tested for compatibility with the Minfos software before purchase.
  • Zebra MC32N
    • Minfos development ceased. Speak to your hardware vendor for support options.


Workstation setup requirements

Ensure that each workstation has:

  • The following mapped server directories:
    • F:\
    • H:\
  • Been set up to print to a laser printer; see “Standard print” for recommended printer specifications. The spool settings should be set to print directly to the printer and the paper size should be set to A4.

In addition, on each workstation create a:

  • Desktop shortcut to the Minfos application, with the appropriate command-line parameters:
    • On till stations, the shortcut should point to C:\minfo01\MINW2.exe /till
    • On dispensing stations, the shortcut should point to C:\minfo01\MINW2.exe /disp
  • Minfos user name.
    • On till stations, the user name should be in the format Txx (for example, T02).
    • On dispensing stations, the user name should be in the format Dxx

MinfosNT (station) numbers

A MinfosNT (station) number must be set up on each Minfos station. Station numbers are reserved and used by the Minfos Database to identify which station is in use.

Station numbers

Which station(s) to use them on

1 to 5

Reserved for till stations.

6

Required for the main backoffice station.
 If your server is running as shared server, then the backoffice and the server run on a single station 6.

This station runs all third-party applications, including: Minfos Automation Manager, PBS Online, eRX and MediSecure.

7 to 98

Available for other stations, including dispense.

99

Reserved for the Minfos Server station (unless a shared server is setup).

Note: 

  • All stations must have a unique station number.
  • Station 6 is a requirement for all Minfos sites and must be used as the backoffice machine for all third-party applications.

Setting a MinfosNT number

1. On the workstation, right-click the Computer icon, then click Properties.

2. Click Advanced system settings, then click Environment Variables….

3. In the System variables group box, click New….

4. In the Variable name text box, enter “MinfosNT”.

5. In the Variable value text box, enter the required MinfosNT number, then click OK, to add the MinfosNT number.

User-check Ensure the MinfosNT number is unique for each workstation.

 

Preparing a new Minfos Client

This section will guide you through the basic steps on how to setup Minfos on the client machine. It is the hardware tech’s responsibility to configure any network or domain settings.
To install or recreate a Minfos Client, you must have set up the:

  • MinfosNT (Station number). For instructions, see “Setting a MinfosNT number”. 
  • Mapping of the H drive and F drive. Mapping NOT REQUIRED from Minfos v 7.8.1

Note: If the store is running a serverless setup, see “Windows registry changes on client machines” and “NetBIOS changes required on all computers in the serverless LAN”.


Installing or recreating Minfos on a Minfos Client

1. Create the folder: C:\MINFOS01.

Alternatively, clear the contents of the folder if it already exists on the workstation.

2. Run command-prompt and run the following commands:

CD \ 
CD Minfos01
Copy h:\Minfos01\Minw2b.exe
Copy h:\Minfos01\*.cfg
Copy h:\Minfos01\Dseback.dat

If MS Visual C++ 2022 is not yet installed, run Copy h:\Minfos01\vcredist_x86_2022.exe 

3. Close command-prompt.

4. Run C:\MINFOS01\Minw2b.exe

Note: If you have issues running Minw2b.exe, run vcredist_x86.exe, then try running Minw2b.exe again.

5. Run C:\MINFOS01\Minw2.exe

6. Login using a valid Minfos username and password.

7. Create a shortcut for C:\MINFOS01\minw2.exe on the Desktop and rename it “Minfos Launch Pad”.

Printers

Minfos requires printers to be given specific names in Windows in order to communicate with them correctly. The required printer name must be set up in Windows for each printer on each station that will use that printer.

Dispense printers

We strongly recommend that each dispense station has its own dedicated printers for labels and repeats. This will help to make the printing process fast and efficient, and will also provide a level of redundancy in case one dispense station’s printers cannot be used.

 

Label printer

Repeats printer

Invoices/receipts

Type

Thermal

Laser

Laser

Supported models

Zebra ZD220

Zebra ZD420

Kyocera 2100 series +

Kyocera 2100 series +

Required printer name

LABELS

REPEATS

NOTES

Required paper size

4″ × 4″

A5

A4

Required driver

The latest Zebra driver, not the generic driver.

The latest driver.

The latest driver.


Till docket printers

Also applies to check-in counters. We recommend USB docket printers.

 

Recommended

Recommended models

Epson TM-T82 or higher

Purpose

Advanced docket printer that can also print 1D and 2D barcodes 

e.g. ePrescriptions

Driver

Epson Advanced Printer Driver

Is default printer

Yes

Printer name

(case sensitive)

Docket        * 

* If set as default printer, print preview feature may not work correctly.
Printer Name of Docket is required on the Minfos Till to print, regardless of configuration options
 

Other Docket printer configuration options:

1. If Docket printer is capable of printing barcodes BUT it's not the default printer, clone Docket printer to be DocketEx.

2. If no DocketEx printer is found, Minfos will send the job to your default printer. If the default printer is not capable of printing barcodes, then it will print plain text only.
Ensure your hardware vendor has supplied you with enough docket printer rolls before you start trading.


Backoffice printers


Standard printers

Minfos supports any standard laser printer that has the ability to supply label media and A4 paper from two separate sources. Standard 44 label sheets are also printable on a laser printer.

Type

Laser

Recommended models

Kyocera Mita P3045DN

Kyocera FS 2235DN (only for shelf label printing)

OKI Laser Printer (P/No: OKIpage 14i)

Required printer name

NOTES

Required settings

All paper sizes must be set to A4.

Power save timeout should be set to 30 minutes.

Note: This printer must be set as the default printer on every backoffice workstation.

Shelf label printers

 

Shelf Label Printer

Type

Thermal

Supported models

Zebra GC420d

Required printer name

SHELF

Required paper size

Stirling Fildes Thermal 3-across POS labels

Required driver

ZDesigner GC420d (EPL) 

To correctly print 3-across shelf labels, specify the paper size in your Windows printer settings:

Recommended printer settings: Control Panel > Printers >

  • Printing preferences > Custom Paper Size > Width: 10.80cm, Height: 2.50cm
  • Printer properties > Advanced tab > Printing Defaults > Width: 10.80cm, Height: 2.50cm
  • Printer properties > Advanced tab > Printing Defaults > Options > Width: 10.80cm, Height: 2.50cm
  • Printer properties > Advanced tab > Printing Defaults > Advanced Setup > Gap/Mark Height 0.30cm