VeriCentre 3.0 Upgrade Pre-Installation and Post Installation Guidelines

Transcription

1 VeriCentre 3.0 Upgrade Pre-Installation and Post Installation Guidelines * For actual installation steps, please refer to the VeriCentre 3.0 Installation guide that came with the VeriCentre 3.0 software. The pre-installation and post installation guidelines below should be used in conjunction with the VeriCentre 3.0 Installation document. Pre-Installation Tasks 1. Ensure the required prerequisites are installed a. VeriCentre (for Oracle or SQL Server) or VeriCentre LE b. IIS 5.x/6.x/7.x and MS.NET Framework (3.0 or 3.5) for VC server c. MS.NET Framework (3.0 or 3.5) for VC client-only machines. d. The required version of Oracle client and Oracle ODBC driver, if Oracle database is being used with VeriCentre 3.0. Oracle 9i/10g/11g versions are supported with VeriCentre 3.0. e. VeriCentre 3.0 is not supported on Windows 2000 OS. All machines need to have one of the following Windows OS versions: Windows XP /Windows Server 2003/Windows Vista/Windows 7/Windows Server f. In the case of SQL Server database, SQL Server 2008 cannot be used for a new VeriCentre 3.0 installation and it has to be one of SQL Server 2000/ SQL Server 2005/ SQL Server 2005 Express/ MSDE Once VeriCentre 3.0 is installed, then the VeriCentre database can be upgraded to SQL Server g. Microsoft.NET 3.0 Installation NOTE: We have come across situations where the Microsoft.NET versions installed on a machine was corrupted and this caused issues during the VeriCentre 3.0 installation as well as upgrade. The only solution in such situations was to uninstall all the Microsoft.NET versions on the given machine and install Microsoft.NET 3.0 packaged with VeriCentre 3.0 and then reinstall VeriCentre 3.0. To prevent the possibility of such an issue occurring during a production upgrade to VeriCentre 3.0 and thereby increasing the production downtime, we recommend that you uninstall all the existing Microsoft.NET versions in the reverse order of the version numbers (like 3.5, 3.0, 2.x, 1.x) and then directly install Microsoft.NET 3.0 that is packaged with the VeriCentre 3.0 software. This step can be done well ahead of VeriCentre 3.0 installation/upgrade. 2. For large amount of terminal records, duplicate your production VeriCentre installation in a test server against a copy of the production database and perform a mock upgrade to see how long it will take for the entire upgrade to complete. This will give you an idea on how much downtime you ll need on actual cut-over day. 3. Copy the required VC 3.0 software (base version, service pack, patches, and hot fixes- if any) into a staging directory in each VC server(s) and VC clients. Do not install VC software from a network drive. Unzip all the files prior to cut-over day because we don't suggest running the setup.exe inside the zip file. Running setup.exe inside the zip file will cause the installer to fail. 4. Take a backup copy of the VeriCentre root folder. The VeriCentre default folder is found in c:\program Files\VeriCentre. Backup the VeriCentre database. Backup the VeriCentre registry as well by running the command below as-is in a Dos screen. The backup VeriCentre registry will be saved in vc2reg.txt file. regedit /e vc2reg.txt HKEY_LOCAL_MACHINE\SOFTWARE\VERIFONE\VERICENTRE

2 *Note: The backup VeriCentre folder and the registry will be useful if you have to roll back during your cut-over day. Roll back would require that you reinstall the old VC 2.x software and then restore the backup VeriCentre folder, the VC 2.x database, and the VeriCentre registry. 5. Ensure that the registry value fipsalogorithmpolicy is set to zero (0). This registry is found under the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. If this is set to 1, VC installer will fail to connect to the database during the upgrade. 6. Ensure that TCP port 8086 in VC primary/license server is reachable by all secondary servers and VC clients. This port is new in VC 3.0 and it is needed when installing VC 3.0 server or client. Test this port using telnet especially if there is a firewall between the primary server and the secondary server or VC clients. To test this port if it's reachable you'll need a software that will listen on port Since VeriCentre server is still in version 2.x and does not use this port, you may run this small stand-alone port listener utility in your current VeriCentre primary server to listen on port This tool can be downloaded from the link below. ftp://ftp.verifone.com/support/vericentre/tools/portlistener.zip NOTE: Please ensure that you don t have any other software running on your VeriCentre primary server that listens on TCP port 8086, since this is a reserved listener port for VeriCentre 3.0 on the VeriCentre 3.0 primary server machine and it is not configurable. The TCPView tool can be used to verify if this port is being used and if so, the name of executable that is using this port. The TCPView tool can be downloaded from the link given below: 7. Please refer to document link below for the list of TCP ports used by VC 3.0. Open the ports used by VC 3.0 in your firewall as necessary. ftp://ftp.verifone.com/support/vericentre/vc30docs/tcp_ports_used_by_vericentre_3.0_sp1.pd f 8. Run the following SQL statement against the VC database to ensure that all VC modem ports configured as TAPI will continue to work after the upgrade. update cm_dial set modemtype = null where USETAPI = 'YES' 9. If you are using Timed Import Service, open the Timed Import Configuration screen and you'll need to note down the configuration because after the VC 3.0 upgrade, the Timed Import Service will need to be reconfigured again. 10. On cut-over day, if you will be using remote desktop to connect to the VC server, ensure that you are connected at the console session (session id=0). Otherwise, some modules will not be installed. You can use Windows Task Manager->Users tab to see your session id under the ID column. The document link below shows you how to connect to the console session. ftp://ftp.verifone.com/support/vericentre/docs/how_to_connect_to_console_session.pdf

3 11. Keep a downloaded copy of Microsoft.NET Framework 3.5 SP1 handy, in case there is a need to install Microsoft.NET Framework 3.5 SP1 on any of the VeriCentre machines. Downloading Microsoft.NET Framework 3.5 SP1 from the Microsoft website can be a very time consuming process and we recommend that this download be done well ahead of the VeriCentre 3.0 installation/upgrade. 12. Ensure that Acrobat Reader is installed on the VeriCentre server machines, since this is needed to view the VeriCentre installation guides. 13. If you are using Web Console, please ensure that you have the latest version of Web Console 2.1 or 2.2 available for installing. Web Console version will not work with VeriCentre Use the query given below to get the number of VeriCentre users that are configured in your VeriCentre database: select count(*) from CORE_USER where upper(username) not in (upper('install'),upper('system')) If the output of the above query is greater than 500, then VeriCentre 3.0 Enterprise version will not allow you to add any new VeriCentre users, since VeriCentre 3.0 Enterprise version has a total user limit of 500. If you have more than 500 VeriCentre users, please review the existing user accounts in VeriCentre and delete any VeriCentre user accounts that are no longer being used. 15. Please ensure that there are no duplicate USES directives in any of your terminals in VeriCentre 2.x, since it will result in download failures once you upgrade to VeriCentre 3.0. Please use the information given in the link below to detect and remove any duplicate USES directives in any of your terminals in VeriCentre. ftp://ftp.verifone.com/support/vericentre/vc30docs/faq_recursion_in_uses_error_vc30.pdf Troubleshooting Tips during Installation/Upgrade of VeriCentre If you are installing VeriCentre 3.0 on a Windows Vista/ Windows 7 / Windows Server 2008 machine, then please follow the steps given in Appendix A of this document prior to installing VeriCentre Install or upgrade VeriCentre 3.0 in the following order: VeriCentre primary server, VeriCentre secondary servers and the VeriCentre clients. 3. While installing (not upgrading) VeriCentre 3.0 clients or VeriCentre 3.0 secondary servers, the VeriCentre 3.0 installer has to connect to TCP port 8086 on the VeriCentre primary server machine to get the licensing and database related information. If the VeriCentre installer is unable to connect to TCP port 8086 on the VeriCentre 3.0 primary server, it will not be able to proceed with the installation. To troubleshoot this issue, please verify the following: a) Verify that TCP port 8086 on the VeriCentre 3.0 primary server is accessible from the given VeriCentre client or secondary server machine using the TELNET command as given in the pre-installation section of this document. It is possible that firewall settings may be causing this issue. b) If the above test is successful, then verify that TCP port 8086 on the VeriCentre 3.0 primary server is being used by the executable named VCLicenseInformation.exe, which

4 is the VeriCentre 3.0 License and Information Manager service. The TCPView tool can be used for this purpose and it can be downloaded from the link given below: c) If the above test is also successful and if the VeriCentre installer is not able to connect to TCP port 8086 on the VeriCentre 3.0 primary server, then uninstall all the Microsoft.NET versions in the reverse order of the version numbers (3.5, 3.0, 2.x, 1.x) and directly install.net 3.0 that is packaged with the VeriCentre 3.0 software and then try the VeriCentre 3.0 installation again. 4. If Windows Vista/Windows 7/Windows Server 2008 OS is used, then at least SP2 for VeriCentre 3.0 and Patch 1 for SP2 should be installed before you can verify if the upgrade/installation is successful. Please ensure that you also install the latest VeriCentre updates that were released after Patch 1 for VeriCentre 3.0 SP2. Post Installation Tasks After VeriCentre has been upgraded to 3.0 and all the required service pack, patches, and hot fixes have been installed, please perform the following tasks: 1. After installing SP2 for VeriCentre 3.0, the VeriCentre Installation guide in the Docs folder under the VeriCentre installation folder (usually C:\Program Files\VeriCentre\Docs) got incorrectly replaced with a zero byte file with the same name. Please replace this zero byte file (27656_VeriCentre_3.0_Enterprise_Installation_Guide.pdf) with the correct file from the Docs folder in the VeriCentre 3.0 software image that you used for installing VeriCentre Please complete the post installation steps for IIS 5.x/6.x/7.x that is given on page 23 in the VeriCentre 3.0 Installation guide. This has to be done on the VeriCentre 3.0 primary and secondary servers. 3. When VC Server service is running and all downloads are working but Monitor Server is not running as seen in VC Server Manager UI. It's possible that the TCP port 8000 and/or 8001 is being used by another application. These 2 ports need to be available for VC monitor server, otherwise the Monitor Server module (VTMonitorServer.exe) will fail to start. You can test the port by stopping VeriCentre Environment Monitor service to ensure all VC modules are not running, and then run the telnet command below executed from the command prompt. Test both 8000 and telnet If there is no application listening on this port, you will see a blank DOS screen open and close immediately. This is the behavior you want. Otherwise, a blank DOS screen will open and stay open. If this happens, you may configure VeriCentre Monitor server to listen on a different port. Choose any port that is not being used by any application, use telnet to verify. Once a port is selected run the SQL statement below to find out which record to change: select * from core_server *Note: You may need the assistance of your DBA when making this change. *Important: You need to ensure that the servername found in the registry value Hostname are all in CAPS. The Hostname registry value is found under the registry key HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Services\Tcpip\Parameters. If the

5 servername is in mixed case or if they are all in lower case, VC monitor server will continue to use the default ports and therefore it will continue to fail to start. 5. After VC 3.0 installation (server or client) is completed, please check Windows AT jobs and ensure that you only have the required jobs running on each VC installation. To display the list of job, type AT in DOS screen. To delete a job, run the command below: at <jobid> /delete i.e. at 1 /delete Please refer to the list of jobs that should be running on each VC installation: (Delete VeriCentre jobs as necessary to reflect the required jobs listed below) a. VeriCentre Primary Server/License Server i. DA_SchedulerMaintananceUtil.exe ii. RemoveDRTempFolder.exe iii. purge.exe /schedule b. VeriCentre Secondary Server (if available) i. RemoveDRTempFolder.exe c. VeriCentre client i. (NO VERICENTRE JOBS SHOULD BE RUNNING HERE) 6. If you are using Timed Import service, install Timed Import service again by running the command below in a DOS screen. VCTimpSv.exe /service *Note: Execute the command above under the <VCHomeDir>\bin folder, and the reconfigure Timed Import by running <VCHomeDir>\bin\TimedImportConfig.exe. 7. If you are using Oracle database, run the post installation script downloadable from the link below that will fix Global Editor functions. ftp://ftp.verifone.com/support/vericentre/vc30docs/vc30postinstallscript_ora.txt 8. If you open Report Manager and you don't see any preinstalled reports in the right pane, it's most likely that you used remote desktop to connect to VC server and did not connect to the console session. To rebuild the reports in Report Manager, follow the procedure in the document link below: ftp://ftp.verifone.com/support/vericentre//faq/faq285_reportsmissing.pdf 9. If you have installed VC secondary server (not primary server), set the VeriCentre Download Automation Scheduler service to Manual. By default, this service is set to Automatic upon completion of VC 3.0 upgrade. This service should only run on 1 VC server, which is by default the primary server. Therefore, if this service is started in secondary VC server, it will fail and log an entry in Windows Event log which can cause some confusion to the user thinking that it s a critical issue.

6 10. If the VeriCentre Console crashes when it is launched for the first time, it is possible that the Microsoft.NET installation on this machine has become corrupted. In this case, please uninstall all the Microsoft.NET versions in the reverse order of the version numbers (like 3.5, 3.0, 2.x, 1.x) and then directly install Microsoft.NET 3.0 that is packaged with the VeriCentre 3.0 software and then try the VeriCentre installation/upgrade again.

7 Appendix A - Installing VeriCentre 3.0 and Web Console on Windows Vista/Windows Server 2008/Windows 7 Title: Installing VeriCentre 3.0 and Web Console on Windows Vista/Windows Server 2008/Windows 7 Question: We are planning to install VeriCentre 3.0 and Web Console on Windows 2008 or on Windows Vista / Answer: Windows 7. Do we need to do any additional steps in addition to the standard prerequisites for installing Web Console on Windows 2003 Server? Below are the additional steps that need to be done when installing VeriCentre 3.0 and Web Console on Windows 2008/Windows Vista/Windows 7: I. Install IIS 6.0 Compatibility components. To install the IIS 6.0 Management Compatibility Components by using the Windows Server 2008 Server Manager 1. Click Start, click Administrative Tools and then Server Manager. 2. In the left navigation pane, expand Roles, and then right-click Web Server (IIS) and select Add Role Services. 3. On the Select Role Services pane, scroll down to IIS 6 Management Compatibility. 4. Select the check boxes for IIS 6 Metabase Compatibility and IIS 6 Management Console. 5. Click Next from the Select Role Services pane, and then click Install at the Confirm Installations Selections pane. 6. Click Close to leave the Add Role Services wizard. To install the IIS 6.0 Management Compatibility Components by using the Windows Vista or Windows 7 Control Panel 1. Click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off. 2. Open Internet Information Services. 3. Open Web Management Tools. 4. Open IIS 6.0 Management Compatibility. 5. Select the check boxes for IIS 6 Metabase and IIS 6 configuration compatibility and IIS 6 Management Console. 6. Click OK. II. Run the command below as-is: %SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/"

8 III. Disable User Account Control (UAC): UAC can be disabled by typing MSCONFIG from command prompt, click on Tools tab, select Change UAC Settings and click Launch button. Slide the bar all the way down to Never Notify in the UAC Settings screen and then click OK. On Windows Vista and Windows 2008 R1 versions, the Tools tab showed Disable UAC and does not have a slider bar.