1. MaxExchange Install and Configuration

2. Background Information  Major changes to MaxExchange for SQL versions:  Switch to SQL Server Express database engine  Support for the Administrator Role  Support for synchronization of multiple Address Books from a single MaxExchange Server  Support for Windows Authentication mode and Single Sign On (SSO)  Support for mixed mode upgrade

3. General Changes  Sending of Remote packet, purging of Backup folder, and updating of the last processed date field during each remote processing cycle.  Packet size to exact standards, no over sizing.  Refresh purges all outbox packets eliminating packet redundancy and saving download time.  Configuration moved from Registry to the MACONFIG table

4. General Changes  Support for Remotes to connect to synchronize to more then one database  Support to suspend synchronization of a Remote  SPDM logs are now named after the database Database_name_log to accommodate multiple database synch

5. SQL Server Express  The Application Server installation will always install an instance of SQL Express called \Maximizer  During the Application Server install the users selects the SQL installation that will house the Maximizer database, you are not forced to use SQL Express.

6. Confidential Information SQL Server/Express

7. Incoming Packet Processing in SQL

8. Outgoing Packet Creation using SQL  Packet files are now created using SQL BCP  A single packet is first created in the outbox.  When the packet is complete it is compressed, encrypted and separated into sub-packets to the exact size specification as set in the remote’s configuration.  The packet in the backup folder is the full size of the main packet, there is no breaking the packet into smaller sub packets in the backup folder.

9. Outbox Processing Activity  There is little indication of processing and packet creation during processing in the outbox.  A single packet is first created as data and is loaded from the database (Using BCP from SQL)  A single Mex files protects the packet file as data is loaded.  Click F5 to see the packet grow in size as the data is loaded

10. Outbox Processing Activity (cont’d)

11.  Once the transactions are loaded from the database into the single packet compression takes place.  Packet compression at this time is about 1/3 the size of the original file

12. Outbox Processing Activity (cont’d)  After compression encryption is applied  The packet remains the same size after encryption

13. Outbox Processing Activity (cont’d)  Completion of encryption leaves a single compressed encrypted packet and HDR file.

14. Outbox Processing Activity (cont’d)  If a packet size has been set for a remote the single packet spawns sub packet using its packet number followed by an _ and then a sequential number 1209_1 1209_2

15. Outbox Processing Complete  The packet/s are moved to the transport folder and the single large packet is moved to the backup folder

16. Major Features  Change MaxExchange REM file from Pervasive to SQL Server Express  MXZREM.MAX now MXZREM.BIN

17. Administrator Role  Support Multi DB Sign-on and Administrator Role

18. Multiple Address Books on one MaxExchange Server Step 1: From the file menu Select Open Address Book or Add Address book

19. Step 2: Select the Address Book to open Step 3: Select the SQL Server & log in Adding Multiple Address Books (cont’d)

20. Step 4: Log into the database & select the MaxExchange Server

21. Step 5: Click on an Address Book to display Settings, Teams, and Remote Users Adding Multiple Address Books (cont’d)

22. Multiple Address Books Address Book Properties in Site Manager Shows the assigned MaxExchange Server machine

23. Windows Authentication Mode

24. Staged Version Upgrade  One point of resistance to upgrade is the difficulty in shutting down the entire MaxExchange system to upgrade remote users.  MaxExchange 10 does the best job yet in allowing backwards compatibility synchronization.  This allows a staged approach for upgrading groups of remote users a few at a time while the system remains operational.

25. Staged Version Upgrade (cont’d)  Data for Remotes that have not been upgraded remain on the server in an Upgrade folder until the remote is upgraded to Maximizer CRM 11.  However incoming data from the remote is processed normally at the server

26. Staged Version Upgrade (cont’d)  After upgrade the remote must be manually updated to allow the normal flow of data and the movement of data from the Upgrade folder

27. MaxExchange Other Features

28. Auto send Remote packet during ALL processing cycles  Purges the Backup folder and updates the last processed date field  Resolves issues to do with space on the server taken up by old data in the backup folder  Allows Administrators to know who is truly synchronizing or not  Allows Administrators to take advantage of the Event Notifications for remote users out of synchronization

29. Auto send Remote packet during ALL processing cycles

30. Packet size to exact standards - no over sizing  Resolves issues around ISP and other download file size restrictions  All packets are exactly the size as set in the Remote Site properties

31. Packet size to exact standards - no over sizing

32. Refresh purges all outbox packets  Eliminates packet redundancy and saving download time  A Refresh contains all data

33. The current number of Registry values is much smaller then in past versions. This is a sample of a version 10 MaxExchange Registry The current number of Registry values is much smaller then in past versions. This is a sample of a version 10 MaxExchange Registry Configuration moved from Registry to MACONFIG

34. Configuration moved from Registry to MACONFIG (cont’d)  Current addition to the MACONFIG table for non-database specific settings for MaxExchange

35. Configuration moved from Registry to MACONFIG (cont’d)

36. Remotes to synchronize to more then one database  In the past there were restrictions when a Remote synchronized multiple databases - the FTP passwords had to be the same on both servers.  Now a remote can synchronize to multiple databases on one or more servers.

37. Suspend synchronization of a Remote  Suspend the remote when users are unavailable for long periods of time  Upon return, the removal of this check will send the remote a refresh  This allows administrators to keep teams and team members properly configured by not having to delete remotes that are unavailable for long periods then add them back in and rebuild the team member synchronization

38. SPDM logs are now named after the database  SPDM logs are now named after the database, Database_name_log to accommodate multiple database synch

39. Common Issue Combining MaxExchange Servers to one  Remove all address books that are moving from site manager  Add each address book back, specifying the new server  Address book selected during installation stored in MaConfig  If uninstalling and reinstalling, not asked for address book again (once Maconfig is established, no further prompts)  To remove address book from synch, remove from Site Manager