Migrate From Version 3.1 to Version 4 Guide Vovici Enterprise 4.0. December PDF Free Download

Migrate From Version 3.1 to Version 4 Guide Vovici Enterprise 4.0 December 2008

For installation support, please contact our Vovici installation experts at installefmc@vovici.com. If phone support is requested an installation expert will call the phone number requested. Or visit: www.vovici.com Please contact Vovici Technical Support if you believe any of the information shown here is incorrect. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of the Vovici Corporation. Copyright 2008 Vovici Corporation. All Rights Reserved. All other company and product names are trademarks or registered trademarks of their respective holders. Printed in the United States of America v. 4.00.02 Page 2 of 38

Table of Contents Migration from EFM Community 3.1 to Vovici Enterprise 4.0...5 Requirements... 5 Things to Note:... 5 A. Download new Vovici Enterprise version 4.0 file... 7 B. Running the installer... 8 C. Options.lic file... 16 D. Authentication and Permissions... 17 Windows 2003 Server permissions...17 Vovici Authentication...18 Vovici Authentication Permissions... 19 I. Windows NTFS Permissions... 20 II. Setting Windows Permissions... 21 III. IIS Permissions... 21 IV. Determining the Application Pool used by Vovici Enterprise... 22 V. Determining the account that runs the Application Pool... 22 VI. Determining the account that the web server runs as in IIS... 22 VII. Determining the account that the Vovici Service runs as... 23 Windows Authentication...24 Edit the Web.Config File for Windows Authentication... 24 Windows Authentication Permissions... 25 I. Windows (NTFS) Permissions... 26 II. Setting Windows Permissions... 27 III. IIS Permissions... 27 IV. Determining the Application Pool used by Vovici Enterprise... 28 V. Determining the account that runs the Application Pool... 28 VI. Determining the account that the Vovici Service runs as... 28 E. Run Table Setup... 29 Access Administrative Portal...29 Update the Database to Version 4.0...31 F. Configure and Test Workgroups... 32 H. Test Environment... 33 Appendix:...35 1. Determining the web server root in Microsoft IIS:... 35 2. ASP.NET Framework... 36 3. Knowledge Base... 37 4. Administrative Portal Guide... 38 Page 3 of 38

Page 4 of 38

Migration from EFM Community 3.1 to Vovici Enterprise 4.0 Requirements 1. EFM Community version 3.1 should already be installed on the application server and working. Vovici Enterprise version 4.0 can only upgrade the database structure of EFM Community 3.1. Performing a migration from a previous version such as version 3.0, will lead to problems. 2. Windows 2000 and Microsoft SQL Server 2000 are no longer supported with Vovici Enterprise version 4.0. These must be upgraded to Windows 2003 and Microsoft SQL Server 2005, respectively, in order for Vovici Enterprise version 4.0 to function. Oracle requirements have not changed. 3. ASP.NET 2.0 Framework needs to be installed. Microsoft.NET Framework (version 2.0.50727. EFM Community version 2.2 and earlier used version 1.1 of the.net Framework) Available at : http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-4b0d-8edd-aab15c5e04f5 Note: On Windows 2003 ASP.NET 2.0 must be set to Allow under the Web Service Extensions in Microsoft IIS in order for Vovici Enterprise to function properly. Follow the steps below to achieve this: 1. Open Microsoft IIS 2. Click Web Service Extensions 3. Highlight ASP.NET 2.0 4. Click Allow 4. The following backups must be done before the migration process is started: The physical directory where EFM Community 3.1 is installed. Typically this is located at: C:\Inetpub\wwwroot\Vovici The existing database used by the application. Things to Note: 1. The migration to version 4.0 can only be done from version 3.1. You must first update or migrate from earlier versions to version 3.1 before the migration can begin. Please see the URL below for documentation on how to do so: Update from version 2.0 or 2.1 to 2.2: http://vovici.com/downloads/commhelp/2_2/efm_c_upgrade_2_x_to_2_2_gde.pdf Page 5 of 38

Migrate from version 1.45 to 2.2: http://vovici.com/downloads/commhelp/2_2/ss_efm_migration_to_efm_c_2_x.pdf Migrate from version 2.2 to 3.1: http://vovici.com/downloads/commhelp/3_1/efmc_migration_to_efmc_v3_10.pdf Update from version 3.0 to 3.1: http://vovici.com/downloads/commhelp/3_1/efmc_upgrade_3x_to_3_1_guide.pdf 2. Existing version 3.1 survey URLs will not change. Note: This was not the case between version 1.45 and 2.x as a new survey processor was introduced that changed the way URLs were built and accessed. 3. Version 4.0 will continue to use the Survey Engine of 2.x and 3.x with some updated code to support version 4.0 s new features. 4. Survey HTML will not be republished. So no custom edits of the HTML will be lost. 5. There were no major fundamental changes to the data structure like there was in versions 2.x and version 3.1. This greatly speeds the migration process from previous migrations. 6. New indexing was added in version 4.0 to speed exports and imports of the application. 7. Exports are now pushed to a background process and will be emailed to the application user once it is completed. This was added as speed enhancement to the application. 8. The Active X control for the Free Form Word Processor from version 3.1 was not changed. So a new version does not need to be installed for version 4.0. 9. Like version 3.1, Vovici Enterprise version 4.0 s installer does not have apply file permissions so often permissions need to be applied manually per Section D of this document. 10. The existing version 3.1 installer should not be uninstalled. The version 4.0 installer will over install the application. 11. Web Services no longer has a separate installer. The license file (options.lic) provided by installefmc@vovici.com enables this functionality. Page 6 of 38

A. Download new Vovici Enterprise version 4.0 file To being the installation process, please perform the following steps: 1. In a web browser, navigate to the following URL: http://vovici.com/downloads/comm/4_0/vovici_ent_4_0.htm 2. Click Save (Steps 3, 4, and 5 refer specifically to Microsoft Internet Explorer and may be different on other browsers.) 3. Choose a local directory to save the installer in. Make a note of this directory. 4. Click Save to begin downloading the installer. Once the download is complete, proceed to the next section. Note: Our technicians will prove invaluable in assisting the server configuration and Vovici Enterprise installation. Please contact them at installefmc@vovici.com for assistance downloading and installing Vovici Enterprise. Page 7 of 38

B. Running the installer Once the installer has been downloaded, locate the file and follow the steps below to unzip it and begin the installation. 1. Double click on the installer file. Note: The following warning message may appear: Click Run to proceed. 2. This will launch the Windows installer and the following start message will appear: Page 8 of 38

Note: The version of the Vovici Enterprise installer can be found by following the steps below. a. Right click on the file and click Properties b. Click Summary c. The version number is in the Comments field This is the version of the installer not the application itself and can help our Installation Specialists and/or Technical Support staff discover which version of the software is being installed. Note: Click Cancel at any time to stop the installation. 3. Click Next 4. This will display the License Agreement page. Page 9 of 38

Please read the license agreement and if it is acceptable, select the I accept the terms in the License Agreement option. 5. Click Next. 6. The Vovici V4 Setup page will appear: Page 10 of 38

In the Select the web site the application should be installed on dropdown select the web site where the application is currently installed. 7. Enter the name currently used for the virtual directory inside Microsoft IIS for EFM Community 3.1 in the: This name will be part of the application URL box The default value is: Community So the URL to access the main application will be: http://servername/community Note: Older clients who started with EFM Community version 2.2 or earlier most likely have the value perseus instead of Community. The old value of perseus could be used for the virtual directory. This will keep existing survey URLs the same. Otherwise in order for old URLs to work a re-direct on the perseus virtual directory pointing to the new Community virtual directory will be needed. This re-direct will not work with Workgroup Community and External Email List surveys. If this redirect is not done a re-publish of the survey inside the main application, once the migration is completed, will change the URL used to access the survey. The survey will now use the new URL path (with Community) to access the survey. It is recommended that the old value of perseus be kept. Page 11 of 38

So the URL to access the main application will be: http://servername/perseus Note: Ensure that the virtual directory name selected is not already in use by another application as a web site name or virtual directory name on the server. 8. Click Next. 9. The Custom Setup page will appear. Multiple options can be selected on this page. On the top part of the window there is an option named Complete with a + next to it. Click the + sign to expose the following two components (Both of these options are installed by default): Vovici v4 This determines the installation options for the main application Vovici Service Determines the installation options for the Vovici Service that controls the scheduling feature within the main application. Note: The Vovici Service will be installed by default. It provides time-based services to users such as deployment of invitations, opening and closing of surveys, etc. It is highly recommended that the Vovici Service is installed because certain functions require this service to work properly. o Installing the service on multiple servers that are in a single web farm may result in duplicate invitations being sent. Although if the Vovici Service is disabled on all but one server this will prevent any duplicate invitations from being sent. This solution allows for a quick failover if the server running the Page 12 of 38

Service goes down: simply enable the Vovici Service on one of the other servers and it will restore the functionality without the need of locating the installer and re-running it to install the service on another server. o Please contact our Installation Specialists for other information regarding the migration of Vovici v4 on a web farm. Note: In order to use the same physical directory as before Browse must be clicked and the path specified otherwise the default value is: C:/inetpub/wwwroot/vovici If the default value is used for older clients who started with EFM Community version 2.2 or earlier the following subdirectories must be copied from the backup of the Perseus Virtual Directory into the new vovici physical directory. \AppData \surveys \reports This needs to be before done proceeding to the next step. Selecting the text for either installation component will display how much disk space is taken up by it. 10. To toggle whether to install one component or the other click the icon ( ) next to its name. Select the X icon to choose not to install the component. The following buttons (other than the three navigation buttons, Back, Next and Cancel) are available on this page: Reset Used to return all options to the original default states. Disk Usage Click to open a page that displays the following information about every drive partition either physically connected to the computer and/or mapped over a network: Disk Size The total available disk space Available The amount of free space available Required How much disk space will be taken by the application 11. Once all desired options have been configured click Next 12. The Vovici V4 window will appear: Page 13 of 38

Click Upgrade in order for the installer to update the older version 3.1 files to version 4.0. 13. The ready to install Vovici v4 upgrade window will appear. Page 14 of 38

Click Install to start the installation of selected components. 14. Click Finish after installation is complete. 15. If prompted, please restart before continuing this installation procedure or Vovici Enterprise v4 will not function correctly. Page 15 of 38

C. Options.lic file This file should be provided by the Vovici installation experts called options.lic. This file needs to be copied into the following directory before proceeding: Drive Letter:\pathto\Vovici\AppData The path for Drive Letter:\pathto\ should be the path to the root of the web site specified in Step 9 above. This is the license file for the application and is needed in order to access the application. It also controls which add-ons to the product that were purchased are accessible. Page 16 of 38

D. Authentication and Permissions Once the machine has been restarted (assuming it was needed) the authentication mode to use to allow access to the application must be decided and configured inside IIS. Windows 2003 Server permissions Vovici Enterprise has two authentication modes: 1. Vovici authentication The authentication process is handled by Vovici Enterprise via users added under Manage Users in the Administrative Portal (or under Administration Users inside the main application). Using this authentication method, when the main application URL (for example: http://servername/community/login.aspx) is accessed the Vovici Enterprise login prompt will appear. 2. Windows authentication IIS handles the authentication of the user. Vovici Enterprise only verifies that the Windows account used to log into the computer itself was added to the list of authorized users under Manage Users in the Administrative Portal (or under Administration Users inside the main application). No login screen to the application is displayed to the user. Each of the two authentication modes has a different set of permissions which must be allowed in order for Vovici Enterprise to function correctly. Both authentication modes still require the users to be added within Administrative Portal - Manage Users or within the application itself under Group Administration Manage Users. These two authentication modes are displayed in more detail below: Page 17 of 38

Vovici Authentication Anonymous access must be enabled inside IIS in order for Vovici Authentication to function correctly. Note: Integrated Windows authentication must be disabled inside IIS in order to attempt to login into Vovici Enterprise using Vovici Authentication. To Enable "Anonymous access" and disable "Integrated Windows authentication" in Microsoft IIS follow the steps below: 1. Open Microsoft IIS 2. Right click the Community Virtual Directory 3. Select Properties 4. Click the Directory Security tab 5. Click Edit 6. Select (to enable) Anonymous access 7. Deselect (to disable) Integrated Windows authentication 8. Click OK twice Page 18 of 38

Vovici Authentication Permissions The following permissions must be assigned after the Vovici Enterprise version 4.0 installer has been run in order for Vovici Authentication to function. Note: Most of the permissions listed below are requirements of the Windows Operating System, the Microsoft IIS web server and Microsoft ASP.NET 2.0. They are listed for your reference to speed the installation process and to aid troubleshooting. Vovici is not responsible for any of the permissions assigned. Vovici does not require any of the accounts listed below. The accounts listed in most cases can be replaced with another account to align with the organization s security standards, but whatever account is used must have these minimum permissions in order for the application to function properly. To change an account being used, follow the instructions in the sections labeled Determining the account list at the bottom of the Windows NTFS permissions chart. The Vovici Enterprise installer does not attempt to assign permissions due to security limitations encountered in most environments. Instead they must be applied manually in order for the application to function with Microsoft IIS and Microsoft ASP.NET 2.0 in a Windows environment. Page 19 of 38

I. Windows NTFS Permissions Network IIS_WPG# Service* Community Virtual Read Read Directory List List Read and Execute AppData Full Control Read List Surveys Full Control Read List Vovici Service** None None Read List Write (Modify) None Reports Full Control Read List Temporary Full Control N/A N/A ASP.NET Files## C:\Program Files\Vovici\Service Windows Temp Dir### None None Read List Read and Execute None Read List Write None * - See the section regarding Determining the account running the default Application Pool. Note: Microsoft IIS requires accounts used to run an Application Pool to be a member of the IIS_WPG group on the local server. Otherwise it cannot start the Application Pool inside IIS. # - See the section regarding Determining the account that the web server runs as in IIS. ** See the section regarding Determining the account that the Vovici Service runs as (On some servers Modify permissions might be needed for the Vovici Service to function properly) ## - This is a Microsoft.NET Framework created directory and whatever account runs the Application Pool needs to have access to it. Otherwise.NET applications will not function. ### - This directory is a Windows environment setting. (This permission is a.net requirement) The default value is: C:/Windows/Temp, but this can be verified under, Control Panel System Advanced inside the Environment Variables tab under System Variables : it will be the TEMP variable. Page 20 of 38

II. Setting Windows Permissions This section is not meant to replace Windows documentation but is intended as reference to people not familiar with applying Windows NTFS permissions. 1. Open either Windows Explorer or the My Computer icon Note: Microsoft IIS 6.0 supports the ability to right click on virtual directories or subfolders in order to apply Windows NTFS permissions. 2. Locate the directory in question 3. Right click on it 4. Select Properties 5. Click Security 6. Use the Add button to add accounts not listed 7. Click on an existing account to see the currently permissions allowed and to change them by clicking Allow Note: It is advisable to verify that permissions have propagated down to files inside each of these directories for each account. In some cases child objects (files inside directories) are not allowed to receive permissions from the parent objects (directories). In order to force this propagation inside the Security tab click Advanced and select the bottom checkbox. This will force the permissions to all child objects under the directory in question. Vovici installation experts have on occasion only seen this work to the next layer of folders. For example: Permissions set up the /vovici directory are only applied to the: /vovici/appdata directory But permissions will not always be applied to: /vovici/appdata/admin directory III. IIS Permissions Community Virtual Directory AppData Surveys Reports Permissions Read Read Write Read Write Read Write Page 21 of 38

IV. Determining the Application Pool used by Vovici Enterprise By default Vovici Enterprise is run by the default Application Pool but this varies. Please use the information listed above to determine the exact Application Pool. 1. Open Microsoft IIS 2. Select the web site that is being used to host Vovici Enterprise 3. Right click the Community Virtual Directory folder (specified during the original installation, sometimes called Perseus) 4. Select Properties 5. Select the Virtual Directory tab 6. Record the Application Pool setting at the bottom of the page. V. Determining the account that runs the Application Pool In IIS 6.0 the Account that the default Application Pool runs as is typically Network Service. The account actually used can be verified by doing the following: 1. Open Microsoft IIS 2. Click the + next to Application Pools 3. Right click Default Application Pool 4. Select Properties 5. Select the Identify Tab 6. Record the username that is specified. This is the account that needs the permissions labeled for the Network Service account in the Windows Permissions column. VI. Determining the account that the web server runs as in IIS In IIS the Account that the Web Server runs as is typically IUSR_machinename or the IWAM_machinename account. This can be checked by doing the following: 1. Open Microsoft IIS 2. Right click the web site that is being used to host Vovici Enterprise 3. Select Properties 4. Select the Directory Security Tab 5. Under Anonymous access and authentication control click Edit Note: Please verify the username that is specified. If IUSR_machinename is listed sometimes this is not used when Vovici Enterprise is used, instead the IWAM_machinename account will be used by IIS. On Windows 2003 Server the IIS_WPG account is used in most scenarios instead of either of these accounts. Both the IUSR and IWAM local machine accounts are included in the IIS_WPG account by Windows. Page 22 of 38

VII. Determining the account that the Vovici Service runs as The Vovici Service used by Vovici Enterprise performs all the scheduled functions within the Schedule Events section of the main application. The only exception is if the Now lightning bolt icon is clicked under List view inside Schedule Events. This can be checked by doing the following: 1. Inside the Control Panel open Administrative Tools 2. Double-click (open) Services 3. Look for the Vovici Service, it is typically named Vovici Service and right click it 4. Select Properties 5. Select the Login Tab Note: Please record the username that is specified. This account needs the permissions specified under the column Vovici Services in order to open and close surveys. The account listed here must have the ability to start services on the local server otherwise the Vovici Service cannot be started. Page 23 of 38

Windows Authentication Integrated Windows authentication must be enabled inside Microsoft IIS in order to attempt to login into Vovici Enterprise using Windows Authentication. The web.config file also needs to be edited in order to support this authentication method. Edit the Web.Config File for Windows Authentication Inside the vovici root directory the web.config file must be found (this path was specified when the installer was run earlier in the process). The following line needs to be changed: <authentication mode="none" /> To: <authentication mode="windows" /> Note: Anonymous access must be disabled in order for Windows Authentication to function correctly. To Enable "Integrated Windows authentication" and disable "Anonymous access" in IIS follow the steps below: 1. Open IIS 2. Right click the Community Virtual Directory 1. Select Properties 2. Click the Directory Security tab 3. Click Edit 4. De-select (to disable) Anonymous access 5. Select (to enable) Integrated Windows authentication 6. Click OK twice Note: Some networks require that Digest Authentication for Windows domain servers be checked in order for users to have access to all features within Vovici Enterprise. Page 24 of 38

Windows Authentication Permissions The following permissions must be assigned after the Vovici Enterprise 4.0 installer has been run in order for Vovici Authentication to function. Note: Most of the permissions listed below are requirements of the Windows Operating System, the Microsoft IIS web server and Microsoft ASP.NET 2.0. They are listed for your reference to speed the installation process and to aid troubleshooting. Vovici is not responsible for any of the permissions assigned. Vovici does not require any of the accounts listed below. The accounts listed in most cases can be replaced with another account to align with the organization s security standards, but whatever account is used must have these minimum permissions in order for the application to function properly. To change an account being used, follow the instructions in the sections labeled Determining the account list at the bottom of the Windows NTFS permissions chart. The Vovici Enterprise installer does not attempt to assign permissions due to security limitations encountered in most environments. Instead they must be applied manually in order for the application to function with Microsoft IIS and Microsoft ASP.NET 2.0 in a Windows environment. Page 25 of 38

I. Windows (NTFS) Permissions Network Service* Windows User Accounts# Community Virtual Read Read Directory List List Read and Execute AppData Full Control Read List Surveys Full Control Read List Vovici Service** None None Read List Write (Modify) None Reports Full Control Read List Temporary Full Control N/A N/A ASP.NET Files## C:\Program Files\Vovici\Service Windows Temp Dir### None None Read List Read and Execute None Read List Write None * - See the section regarding Determining the account running the default Application Pool. # - In certain IIS configurations (for example when Impersonation is enabled) all the domain users that will access Vovici Enterprise will need these permissions in order to access the product correctly. ## - This is a Microsoft.NET Framework created directory and whatever account runs the Application Pool needs to have access to it. Otherwise.NET applications will not function. ### - This directory is a Windows environment setting. (This permission is a.net requirement) The default value is: C:/Windows/Temp, but this can be verified under, Control Panel System Advanced inside the Environment Variables tab under System Variables : it will be the TEMP variable. Note: In some cases Write and Modify permissions might need to be assigned to these users over the AppData, Surveys and Reports subdirectories. It is recommended that a group be created containing all these users under Control Panels Administrative Tools Computer Management Local Users and Groups. This will make assigning the permissions in Windows easier, but the group must be maintained every time a new user is added. ** See the section regarding Determining the account that the Vovici Service runs as (On some servers Modify permissions might be needed for the Vovici Service to function properly) Page 26 of 38

IV. Determining the Application Pool used by Vovici Enterprise By default Vovici Enterprise is run by the default Application Pool but this varies. Please use the information listed above to determine the exact Application Pool. 1. Open Microsoft IIS 2. Select the web site that is being used to host Vovici Enterprise 3. Right click the Community Virtual Directory folder (specified during the original installation, sometimes called Perseus) 4. Select Properties 5. Select the Virtual Directory tab 6. Record the Application Pool setting at the bottom of the page. V. Determining the account that runs the Application Pool In IIS 6.0 the Account that the default Application Pool runs as is typically Network Service. This can be verified by doing the following: 1. Open Microsoft IIS 2. Click the + next to Application Pools 3. Right click Default Application Pool 4. Select Properties 5. Select the Identify Tab 6. Record the username that is specified. This is the account that needs the permissions labeled for the Network Service account in the Windows Permissions column. VI. Determining the account that the Vovici Service runs as The Vovici Service used by Vovici Enterprise performs all the scheduled functions within the Schedule Events section of the main application. The only exception is if the Now lightning bolt icon is clicked under List view inside Schedule Events. This can be checked by doing the following: 1. Inside the Control Panel open Administrative Tools 2. Double-click (open) Services 3. Look for the Vovici Service, it is typically named Vovici Service and right click it 4. Select Properties 5. Select the Login Tab Note: Please record the username that is specified. This account needs the permissions specified under the column Vovici Services in order to open and close surveys. Page 28 of 38

E. Run Table Setup The migration of the database structure from version 3.1 to version 4.0 will be handled via the Administrative Portal (Almost all the changes are new tables being added to support new functionality). No external utility will be needed outside the basic installer for Vovici Enterprise 4.0 which should already be installed. Access Administrative Portal This section explains how to enter the URL in a web browser to access the Vovici Enterprise Administrative Portal. Note: Internet Explorer 6.0 or 7.0 is required to access the Vovici Enterprise Administrative Portal. Depending on the authentication method designated in Section D access to the Vovici Enterprise Administration Portal will be different: Vovici Authentication The first time the Vovici Enterprise installer is run it is required that access be made on the server that Vovici Enterprise is installed on or by remotely connecting to it. The Administrative Portal will be accessed through the following URL: http://localhost/community/admin/default.aspx Note: If a virtual directory other than community was used in Section B, Step 7 above, replace community in the URL with the name of the virtual directory used. Attempting to access this URL from a different computer by changing localhost to the server s name or IP will fail on all initial installations performed until the administrator account is enabled inside the Vovici Enterprise Administrative Portal. This is by design and is intended as an extra security feature. Using Localhost on a Web Server Hosting Multiple Web Site In a web server hosting multiple web sites, in order to use localhost as a URL for a specific web site, a unique port needs to be assigned for localhost for that web site. The steps below explain how to do this. This example assumes the port will be 8080, but any viable port that Microsoft IIS supports and is not currently in use will work. 1. Open Microsoft IIS 2. Right click the web site that is being used to host Vovici Enterprise 3. Select Properties 4. Select the Web Site Tab 5. Click Advanced 6. Click Add 7. Leave the IP Address (All Unassigned) 8. Enter 8080 for the TCP Port 9. In the Host Header Name enter localhost 10.Click OK Page 29 of 38

After the initial setup is configured usage of the administrator account to access the Vovici Enterprise Administrative Portal remotely will be enabled. Windows Authentication If Windows Authentication was chosen access can be from any machine but the login to the machine will need to be a local system administrator (Not a Domain Administrator) on the EFM host application server. The Administrative Portal will be accessed through the following URL: http://server/community/admin/default.aspx Or via the server either locally or by remotely connecting to it: http://localhost/community/admin/default.aspx Note: If a virtual directory other than community was used in Section B, Step 7 above; replace community in the URL with the name of the virtual directory used. Attempting to access this URL from a different computer by changing localhost to the server s name or IP will fail on all initial installations performed after EFM Community version 2.1 Build 901 or later (earlier versions/builds did not have the ability for remote access) until the administrator account is enabled inside the Vovici Enterprise Administrative Portal. This is by design and is intended as an extra security feature. Page 30 of 38

Update the Database to Version 4.0 Follow the steps below to upgrade the existing version 3.1 database structure to version 4.0. Note: This must be done before logging into the main part of application. 1. Click Configure 2. Under Connections 3. Click Run Table Setup Note: This will create the new tables and modify existing tables to accept the version 4.0 formatting. Page 31 of 38

F. Configure and Test Workgroups This section tests the publishing paths and email connection to the SMTP Server work within the application. 1. Access the Vovici Enterprise Administrative Portal using the information presented in Section E. 2. Click Workgroups 3. Select the first Workgroup in the list 4. Click Edit 5. Click Publishing and make sure the information under the tab is correct. 6. Click Test 7. The following message should be displayed: 8. Click Mail and make sure the information under the tab is correct. 9. Click Test 10. Click Workgroups 11. Select the next Workgroup in the list 12. Repeat steps 4 through 11 until all workgroups have been configured. Page 32 of 38

H. Test Environment The migration process is complete and testing can be performed. Below is a recommendation of testing that can be done to insure the migration was a success: Test existing surveys (Under Surveys in the main application attempt to access existing surveys from the list) 1. Check published URLs and see if the surveys can be accessed via a web browser. Note: Some survey types require this be tested in Preview from Write Invitations. 2. Click Manage Responses o Make sure all responses are visible o Test an export and see if the correct number of responses are displayed Note: All three of the following response counts should match: Data number of responses in the Data section on the survey s home pane Manage Responses The number of records displayed inside Manage Responses: please make sure that no filter is applied Export within Manage Responses How many records are exported: please make sure that either Manage Responses has no filter applied or the export is done using the No Filter option, as this will often lower the number of exported records. 3. Click Manage Reports o Attempt to create some reports Attempt to create a new survey 1. Create a test survey via Surveys Create New Survey (Select External Email List as the Respondent Source.) 2. Test publishing by clicking Publish under the Actions Bar. 3. Click Select Participants and under the Actions Menu select Add Participant 4. Enter an e-mail address in the e-mail field and click OK. 5. Inside Write Invitations enter a Subject place the cursor inside the body of the invite and under the Fields box click Survey URL. 6. Inside Schedule Events (formerly Deploy Survey) and under the New Menu select Open Survey. 7. Set the Start time to the next half hour time period (Either the top of the hour such as 1:00 or the bottom of the hour 1:30). 8. Set no Recurrence or Advanced options and click OK. 9. Under the New Menu select Send Initial Invitation 10.Set the Start time to the next half hour time period after the Open Survey event was scheduled (Either the top of the hour such as 1:00 or the bottom of the hour 1:30). 11.Set no Recurrence or Advanced options and click OK. 12.Check the survey after both time periods entered to confirm that the survey was: a. First Opened b. The initial invite was sent. Confirm that any custom Survey Templates appear under Library Survey Templates. Page 33 of 38

Confirm that existing Community Members are still present in the UI and have profile data o Click Community Members Existing community members will be listed here o Click Profiles (accessed under the Community tab) Confirm that existing profiles are present Confirm that data exists for the profile members, under Manage Profiles Page 34 of 38

Appendix: 1. Determining the web server root in Microsoft IIS: The web server root can be checked under Microsoft IIS by performing the following steps: 1. Open Microsoft IIS 2. Right click the web site that is being used to host Vovici Enterprise 3. Select Properties 4. Click the Home Directory tab Note: the path specified in the Local Path field Page 35 of 38

2. ASP.NET Framework Vovici Enterprise 4.0 only works with version 2.0.50727 of the Microsoft ASP.NET Framework. Microsoft ASP.NET Framework 1.1 will not function. If both are installed on the Application Server inside Microsoft IIS it is possible to enable the version 2.0.50727 over the version 1.1 by following the steps below: 1. Open Microsoft IIS 2. Right click the Community Virtual Directory 3. Select Properties 4. Click the ASP.NET tab 5. Select 2.0.50727 in the ASP.NET version dropdown box. 6. Click OK Note: Both versions of Microsoft ASP.NET cannot be used on the same virtual directory. Applications using one version of ASP.NET (v1.1 for example) cannot run in an application using the other version of ASP.Net (v2.0 for example). A new Application Pool must be created to house one of the applications using the different version of ASP.NET. Page 36 of 38

3. Knowledge Base Vovici has a Knowledge Base within our Vovici Customer Support Portal. This contains valuable recommendations on maintaining the server Vovici Enterprise is installed on and contains troubleshooting assistance (This is in addition to our installation experts). It also provides information about best practices for the application: http://www.vovici.com/support/ Page 37 of 38

4. Administrative Portal Guide The link below explains how to access the Administrative Portal and what the functions are of each section of the Administrative Portal. It can be very helpful in administering the application: http://vovici.com/downloads/commhelp/4_0/vovici_v4_system_admin_guide.pdf Page 38 of 38

Migrate From Version 3.1 to Version 4 Guide Vovici Enterprise 4.0. December 2008