Overview

Although PAWS is Internal Audit's legacy application and is no longer supported, clients will sometimes retain a working instance so that historic data can be viewed.

 As hardware fails and OS's become unsupported, so it may be necessary to move PAWS from an old server to a new one.

 This is a brief checklist guide to the procedure.  It is assumed that the new server will:

• Host the PAWS database
• Host the workpapers and templates
• Run the client application, to be RDP'd to by the few audit users who require access
• The Web modules will not be installed

 Overview of Steps

• Copy the PAWS database from your old database server to the new one
• Set up a database user or users as dbo within the application.  This can be a SQL account, or the Windows accounts of the end users
• Copy the file share containing workpapers and templates to the new server
• Share this, e.g. as \\server.domain.com\paws
• Grant read access to this share to the end users
• It is necessary to set the compatibility mode of the two application installers to Windows XP. Do this for:
• Ideagen Internal Audit (Aura) Work System v8.4.0\Full Installation\Installation Set\setup.exe
• Ideagen Internal Audit (Aura) Work System v8.4.0\Full Installation\Administration Tools\setup.exe
• Run Ideagen Internal Audit (Aura) Work System v8.4.0\Full Installation\Installation Set\setup.exe and follow the wizard (be sure to Run as Administrator)
• Run Ideagen Internal Audit (Aura) Work System v8.4.0\Full Installation\Administration Tools\setup.exe and follow the wizard (be sure to Run as Administrator)
• From the old client installation, copy the files paws.lic and paws.pds into the newly installed client folder
• On the new server, from the Start menu, run PAWS v8.4 > Database Configuration Manager (be sure to Run as Administrator)
• Click File > Open and open the PDS file
• Update the server name, and anything else that may have changed (e.g. database name or authentication type)
• Click the red question mark in the toolbar to test connection.  After a successful test, do not test the connection to the LOCAL database
• Run PAWS
• Click on the System Admin group on the spine
• Click on the System Configuration icon
• Click on the Work papers tab
• In the Work papers section, enter the new path to the workpapers folder, e.g. \\server.domain.com\paws\workpapers
• In the Master Templates path, enter the new path to the templates folder, e.g. \\server.domain.com\paws\templates

 You can test the migration has been successful as follows: 

• Turn off the old server, to prove that the application can only be connecting to the new one
• Open PAWS and log in
• Open an audit that contains workpapers
• Click on the Work papers spine item
• Attempt to launch a workpaper.  Note that if you are doing this on a server where a workpaper's application is unlikely to be installed (e.g. Office or Acrobat) then the file can be copied via the right-click menu.  If the file copies successfully then this demonstrates that the workpapers share was configured correctly