HOW TO GUIDE. Pcounter for Windows Upgrade to version 3.02 with SQL Express. For Support Click here

Transcription

1 INTRODUCTION This document details how to upgrade Pcounter for Windows. Upgrading Pcounter for Windows is a quick and easy job, requiring almost no down time. A restart of the Pcounter services is the only downtime necessary. Consequently an upgrade can be performed during normal working hours with minimal disruption Click here to access further How to Guides This guide assumes Pcounter for Windows 2.87 or above is already running on the server, and there are no issues with the current configuration. Correct any issues before continuing with this guide. At this time, all print components of Pcounter 2.x are compatible, so only the components that interact with data are newer. For example, Pcounter Printer Control service, ports, and clients are the same for now. Install Pcounter 2.x and then unzip the beta components over the top, including subdirectories, and the new data components will be updated. There will still be the concept of the Pcounter data server and the Pcounter share. The Pcounter Data Server service will still run on the data server, and will automatically create and/or modify the Pcounter database schema when it is started up. Microsoft SQL, MySQL, and Oracle databases/drivers are supported. Drivers may need to be installed if the database server is not local. 1. Install SQL Express on the Pcounter data server. SQL Express with Reporting Services is highly recommended. Best Practice Tips If you prefer to err on the side of caution it is recommended that you take a quick backup of the Pcounter share (default C:\PCOUNTER) before upgrading For Support Click here

2 Leave all features at default Choose Named Instance SQL Express Leave all features at default

3 Select Mixed Mode, set sa password, click next If you do not wish to use the built-in "sa" administrator account, you can create and use an account called "pcounter" and assign "dbcreator" and "public" server roles later. At Reporting Services Configuration choose Install and Configure, click next Check all features have status Succeeded and close.

4 2. Configure using Microsoft SQL Management Studio Check that SQL server set up using mixed mode (SQL Server and Windows Authentication Mode). Useful Note Pcounter services such as the Pcounter Data Server service and embedded products such as Pcounter XAuditron must use SQL Server authentication mode. UI applications such as Pcounter Administrator can use either SQL Server or Windows authentication modes. However, to avoid conflicts, all applications will use SQL Server authentication mode when running on the Pcounter data server. Users running Pcounter Administrator on remote computers can use Windows authentication mode. a. In SQL Server Management Studio Object Explorer, rightclick the server, and then click Properties. b. On the Security page, under Server authentication, select the new server authentication mode, and then click OK. c. In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server. d. In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be restarted e. If you do not wish to use the built-in "sa" administrator account, create and use an account called "pcounter" and assign "dbcreator" and "public" server roles. The same server roles should be assigned to Windows users using Pcounter Administrator and Windows authentication mode.

5 Ensure enforce password policy is not checked f. Using Pcounter Administrator from remote computers requires remote connections to be enabled. In SQL Management Studio, connections, tick Allow remote connections to this server.

6 sure that the SQL Server Browser service is enabled/running. Remember Remember If your licence has expired you can still upgrade by coming back into maintenance. Contact for more details. If you experience any problems feel free to contact Support on , or /support All new features in a Pcounter update are Detailed in the README, which is unpacked during the installation h. Open the SQL Server Browser properties, set the start mode to automatic, apply, and start the service. i. Open TCP/IP properties, enable the protocol, set the TCP Port to 1433, remove TCP Dynamic Ports value.

7 g. In SQL Server configuration manager, make Open the SQL Server Browser properties, set the start mode to automatic, apply, and start the service.

8 3. Configure Pcounter to new SQL database a. Open Pcontrol, select server from Quick server list, select Configure Pcounter server b. On Data Server tab, enter new database set up path to point to new database. Use the Test/Status button to test the database connection. This is correct, as the Pcounter database is not yet configured

9 c. Click on Services / Ports within Pcontrol Configuration you should see that all the services are at 2.XX but the current version in the header says version 3.xx d. Stop the Services

10

11 e. Update and start the services f. The Pcounter database will now be created.

12 g. Test database connectivity as above.

13 Pcounter has now been upgraded to version 3.xx!

14 4. MySQL Notes It will be necessary to create or modify users and privileges which can connect to the Pcounter database, using MySQL Workbench. Click on "Users and Privileges" under Management. Either "Add Account" (create a new user such as "pcounter") or select an already created user, other than root. Under the "Login" tab, set the user's password. Under the "Administrative Roles" tab, grant all privileges. Under the "Schema Privileges" tab, select all and save. 5. Oracle Notes These are notes for configuration on a client machine, ie. Oracle is running on a remote server. Assuming the values: Global Database Name: orcl System Identifier(SID): orcl Install the Oracle Instance Client. If needed, create a NETWORK directory, then within that directory create an ADMIN directory, and then create and configure your "tnsnames.ora" file. For example, start in the path D:\app\username\product\11.2.0\client_1 (where D:is the drive where the Oracle software is installed). Example full path: D:\app\username\product\11.2.0\client_1\NETWORK\ADMIN\tns names.ora Typical tnsnames entry to connect to remote database: ORCL_REMOTE = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = OracleServerIP)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = ORCL)) Edit the Registry settings for Oracle and ODBC; make sure the settings point to correct drivers. (xxxx = version numbers) HKEY_LOCAL_MACHINE ODBC ODBC.INI ODBCINST.INI ORACLE Wow6432Node ODBC ODBC.INI ODBCINST.INI MySQL ODBC xxxxx

15 Oracle in Oraxxxxx SQL Server Native...

16 6. Migration of data from Version 2.xx The utility Dbupdate3.exe located under C:\Program Files (x86)\pcounter for NT\NT\ must be run to migarate data from version 2.xx. The data migrated is: User Account Balances/Free Quota Auto Client Codes Client Codes Client Code List Associations Pcounter Pro ID/PIN Numbers Pcounter Users Pcounter log file data: eg \\SERVER\SHARE\PCOUNTER\DATA\PCOUNTER.LOG \\SERVER\SHARE\PCOUNTER\DATA\PCOUNTER_xx.LOG \\SERVER\SHARED\PCOUNTER\DATA\REJECT.LOG Is also migrated to the SQL database.