INFUSION BUSINESS SOFTWARE Installation and Upgrade Guide

Transcription

1 INFUSION BUSINESS SOFTWARE Installation and Upgrade Guide 27/01/2016

2 Published by Infusion Business Software Ltd All Rights Reserved Copyright Infusion Business Software Ltd 2012 Copyright No part of this book may be reproduced transmitted in any form or by any means, including photocopying without the permission of the author. Disclaimer: Because of the possibility of human or mechanical error the material contained within this book is supplied without representation or guarantee of any kind. The publishers and author are not responsible for any errors or omissions or the result from the use of such material. All accounting information used in this book is to help understand how the program can be used. It is important to seek the advice of the business accountant to ensure that all tax issues relevant to the business are covered.

3 Installation and Upgrading These instructions are for the installation and upgrade of Infusion software on a standalone workstation, peer to peer network or LAN. To install Infusion software firstly download and save the appropriate package from If the install is an upgrade make a full backup of the existing version of the software (ie. Data, Custom and Images folders). Modify the name of the backup to include a note signifying it is a pre upgrade backup and what version is being upgraded eg IBSDATA b4upgrade503. Refer to the Release Notes relating to the version being installed for information on whether upgrades need to be done on workstations. To start the install Double click on the.exe file. Select Next to this The License Agreement form will then display

4 After having read the License Agreement select the I accept the agreement radio button if you agree with it. Select Next From the Select Components form select the components that are to be installed. Typically both options are selected for the computer the Infusion data is stored on while only the Workstation option is selected for a workstation install. The Workstation install needs to be done on all workstations accessing Infusion Select Next If the "Workstation component files" option was selected you will be prompted for the folder to install these files into. Type this in our browse to the required location. Select Next

5 If the "Database files" option was selected you will be prompted for the folder to install the Database files into. This is typically the same folder as the Workstation install but can be in a different location. eg a separate drive possibly on a server location. (the example above shows this as F: drive). Type in or browse to the required location. Select Next If the "Workstation components files" install was selected the next form is Additional Tasks. Note: If Database ONLY option was selected, go to the Ready to Install step. Select the "Create a desktop icon" option to create a shortcut on your desktop. Select Next to be shown the "Enter Icon Name" form.

6 Enter the name you want displayed with the Icon. Infusion Setup Wizard will then prompt you to install the software. Select Install

7 Once the install has completed the following form will display. Select Finish

8 Uninstall Wizard If only the "Workstation component files" option was selected only the files required to run Infusion and Help files are installed (plus two Unins000.* files). Run unins000.exe to uninstall and de-register the install. The unins000.exe is only created when the Workstation component is installed. IMPORTANT NOTICE: If you install FULL or both Workstation and Database at the same time, running unins00.exe will uninstall both the Workstation AND the Database so it is recommended that two installs are done: firstly install the Database then run it again to install the Workstation. Double click Unins000.exe in the workstation folder. If any files are no longer needed you may be presented with the following. Followed by:

9 Anti Virus software A number of antivirus software packages slow the speed and performance of Infusion as well as lock files. Because of this the Infusion root folder should be added to any exclusion folder available within the antivirus software setup on all computers running Infusion. Windows Data Execution Prevention (DEP) Infusion (v5.0 and above) requires that it is excluded from Windows Data Execution Prevention (DEP) This setting can be located (on Windows 7) by right click on Computer, Properties, Advanced System Settings, Advanced, Settings tab. Select the Data Execution Prevention tab. If the system is set to the 2 nd radio button option ( Turn on DEP for all... ) select Add... to include Infusion (ibsapp.exe) as a program to exclude. When selecting this file make sure it is located through the same path as that on the user desktop shortcuts. If the first radio button was shown as selected when the window was opened, change it to the second option, follow the process above then restart the computer. Server Message Block (SMB2) Networks with computers having operating systems of Vista and above (ie support SMB2) will require disabling of SMB2. For assistance with this see the Workaround section of This is to be done on Vista and above computers. If it has already been done you will see a file names SMB2 sitting under Parameters with a value of 0 (zero) To disable SMB 2.0: 1. Click Start, type regedit in the Start Search box, and then press ENTER. 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters 3. On the Edit menu, point to New, and then click DWORD Value. 4. Type SMB2, and then press ENTER. 5. On the Edit menu, click Modify. 6. Type 0 (zero), and then click OK. 7. Exit Registry Editor. 8. Restart the computer.

10 Configuring opportunistic locking in Windows: The location of the client registry entry for opportunistic locking has changed from the location in Microsoft Windows NT. In later versions of Windows, you can disable opportunistic locking by setting the following registry entry to 1: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\ Oplock sdisabled REG_DWORD 0 or 1 Default: 0 (not disabled) Note The OplocksDisabled entry configures Windows clients to request or not to request opportunistic locks on a remote file. You can also deny the granting of opportunistic locks by setting the following registry entry to 0: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters EnableOplocks REG_DWORD 0 or 1 Default: 1 (enabled) Note: The EnableOplocks entry configures Windows-based servers to allow or to deny opportunistic locks on local files. These servers include workstations that share files. See:

11 Workstation Installation For a workstation on a LAN a network drive needs to be mapped to a shared directory on the Server created for Infusion Networked Workstation Installation: In the above example, the directory Accounting was shared on the network, each client machine needs to map the network drive to \\server\accounting (where server is the name of your server, and accounting is the name of the share you created). Once this has been completed, Infusion is able to run from the Infusion folder on the network drive. The executable is called ibsmain.exe. It is recommended that a shortcut to this file is placed on the user's desktop. All data is stored in the Infusion folder on the server, and should be backed up on a regular basis. If there are multiple installations of Infusion on the workstation computer, rename the shortcuts and icons to something other than "Infusion" before any additional installations are done otherwise they will be overwritten. Each User who accesses Infusion must have Full Control permissions for the Infusion Directory and all sub folders Once the installation is completed, select the icon on the desktop to open Infusion Printers and layouts are selected per computer and will need to be selected for a new installation. If there are several versions of Infusion that a computer will access it is only necessary to install the System Files once. A shortcut can be created to IBSMAIN.EXE file for each additional data file. When checking or creating any shortcuts: The target should point to the IBSMAIN.EXE file being used for this installation of the software. The Start In directory should be the Infusion folder (or other named folder) where Infusion was installed to on the server. While it is not essential to map network drives this is the recommended method. Standalone Workstation Installation: Install Infusion as per a Server install saving it to a local drive on the workstation. The default path is C:\Infusion.

12 Requesting / Entering an End User License Upgrading within version eg v6.00 to v6.20 will not require a license key for the software. If it is being done on a version prior to the version being installed eg v5.03 upgraded to v6.20, upon completing the initial steps of the upgrade you will be prompted to re-open Infusion. Doing so will display the following message: Click OK: to open the Software License Agreement window where upon after carefully reading Infusion Software Limited Terms and Conditions. Click I Agree: The Enter License Information window will appear. For a new install enter in the required information ie Company details, number of users required, modules and package. Click Print: to print out a faxable copy. Fax the License Request to The Request form must be signed by the Certified Partner Once Infusion Business Software Limited has processed the request and faxed / ed it back enter the License # and System ID. Click Save. Your Infusion software will now be licensed for use.

13 Minimum Hardware Specs for Operating Infusion Software For a Standalone Installation: PC (OS X, UNIX and its variants are not supported). 100 MB of free Hard Drive Space (excluding normal operating requirements). 2GB RAM i5 2GHz Processor Operating System: Windows 7 Network Server Installation: PC (OS X, UNIX and its variants are not supported**). At least i5 2GHz Processor 4GB RAM. 200 MB of free Hard Drive space (excluding normal operating requirements). Windows 7, Windows 10 Windows 7, Windows 10 Server 2008 R2 (32 and 64 bit), Server 2012 R2 Network Workstations: PC (OS X, UNIX and its variants are not supported). 100 MB of free Hard Drive Space (excluding normal operating requirements). 2GB RAM. i5 2GHz Processor Windows 7 Windows 7 (Workgroup and Domain). All work stations should ideally have the same Operating System. Network: A Gigabit network or VPN connection. Monitor: Minimum resolution 1280 x 1024 There is no technical reason for a SAMBA implementation on a Linux server not to be supported. The SAMBA share must be configured to allow full read / write access to the Infusion directory. Windows XP Home, Windows XP Media Centre Edition 2004 & 2005, Windows Vista Home Basic and Windows Vista Home Premium are not officially supported by Infusion Software as none of these Operating Systems are intended for business use. They have various limitations such as lack of Remote Desktop access for support purposes and limited network capabilities.

14 Infusion Software Hosted Server Hardware Specifications The following is the recommended hardware minimum specification and operating system configuration to operate Infusion software across a Remote or Hosted server: Server: Two + (clustered) Dual/Quad Core processor with at least 8GB ECC RAM (preferably 16 GB) Hardware: HP ML350 or DL380 with a Raid 5 setup and a minimum of 3*250GB Serial ATA Hard drives. Operating System: Server 2008 Terminal Services Backup: VSS Drive 250GB + (LTO) Workstations: If new work stations are to be supplied then we would recommend the following HP computers or better: HP dc 74xx series desktops Windows 7 i5 2GHz Processor 2GB RAM 160 GB Hard Drive If existing computers are to be used the recommended specification for these is at least: i5 2GHz Processor 2 GB RAM Windows 7 40 GB Hard Drive Video must run at least 1280 x 1024 Laser Printer Network Connectivity: Gigabit Network Adapter + ADSL Router

15 Infusion Software and Terminal Server Permissions This section outlines the file and folder permissions required by Infusion to successfully run under a Terminal Server session. System Requirements: The following are minimum recommended system requirements for Infusion software across a Terminal Server environment. These are meant as a rough guide only and are subject to revision. Processor Dual Core Dual Core RAM 4 GB 4 GB Hard Disk SCSI - base of 1 GB plus 10 MB per User SCSI - base of 1 GB plus 10 MB per User Operating System Server 2008 Server 2012 Permissions required by Infusion: Infusion requires Full Read and Write access to its root folder and subsequent sub folders. When running Infusion for the first time, Infusion creates a file called setup.ibs in the current user s document folder (C:\Documents and Settings\%USERNAME% for Windows Server 2003). Infusion requires read access to the System32 folder. Installation on the Server: Infusion requires Administrative access to install on the Server. By default Infusion is installed to the root of the system drive (typically C:\). Infusion also places a number of visual basic DLL files in the %SYSTEMROOT%\System32\ folder.

16 Infusion and Windows Server 2008 Remote App Server: Windows Server 2008 includes an extension to Terminal Services called Remote App. Remote App allows a single application to run on the client PC via Terminal Services while allowing the user to retain full control over their desktop. Infusion software will run over Remote App. The application runs in its own window and to the user appears as if the application is installed on their local machine. As well as supporting the standard features of a Remote Desktop Session such as port and disk redirection, Remote App also makes use of a new feature called Easy Print. Easy Print allows local printers to be available under a Terminal Server Session without the requirement of having to install the driver on the Server first. Windows Server 2008 Terminal Services Roles Infusion Client Machines: CCD Barcode Scanner (P/S2) Cash Drawer (Serial & Drawer Kick Models) Receipt Printer (Serial & Parallel) Pole Display (Serial) The hardware listed above was tested as working with the latest build of Infusion at the time of writing. The server was running Windows Server 2008 Enterprise with the latest available updates, the server was configured a Terminal Server and as a member on a domain. The POS unit was a standard Windows XP SP3 PC. Remote App was configured with all default options and was deployed to the POS unit by means of an MSI file.

17 Terminal Server Installation Infusion supports installation in a Windows Terminal Server. It is important to follow the below steps to ensure Infusion functions as expected. Install Process: Log in to the Terminal Server computer as a user with Administrative rights. Put the Terminal Server into Install mode by typing "change user /install" into the DOS prompt Install the software Put the Terminal Service into Execute mode by typing into the DOS prompt "change user /execute". A reboot will automatically put into execute mode. If this is not done there will be OLE errors when logging in from workstations (but not the TS) Follow the on-screen prompts to install Infusion. When prompted for an install destination, install Infusion into the folder C:\infusion4ts\. Once the installation has been completed, the directory permissions need to be set on the Infusion directory. The group Domain Users require full control of the Infusion directory. All users of the Terminal Server should now have an Infusion icon on their desktop. If you have multiple company files (mentioned below), you will be required to create a shortcut to these subsequent companies ( ibsmain.exe ). The shortcut should be through a mapped drive (eg. d:\accounting\infusion\ibsmain.exe). Once installation has been completed, the infusion4ts directory can be copied to a different location and renamed to allow creation of other Infusion folders for other companies. When any of these different copies of Infusion are run by the user, they will continue to use the original installs system files. Any new copies of the Infusion folder require the permissions to be set. If the Data file for Infusion does not reside on the Terminal Server the mapped drive letter needs to be added to the Allowed Sites list in Internet Explorer on the Terminal Server. This is done through Tools \ Internet Options \ Security \ Local Intranet \ Sites \ Advanced and in the Add this website box add the drive letter for where Infusion data is located.