Billing Server Security Updates and Patching Best Practice

Summary

This article describes the best and safe practices for updating your EngageIP Billing server or SQL server.

Required Patches May Include

• EngageIP Billing Upgrade

• Windows Server Updates

• Windows Service Packs

• MSSQL Security patches, service packs

• Third party software updates / upgrades

Recommended Process when Updating Servers where EngageIP is Installed

1. Backup working files OFF the existing servers (this may be on a backup hard drive, SAN, or other network backup medium)

2. Backup Databases for EngageIP and any other critical databases

3. Backup the EngageIP installation folder which contacts the AdminPortal files

4. Review release notes for the updates you're installing to confirm there are no known issues with the software currently installed on the system. A complete search of Microsoft's website for compatibility of software and updates is recommended

5. Once all backups are complete, install the update or patch

6. Restart all services, in many cases a full Server reboot is best

7. When rebooting, first reboot MSSQL server, then reboot IIS server so that MSSQL is ready when IIS tries to access it

8. If there are any other updates, install them as necessary

9. Confirm all critical tasks are still functioning after the servers have been rebooted. The list includes but is not limited to the bulleted list below:

   • Ensuring the AdminPortal is accessible

   • Ensuring any customer portals/external sites that integrate with EngageIP are functioning as expected

   • Ensuring payment processing is working in EngageIP (credit card, echeck, etc.) and/or in web portals that allow payments to be made by account holders

   • Ensuring sales/other agents are able to login and execute their normal tasks

   • Checking the Windows and EngageIP Event Logs for errors

   • Any other critical functions and EngageIP features that you use are functioning normally