Installing ManagePro 12.1 in Shared Database (Workgroup) Mode Overview 1 ManagePro 12.1 can be operated in Workgroup (also known as remote client ) mode where it accesses a shared SQL database in a LAN environment operating on a Windows-based LAN server. This document addresses the installation steps on the server and installing the client s (workgroup) machines. On the LAN server, smaller workgroups can use SQL Server 2008R2/2012 Express when it is installed and configured for remote access using a network protocol (e.g. TCP/IP). Although there is no set limit to the number of connections supported by the free SQL Server Express product, there are practical limits due to limitations imposed by Microsoft on memory usage. In general we would not recommend this approach for more than 5 users and the practical number may be less depending on factors such as database size. Bear in mind SQL Server Express is intended to be used as a Personal Server only. Larger, active workgroups (or workgroups with large databases) must use one of the full editions of SQL Server. Server Requirements: The following minimum requirements should be followed for best results: Ram 1. Windows 2008/2008R2/2012/2012R2 Operating System. 2. Dual Xeon CPU s or a single quad core CPU (min 1.9 mhz speed) for small groups, for larger groups, quad-core, dual cpu s are a better minimum - min 2.4 mhz speed 3. 8 gig of Memory is recommended (4 gig if using SQL Express) 4. 5 gig of Hard Drive space 5. Microsoft SQL Server 2008R2/2012 or Express 2008R2/2012 6. Server less than 50% operationally loaded with support of other tasks and applications before supporting ManagePro. 7. Individual PC workstations Windows 7, Window 8 and Windows 10 and for optimum speed 4 Gig of Installation Steps on the Server: Either SQL Server 2008R2/2012 or SQL Server 2008R2/2012 Express must be installed on the server and correctly setup for remote access. Setting up the server There are two approaches to setting up ManagePro on a work-group (LAN) server: 1. By far the easiest approach is to install the ManagePro 12.1 product on the server machine. a. If you intend to use SQL Server Express and it is not already installed you can use the ManagePro Full Installer to install SQL Server 2012 at the same time as ManagePro. This will create an instance of SQL Server named.\managepro, however you will need to enable the user sa with the default password of ManagePro1. b. If SQL Server (full or express) is already installed and configured on the server then use the ManagePro Upgrade Installer to install ManagePro.
Run the ManagePro Installer a. Choose install licensed copy 2 b. Choose ManagePro Standard Workgroup, click Next c. Click Next to accept the default Destination Folder C:\Program Files\Performance Solutions Technology. LLC\ManagePro or click change to specify another location and then click Next on this screen.
3 d. ManagePro Workgroup will install. Click Finish on the last screen ManagePro installation puts a shortcut on the desktop, before launching follow the steps below to set the remote client attribute. The remote client attribute allows remote access when set to true and when set to false disallows remote access and in this case allows you to create a database for workstations. c. Setting the remote client attribute: a. Once the installation is complete and before launching ManagePro, you must first set the remoteclient attribute to False found in the Mpro7init.xml file located at C:\Users\Public\Public Documents \ManagePro. b. Right-click on the Mpro7Init.xml file and choose open with Notepad and then change the remoteclient attribute to False, save the file. Doing so allows you to create a new database within ManagePro; otherwise the new database icon on the ManagePro Ribbon control will be disabled. d. License Key: In step 1b above, the Install licensed copy option was selected. Now, when you launch ManagePro, choose Enter License Code at the prompt and enter the software license key sent to you in an email. You will need a licensed copy of ManagePro on the server, because this will be the ONLY location that will allow you to create new databases, both during initial installation as well as in the future.
4 e. ManagePro Connection Properties: The first time you launch ManagePro, you will need to enter the parameters required to connect to SQL Server as a sysadmin. Fill in as shown below In the ManagePro Connection Properties window (see screenshot below). The highlighted name will be your computer name, the password is ManagePro1 (no quotes) or use your SQL Server specified sa password used during the set up when you installed SQL Server. a. If you used the Full Installer (in Step 1a) above which automatically installs the SQL Server Instance name called.\managepro, then launching Mpro the first time will display the login for the sample database b. The file locations (not shown below) will generally be automatically populated. c. Test your connection then Login f. Once in ManagePro, create a New Database and optionally restore a backup of your existing database for your workgroup.
a. To create a new database, click the New database icon in ManagePro 5 b. Name the database and then click OK c) The new database is created. This is the database the client machines (workgroup) will point to. You can now proceed with installing Mpro Workgroup on the Workstations (See Installing Clients) below, otherwise, if you are restoring an existing database, first create a new database as shown in the step above and then restore the database (see below). d) If you would like to restore an existing database, place a copy of your existing database i.e. yourdatabase.bak file in the C:\Users\Public\Public Documents\ManagePro\Backup folder and then in ManagePro click Utilities>Restore SQL Backup
6 e) Answer Yes to the prompt below f) Navigate to the C:\Users\Public\Public Documents\ManagePro\Backup folder and open your database g. Finally, you can now optionally adjust the security of the MproDirectory and ManagePro databases by creating a specific login and database users with access limited to these databases, this avoids having to expose the sysadmin login to Workgroup members (at time of writing the SQL Server login credentials used by workgroup clients are not encrypted). We recommend making the login the DB Owner. You are now ready to install and configure the workgroup clients 2. The second method is slightly more involved and requires that you create the ManagePro databases manually on the server, as opposed to installing ManagePro on the server - although it is possible to create them entirely from scratch this is not recommended, instead you will follow these steps: a. Assuming you have a server pc with SQL Server 2008R2/2012 (or Express) installed and correctly configured for remote access. b. Install ManagePro 12.1 on a workstation using the Desktop installation mode (you may already have this). c. Download and install (on the workstation) SQL Server Management Studio Express 2012: For 32 bit sql server: http://download.microsoft.com/download/8/d/d/8dd7bdba-cef7-4d8e-8c16- D9F69527F909/ENU/x86/SQLManagementStudio_x86_ENU.exe For 64 bit sql server: http://download.microsoft.com/download/8/d/d/8dd7bdba-cef7-4d8e-8c16- D9F69527F909/ENU/x64/SQLManagementStudio_x64_ENU.exe d. Identify the ManagePro database(s) you intend to host on the server then backup both the MproDirectory database and the selected ManagePro database(s).
e. On the server, create a database named MproDirectory and restore the backup into it using the appropriate options. If you intend to use SQL Server authentication then create a SQL login and user as dbowner for this database otherwise ensure the workgroup users will have at least datareader and datawriter access. 7 f. On the server, create the ManagePro database(s) you will be hosting and restore them from their respective backups. Again setup access control either via SQL Server authentication or Windows Authentication, users will require sufficient permissions to allow read, write and schema changes (for upgrades), we recommend dbowner. g. You are now ready to install and configure the workgroup clients. Installing the Clients (Workstations) Privileges: Users running the ManagePro Installer on Workstations must have adequate privileges to install software. The machine user must have at least modify permissions on the ManagePro folder as well as the HTTPTemp and DocTemp folders found at: Windows 7/8/10: C:\Users\Public\Public Documents\ManagePro Each machine in the workgroup will require ManagePro 12.1 installed in WorkGroup mode. a. Run the installer provided by Performance Solutions Technology b. Choose Install licensed copy of MangaePro during the install set-up c. Select ManagePro Workgroup on the ManagePro Product Type page, click Next then click Finished on the last page of the install set-up.
8 d. The first time ManagePro is run it will prompt for SQL Login information, fill in the login dialog with the appropriate credentials (your server and SQL Server Instance) and you should now be able to login to the ManagePro database(s) on your server. Example: The file locations on the workstations can be left blank. Click Test connection. If successful, the login screen will be displayed. If your connection is not successful, please be sure you have entered the correct SQL Server Connection setting to connect to the database which resides on your server. Select your initials for the Login screen dropdown
9 Multiple Databases: If you have created multiple databases on the server, click Cancel at the login screen and choose the database you would like to start from the Open ManagePro Database window and select the database you want to run. Click Login one at the login window for that database. Limitations Currently there are several limitations when operating ManagePro 12.1 in Workgroup mode, when you install ManagePro in this mode the following functions are disabled at the local pc and must be performed at the server: Create Database, Backup Database, Restore Database These functions all require SQL Server to have physical access to local files so they need to be run on the server itself. Generally, these functions are not required once ManagePro has been installed and configured (Backup and Restore can be handled at the server using ManagePro or SQL Management Studio or Maintenance Plans). Throughput, as defined by ability to access memory, of the SQL license chosen. Note the amount of memory the various licenses listed below support. One can expect each to support up to some preferred limit of concurrent users, which means users accessing the SQL database at the same time without experiencing undue delays. SQL License type Memory Accessed Cost Anticipated max of concurrent users MS SQL Express 1 GB Free 4-5 MS SQL Workgroup 2 GB $700 - $3500 15-30 MS SQL Standard Up to OS Max $2000 - $4700 30 and up
These are only estimates and you may have better performance (or less) than what is listed above. Every server and organization is different. The work load of your users will greatly impact your performance. The amount of RAM and the database size also come into play. If you are running a Windows Enterprise Server with SQL Standard, with 8GB of RAM and a 2GB database, SQL will keep the database up in RAM to facilitate faster read times, but if the database size exceeds the amount of RAM SQL is constantly having to go to the hard drive for the information. 10 For further assistance, please contact pst@managepro.com or call 707.487.3000. Document created by Performance Solutions Technology, LLC Web http://www.managepro.com