Installation Guide. for Business Partners

Transcription

1 Installation Guide for Business Partners

2 Notice The information in this document is subject to change without notice. MPAY Inc. shall not be liable for any technical or editorial errors contained herein or for incidental or consequential damages resulting from the performance, furnishing, or use of this publication. The software described in this document is furnished under license and may be used or copied only in accordance with the terms of that license. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including (but not limited to) photocopying, recording, scanning, or retrieval system, for any reason other than the purchaser s personal use without the express written permission of MPAY Inc. The company data contained in the examples within this text is fictitious and any resemblance to real people, places, or companies is purely coincidental. MPAY, Millennium, and payentry.com are trademarks of MPAY Inc. Windows, Windows 2000, Windows XP, Windows Vista, and Windows 7 are registered trademarks of Microsoft, Inc. All other brand and product names are trademarks or registered trademarks of their respective owners. Corporate Headquarters: 9920 West Kincey Avenue Suite 120 Huntersville, NC Phone: Copyright 2012 by MPAY, Inc Version: February, 2012 Document Number: M3 Install GD BP All rights reserved Printed in the United States of America

3 Table of Contents TOC Chapter 1: Introduction What Are the Components of Millennium 3? What Are the Prerequisites? Part 1 Installing Millennium Chapter 2: Installing SQL Server 2008 R2 Express Edition SP Requirements & Download Requirements for SQL Server 2008 Express Download SQL Server 2008 Express Installation Configuration Chapter 3: Overview of Millennium 3 Installation What Type of Installation Are You Doing? Business Partner Installation Process Set Up Your Database Server Set Up Your File and Print Server End Client Installation Process Chapter 4: Installing Millennium Download the Millennium 3 Installation Package Install Millennium Chapter 5: Creating the Millennium Database Create the Database Configure the Database Chapter 6: Setting Up Dedicated Process Servers Set Up Your Processing Machines Set Up Printers for the Processing Machines Restart the Process Server Service Chapter 7: Setting Up Other Workstations in Your Organization Chapter 8: Installing End-Clients iii

4 Table of Contents End Client Installation Process Optional End Client Installation Steps When should your end client have a dedicated processing machine? End clients with users at multiple locations Chapter 9: Synchronization Basic Operation Upstream and Downstream Sites Installation From the Downstream Site Looking Upstream Running Synchronization Initiating a Synchronization Synchronization Jobs Versions and Synchronization Database Version Updates Sent Downstream The Mechanics of Synchronization What Data is Exchanged The User Who Made a Change Last Transmit and Receive Times Verification and Security Conflict Resolution What Conflicts Are Recognized How Conflicts Are Resolved Working With Conflict Resolution Caveats Starting Payroll New Hires Manual Checks Deleting and Recreating Data Full Company Downloads Sending a New Company Resending an Existing Company Network and Protocol Details Underlying HTTP Protocol Files Exchanged During Synchronization Part 2 Appendices Appendix A: Installing SQL Server 2005 Express Edition SP Requirements & Download Requirements for SQL Server 2005 Express Download SQL Server 2005 Express iv Millennium 3 Installation

5 Table of Contents Installation Configuration Appendix B: Database Tables: Synchronized Appendix C: Database Tables: Not Synchronized Appendix D: Minimum Process Server User Rights Appendix E: Millennium 3 Registry Warning Add the User as a Local Administrator Edit the Registry to Grant Full Control to Specific Registry Keys Additional Registry Keys to Allow End Users to Save Preferences Release 3.29 v

6 Table of Contents vi Millennium 3 Installation

7 Introduction Chapter 1 This chapter provides you with a general overview of Millennium 3. What Are the Components of Millennium 3? A summary explanation of the components of the Millennium system are as follows: A. The Millennium 3 application This is the primary application. It is the one in which you enter employee and company information, process money transfers, and process taxes. B. The Process Server application This is the next most important application. Many people use the term process server to describe a separate computer that performs a function. This is a misnomer. A computer functions as a processing machine when it is running the Process Server application (processserver.exe). The Process Server application is responsible for ensuring any job that appears in the Millennium job queue is processed. If you do not have a computer running the Process Server application, all jobs will simply sit in an Active state nothing will get processed. In the Millennium 3 system, the processing machines handle the job of building and printing reports, checks, and tax forms. They also process the end data transfer jobs to and from the end clients; these are known as synchronization jobs. C. The Synchronization Server application Like the term Process Server, many people mistakenly use this term to refer to a separate machine that performs a function. The Synchronization Server application is the part of the Millennium 3 system that is responsible for receiving synchronization requests from downstream sites. This application and the machine it runs on becomes the conduit for data transfers between the service bureau and end clients. The Synchronization Server machine is the only Millennium 3 component that needs to be accessible to/from the Internet. Even though the access is strictly limited, a qualified network administrator should assist with the configuration as router and firewall changes will be necessary. D. Other applications are packaged with the system, but they are outside the scope of this document. Release

8 Chapter 1 E. MPAY occasionally creates utilities you can use with the Millennium 3 system to make specific bulk changes (for example, change EFile status, Employee Import, and so on). These utilities are usually distributed via knowledge base articles. For an explanation of the system components, see the Millennium 3 System Architecture document. The document is available in Knowledge Base article What Are the Prerequisites? If you have not done so already, please read the Millennium 3 System Requirements document, which provides information on hardware and networking requirements. The document is available in Knowledge Base article IMPORTANT MPAY offers some specific information and steps concerning other products as a helpful gesture to assist you; however, such instruction goes beyond the scope of MPAY s business. If you have questions beyond what is provided here, or need assistance with purchasing, setting up, running, or maintaining your organization's computer systems hardware, software (including Microsoft), and networking please seek help from sources that provide those services. Once you have confirmed that all prerequisites are met, you can install Millennium 3. 8 Millennium 3 Installation

9 M3-Install-GD-BP Part 1 Installing Millennium 3 Release

10 1 Installing Millennium 3 10 Installation Guide

11 Chapter 2 Installing SQL Server 2008 R2 Express Edition SP1 This chapter describes the steps you must take to install and configure SQL Server 2008 R2 Express Edition Service Pack 1 for use with Millennium 3. This chapter includes the following subjects: Requirements & Download Installation Configuration Note Any links provided in this chapter were current as of the time of this writing. Microsoft and other vendor sites change URLs without notice; therefore, be prepared to use an online search engine if a link fails. Requirements & Download Requirements for SQL Server 2008 Express Visit Microsoft s Web site and verify you have met all the requirements needed to install and run this application: requirements.aspx Download SQL Server 2008 Express After the requirements have been met, download the SQL Server 2008 R2 Express Edition SP1 from Microsoft s site: Microsoft has two versions of SQL 2008 Express: one for 32 bit versions of Windows, and another for 64 bit versions of Windows. Be sure you download the correct version for your edition of Windows. Release

12 Chapter 2 Installation This chapter was written with screen shots from the 32 bit version of SQL 2008 Express. The installation process for the 64 bit version of SQL 2008 Express is the same. When you download the files mentioned above, do not run the installation from the Microsoft site. You should save the files first, then run/open the files for installation. To install SQL Server 2008 Express Edition, perform the following steps: 1. Locate the file you downloaded in the previous section (for example, SQLEXPR32_x86_ENU.EXE). 2. Double click the downloaded file to launch the SQL Server installation. The Windows operating system displays the following warning: Figure 1: Open File - Security Warning dialog It is safe to continue the installation. 3. Click the Run button. The installation program displays the SQL Server Installation Center dialog, beginning with the Planning page: 12 Millennium 3 Installation

13 Installing SQL Server 2008 R2 Express Edition SP1 Figure 2: SQL Server Installation Center, Planning page 4. Select the Installation option. The installation program displays the Installation page: Figure 3: SQL Server Installation Center, Installation page 5. Select the New SQL Server stand-alone installation option. Release

14 Chapter 2 The installation program checks your machine for possible problems, then displays the Setup Support Rules page in the SQL Server 2008 Setup dialog: Figure 4: Setup Support Rules page If the program detected failures or warnings, review the details or report. Ensure all problems are solved before running this installation program again. 6. If no issues are detected, click the OK button. The installation program displays the Setup Support Files page: Figure 5: Setup Support Files page 7. Click the Install button. 14 Millennium 3 Installation

15 Installing SQL Server 2008 R2 Express Edition SP1 The installation program performs another check for potential problems, then displays the Setup Support Rules page: Figure 6: Setup Support Rules page If the program detected failures or warnings, review the details or report. Ensure all problems are solved before running this installation program again. 8. If you are ready to proceed, click the Next button. The installation program displays the Installation Type page: Figure 7: Setup Support Rules page Release

16 Chapter 2 This page allows you to choose between installing a new instance of SQL Server 2008 or adding features to an existing one. 9. Select the appropriate radio button and click the Next button. In this example, Perform a new installation of SQL Server 2008 is selected. The installation program displays the Product Key page: Figure 8: Product Key page This page allows you to choose between installing a free edition of SQL Server 2008 or entering a product key. 10. Select the Specify a free edition button and select Express from the drop down list. 11. Click the Next button. The installation program displays the License Terms page: 16 Millennium 3 Installation

17 Installing SQL Server 2008 R2 Express Edition SP1 Figure 9: License Terms page 12. Read and accept the license agreement to continue. 13. Click the Next button. The installation program displays the Feature Selection page: Figure 10: Feature Selection page 14. Put a check in the Database Engine Services check box, as shown in Figure 11: Release

18 Chapter 2 Figure 11: Feature Selection page You do not need to check any additional boxes. 15. Click the Next button. The installation program displays the Instance Configuration page: Figure 12: Instance Configuration page This screen allows you change the name of the SQL Server instance. This can be helpful if you already have a previous version of SQL installed on the same machine. 18 Millennium 3 Installation

19 Installing SQL Server 2008 R2 Express Edition SP1 The server name that appears when you run Millennium Server Setup to connect to the database (Chapter 3, Installing Millennium 3 ) depends on the option you select on this page. If you select the: Default instance option (the default value), the server name will appear as the COMPUTER name Named instance option (as in Figure 12 above), the server name will appear as COMPUTER\<whatever you type in the text box> In this example, the instance is named SQLExpress2008. You can normally use the default selection. 16. Click the Next button. The installation program displays the Disk Space Requirements page: Figure 13: Disk Space Requirements page 17. If you are satisfied with amount of free space and your selection of the installation location, click the Next button. The installation program displays the Server Configuration page, beginning with the Service Accounts tab: Release

20 Chapter 2 Figure 14: Server Configuration page, Service Accounts tab 18. In most cases for the SQL Server Database Engine, you can select the built in System account by selecting NT AUTHORITY\SYSTEM under the Account Name column, unless otherwise requested to do so. The only other account type that should be used is a local or domain administrator account. 19. For the SQL Server Browser service, select Automatic under the Startup Type column. Note The value of the Startup Type column for both services should be Automatic. There is no need to click the Collation tab because you will use the default settings (don t change them). 20. Click the Next button. The installation program displays the Database Engine Configuration page, beginning with the Account Provisioning tab: 20 Millennium 3 Installation

21 Installing SQL Server 2008 R2 Express Edition SP1 Figure 15: Database Engine Configuration page, Account Provisioning tab 21. Select the Mixed Mode radio button. 22. Enter a password in the two text fields. This will be automatically assigned to the sa (system administrator) account. WARNING It is very important to remember this password. The password should have a mix of letters and numbers. 23. Click the Add Current User button. Add other Windows user accounts, as necessary. 24. Click the User Instances tab: Release

22 Chapter 2 Figure 16: Database Engine Configuration page, User Instances tab 25. Remove the check mark from the Users are allowed to run a separate instance of the Database Engine check box. 26. Click the Next button. The installation program displays the Error and Usage Reporting page: Figure 17: Error and Usage Reporting page 27. Use the default settings (don t change them). 28. Click the Next button. 22 Millennium 3 Installation

23 Installing SQL Server 2008 R2 Express Edition SP1 The installation program checks your machine for potential issues that would block the installation, then displays the Installation Rules page: Figure 18: Installation Rules page If the program detected failures or warnings, review the details or report; then ensure all problems are solved before proceeding. 29. If no issues are detected, click the Next button. The installation program displays the Ready to Install page: Figure 19: Ready to Install page 30. Click the Install button. Release

24 Chapter 2 The installation program displays the Installation Progress page. Once the installation has completed, it displays the following: Figure 20: Installation Progress page 31. Click the Next button. The installation program displays the Complete page: Figure 21: Complete page 32. Click the Close button. 24 Millennium 3 Installation

25 Installing SQL Server 2008 R2 Express Edition SP1 Configuration This section is especially important if you will have more than one computer accessing the Millennium database. After the installation, perform the following steps: 1. In Windows, select Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager. The system displays the SQL Server Configuration Manager window. 2. In the left pane, expand SQL Server Network Configuration. 3. Highlight Protocols for SQLEXPRESS (or whatever you named the instance). In this example, the instance is named SQLExpress2008, so the selection that is highlighted is Protocols for SQLEXPRESS Highlight and right click TCP/IP. 5. Select the Enable option (as shown in Figure 22) to enable access via TCP/IP: Figure 22: SQL Server Configuration Manager window Once you have enabled TCP/IP, you must restart both SQL Server services. 6. In the left pane, expand SQL Server Services. 7. Highlight and right click SQL Server Browser. 8. Select the Start option (as shown in Figure 23) to start the service: Release

26 Chapter 2 Figure 23: SQL Server Configuration Manager window 9. Highlight and right click SQL Server (SQLEXPRESS) (or the named instance). 10. Select the Restart option to restart the service. Once both services have restarted, your window should look like the example in Figure 24: Figure 24: SQL Server Configuration Manager window 26 Millennium 3 Installation

27 Installing SQL Server 2008 R2 Express Edition SP1 11. You are finished with the SQL Express installation and can close the SQL Server Configuration Manager. 12. Once all SQLExpress components have been installed and configured, you should reboot the computer where you installed SQL Express, if possible. Release

28 Chapter 2 28 Millennium 3 Installation

29 Chapter 3 Overview of Millennium 3 Installation This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects: What Type of Installation Are You Doing? Business Partner Installation Process End Client Installation Process What Type of Installation Are You Doing? There are two primary types of installations: Business partner End client Each installation has its own typical needs, which are explained in the sections that follow. Business Partner Installation Process When you install the system for a service bureau, follow these major tasks: A. Set Up Your Database Server B. Set Up Your File and Print Server The sections that follow explain the detailed steps for each major task. Set Up Your Database Server This is usually done by a qualified network or database administrator. Set Up Your File and Print Server This is usually done by a qualified network or database administrator. End-Client Installation Process For this procedure, see Chapter 8, Installing End Clients. Release

30 Chapter 3 30 Millennium 3 Installation

31 Installing Millennium 3 Chapter 4 This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects: Download the Millennium 3 Installation Package Install Millennium 3 Download the Millennium 3 Installation Package To download the Millennium 3 installation program, perform the following steps: 1. Go to and log in. 2. Navigate to Support > Product Updates > Millennium 3 > Download Latest Version. The site displays the Download Latest Version page, as shown in Figure 25: Release

32 Chapter 4 Figure 25: Download Latest Version page You will download (save) the Millennium 3 installation file to your file server. Saving it to the server s hard drive allows you to run the installation file on multiple computers without the need to download it multiple times. 3. Click the Download Millenn3nnn.exe link (where nnn is the minor version number of the current Millennium 3 release). The site displays the Download page, as shown in Figure 26: 32 Millennium 3 Installation

33 Installing Millennium 3 Figure 26: Download page If your download doesn t automatically start after 30 seconds, click the here link shown above. When the site begins to download the file, your browser will display a pop up window, similar to the one shown in Figure 27: Figure 27: Opening MillennXXXXX.exe dialog 4. Click the Save button and save the file to a location where it can be accessed by other computers on your network. If you intend to install Millennium 3 on just one workstation, you can save the file to the desktop, the Downloads folder, or whatever location is easiest for you to remember. Figure 28 shows an example of saving the file to your desktop: Release

34 Chapter 4 Figure 28: Choose a download location 5. Choose your location to save the file. The download begins. When the download is complete, you can either run the program or close the window and run the install file later. Install Millennium 3 To install Millennium 3, perform the following steps: 1. Ensure you have your Millennium 3 license key handy. 2. Double click the downloaded file to launch the Millennium 3 installation on the first workstation. The Windows operating system displays the following warning: Figure 29: Open File - Security Warning dialog It is safe to continue the installation. 3. Click the Run button. 34 Millennium 3 Installation

35 Installing Millennium 3 Figure 30: Welcome page of the Millennium 3 Installer dialog 4. At the Welcome screen, press the Next button to continue the installation. The installation program displays the Customer Information page: Figure 31: Customer Information page of the Millennium 3 Installer dialog 5. Fill in the User Name, Organization, and Serial Number fields. 6. Click the Next button. The installation program displays the Destination Folder page: Release

36 Chapter 4 Figure 32: Destination Folder page 7. Select your destination folder (or keep the default setting shown above) and click the Next button. The installation program displays the Ready to Install the Program page: Figure 33: Ready to Install the Program page Millennium 3 now has all the information it needs to complete the installation on the first workstation. You can click the Back button to change any previous selections, or press the Install button to continue the installation. 36 Millennium 3 Installation

37 Installing Millennium 3 8. One the install is complete, click the Finish button. This concludes the third major task in the installation process. You are ready to proceed with creating your Millennium database. Release

38 Chapter 4 38 Millennium 3 Installation

39 Chapter 5 Creating the Millennium Database This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects: Create the Database Configure the Database Create the Database To create and configure your production Millennium database from the workstation used in the preceding section, perform the following steps: 1. Open Millennium 3 on the first workstation. The system displays a dialog similar to the following: Figure 34: Create New Database dialog 2. Click the Yes button to create the database. The system displays the Specify the SQL Server Computer page: Release

40 Chapter 5 Figure 35: Specify the SQL Server Computer page 3. Select your SQL Server computer (the SQL Instance name) from the Server dropdown list. Even though you can type the name of the SQL Instance name into the field provided, you should select it from the drop down list. If the SQL Instance name does not appear, that is an indication that: Something is not ready with SQL, and You should cancel the database creation process until you have remedied the situation with the SQL Instance 4. Click the Next button. The system displays the Specify the Millennium Database page: 40 Millennium 3 Installation

41 Creating the Millennium Database Figure 36: Specify the Millennium Database page 5. Select the Create a new Millennium database radio button. 6. Enter the name of the new database in the Database text field. 7. Click the Next button. The system displays the Login to the SQL Server page: Figure 37: Login to the SQL Server page Release

42 Chapter 5 Before you can create your database, you must log into the SQL Instance with a username and password that has System Administrator level rights to SQL. The default username is sa. You would have defined the sa password during setup if you used one of the following: Chapter 2, Installing SQL Server 2008 R2 Express Edition SP1 or Appendix A, Installing SQL Server 2005 Express Edition SP4 Otherwise, check with the network or database administrator for this password. If you see an error dialog that mentions password validation failed, check your SQL error log. The error log will be in a sub folder where SQL was installed; for example: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG The error log will record failed logins by default. The error will most likely look something like the following: :07:20.55 Logon Error: 18456, Severity: 14, State: :07:20.55 Logon Login failed for user 'Millennium'. [CLIENT: ] SQL 2008 automatically tries to create any new user with the Enforce Password Policy option enabled, and the password for the Millennium SQL account does not meet this requirement. At this point, someone must manually create the Millennium SQL account, assign it a password, and remove all three check marks from the password policy check boxes. Once this is done, you will need to cancel and then restart the database creation process from the beginning of this section. After you have successfully logged into SQL and the user called Millennium has been created, you are prompted to enter a database name (the default name is Millennium). 8. Click the Next button to continue. The system displays the Specify Data Source Name (DSN) page: 42 Millennium 3 Installation

43 Creating the Millennium Database Figure 38: Specify Data Source Name page Next, you must specify the data source name (DSN). For simplicity of naming, the DSN usually has the same name as your new database. 9. Enter a name in the Database (DSN) text field. 10. Click the Next button. The system displays the QuickStart File page: Figure 39: QuickStart File page Release

44 Chapter 5 The Millennium 3 uses the QuickStart file (QSF) to: Create your database Set up the database structure Begin to populate the database with data Establish a two way trust to a specific upstream synchronization site The example in Figure 39 on page 43 is the default QSF used for service bureau installations that is bundled in Millennium Either use the default QSF or click the Browse button to locate another QSF. 12. Click the Next button. Once the database has been created, the system displays the Specify Shared File Location page: Figure 40: Specify Shared File Location page You must specify a place to put the shared system files that Millennium requires. These files are usually placed on your file server. Note Whoever is doing the initial installation of Millennium 3 must have Full Share permissions as well as Full File and Folder rights to the selected folder. 13. Use the Browse button to select the appropriate folder. 14. Click the Next button. 44 Millennium 3 Installation

45 Creating the Millennium Database Once the files has been copied, the system displays the Millennium Server Setup Complete page: Figure 41: Millennium Server Setup Complete page Your setup of the Millennium database is now complete. The next steps in the process are to configure the system so it is ready to use. 15. Click the Finish button. Configure the Database 1. Log into Millennium 3 with the initial default username and password of Admin. 2. Go to System > Setup > Online Help info tab. The system displays the Online Help Information page: Release

46 Chapter 5 Figure 42: Online Help Information page 3. Click the Import Help Information button. The system displays the Open dialog: Figure 43: Open dialog 4. Navigate to the following folder and open the M3Doc file, as shown in Figure 43: C:\Program Files\Millennium 3\Server\Quickstarts If you skip this step, the system will have no help text available. 5. Select the System > Synchronization > Upstream Site tab. The system displays the Upstream Synchronization Site page: 46 Millennium 3 Installation

47 Creating the Millennium Database Figure 44: Upstream Synchronization Site page 6. Click the Synchronize Now button perform the initial syncup with MPAY. Release

48 Chapter 5 48 Millennium 3 Installation

49 Chapter 6 Setting Up Dedicated Process Servers This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects: Set Up Your Processing Machines Set Up Printers for the Processing Machines Restart the Process Server Service Set Up Your Processing Machines To set up your processing machines, perform the following steps: 1. Choose one username that will run the Millennium 3 Process Server service. This username should be a network (domain) administrator level account with a password that does not expire. 2. Log onto the machine that will become a Process Server, using the username you chose in the previous step. You must stay logged onto the computer with this account for the rest of this section. 3. Install Millennium 3 on the computer that will become a processing machine. 4. Once Millennium is installed, go through the same database setup that you did on the first workstation (Chapter 5, Creating the Millennium Database ) but this time, select an existing database. Ensure you can log into Millennium before proceeding. 5. Set up the ProcessServer.exe application to run as a service: a. In the Windows operating system, open a command window (run cmd.exe). The system displays the command window: Release

50 Chapter 6 Figure 45: Command window (cmd.exe) b. Change the directory to the folder where you installed Millennium 3. c. To see all the options available to the process server command, you can type the following at the command line: processserver /? The system displays the options: Figure 46: processserver /? d. If you have called your database Millennium, install the service by typing the command below and pressing the [Enter] key: processserver /I The system displays the following warning and message: 50 Millennium 3 Installation

51 Setting Up Dedicated Process Servers Figure 47: processserver /i If you have named your database something else, use the following command instead, substituting databasename with the actual name of your database: processserver /I /D databasename e. Type exit and press the [Enter] key to close the command window. f. In the Windows operating system, select Start > Control Panel > Administrative Tools > Services. The system displays the Services window. g. Scroll down and locate the Millennium Process Server line, as shown in Figure 48: Figure 48: Services window h. Right click on the Millennium Process Server line. The system displays the Millennium Process Server Properties dialog. Release

52 Chapter 6 i. Select the Log On tab, as shown in Figure 49: Figure 49: Process Server Properties dialog j. Select the This account radio button, as shown in Figure 49. k. Enter the account you chose in step 1 on page 49 in the text field next to the Browse button. l. Enter the account s password in the Password and Confirm password fields. m. Click the OK button. n. Do not close the Services window; it is required in a subsequent step. Set Up Printers for the Processing Machines 1. Add all printers that will be used by Millennium 3 as Windows printers: a. Ensure you set the Windows default printer to a physical printer. b. Log in to Millennium 3. c. In Millennium, select System > Setup > Printers tab. d. To add a printer, click the yellow star button in the page header: 52 Millennium 3 Installation

53 Setting Up Dedicated Process Servers Figure 50: Yellow star button to add an item The system displays a pop up window in which you type in a printer code: Figure 51: Please Enter a Printer Code dialog e. Enter the printer s ID and click the OK button. The system adds the printer to the items list. f. Enter the appropriate information in the Description field. g. Select the appropriate printer from the Physical Printer drop down list. h. Be sure to specify one printer as the Millennium default printer by putting a check in the Default Printer check box. i. Repeat these steps to add more printers, as necessary. Restart the Process Server Service 2. Return to the Services window and start the Millennium Process Server service, as shown in Figure 52: Figure 52: Services window 3. Close the Services window. 4. Repeat the steps in this section for each additional processing machine. Release

54 Chapter 6 54 Millennium 3 Installation

55 Chapter 7 Setting Up Other Workstations in Your Organization The last step is to install Millennium 3 on the rest of your organization s computers, as necessary. Note If you are going to set up a computer as a dedicated or local process server for a user who is not a local administrator, see Appendix D, Minimum Process Server User Rights. Release

56 Chapter 7 56 Millennium 3 Installation

57 Installing End-Clients Chapter 8 This chapter describes the steps you must take to install and configure Millennium 3. It includes the following subjects: End Client Installation Process Optional End Client Installation Steps End-Client Installation Process Note This section assumes that your end client has decided to use Millennium 3 instead of Payentry.com. End client installations have similar prerequisites to service bureau installations. However, the process differs in several key ways. Often good communication early in the process is the key to a successful end client installation. 1. Determine how your end client will use Millennium 3. How many people will be using it? Are the users at a single or multiple locations? Users at multiple locations may require some type of remote access solution like Microsoft Terminal Server or a Citrix product. Remote access solutions are briefly discussed in Optional End Client Installation Steps on page 58. How many company codes and employees will be loaded in their system? 2. Determine you end client s level of technology preparedness. This is especially important for end clients with multiple users. Find out the following: Does the end client have an existing IT staff that you can work with? If not, who is available to make firewall or network security changes? Does the end client have an existing server they use to share files? If not, whose computer will be the main Millennium computer? Do they have an existing server with SQL2005 or SQL2008 on it? If not, do they have an existing server where they will allow you to install SQLExpress? Keep in mind that you may have to install SQLExpress on someone s workstation. Release

58 Chapter 8 Are the end client s users allowed to be local administrators of their own workstations? That is, do they have full and complete rights to install or run anything they want to on their computer? If not, you may need to install the Millennium Process Server service on someone s computer. 3. MPAY Services will create a QSF with your end client s data. 4. Install the Millennium 3 install file on your end client s first workstation using the same process detailed in Install Millennium 3 on page Create the Millennium database on the end client s side using a similar to (but more limited than) process detailed in Create the Database on page 39. a. Follow the same process detailed in step 1 and step 2 on page 39. b. Log into Millennium 3 with a valid service bureau username. c. Follow the same process detailed in the Service Bureau Installation process steps 4d. d. Go to System > Synchronization > Upstream Sites tab, and click the Synchronize Now button perform the initial syncup with your service bureau. e. End clients can usually print reports by previewing them first, then printing them from Adobe Reader. If they need to run reports or print checks, you must set up a Millennium 3 printer for them. Optional End-Client Installation Steps When should your end-client have a dedicated processing machine? When should your end client have a computer set up as a dedicated processing machine? The main reason to make an end client machine a dedicated processing machine is in the case where your end client s IT staff doesn t allow the end users to be local administrators of the computer(s) where they will run Millennium 3 from. If this is the case, follow the same process detailed in Chapter 6, Setting Up Dedicated Process Servers. End-clients with users at multiple locations End clients with users at multiple locations present a complex set of issues and from a technical perspective are best served when using Payentry.com. 58 Millennium 3 Installation

59 Synchronization Chapter 9 This chapter explains database synchronization in Millennium 3. Synchronization is the process of keeping portions of two or more Millennium databases in sync with each other through the exchange of data and structure changes. The synchronization in Millennium has the following basic properties: Efficiency Only data changes are sent between sites rather than full tables, allowing small file sizes. In addition, compression is used to further reduce file sizes. Reliability A large number of verifications are performed against many aspects of both databases during each synchronization, ensuring a reliable and consistent synchronization process. Automated conflict resolution is used to handle any single piece of data that is changed differently at two sites. Security Triple DES encryption and internal consistency checks are used to ensure data in transit cannot be viewed by any party except the destination site. Scalability An arbitrary number of synchronization levels can be used to create a large network of sites communicating with each other. Compatibility The synchronization protocol uses HTTP to communicate between sites, ensuring easy traversal of most networks and a high probability of getting through firewalls and proxy servers. Ease of Use Synchronization is easy to configure, execute and monitor. In addition, useful management information is automatically maintained on the various parties synchronizing with each other. This chapter provides the following: Basic Operation The Mechanics of Synchronization Conflict Resolution Caveats Full Company Downloads Network and Protocol Details Release

60 Chapter 9 Basic Operation This section provides a basic understanding of where synchronization is configured at a site and how it is initiated. Upstream and Downstream Sites A site is an installation of Millennium on a series of computers, all centered around a single database. A site can have only one upstream partner (MPAY Services), but an unlimited number of downstream partners (your organization and your end clients). From your organization s perspective, MPAY Services is the upstream site, and you and your end clients are the downstream sites. In this case, Payentry.com is also considered a downstream site. The synchronization system allows for unlimited levels of sites to communicate with each other. This means MPAY Services can have an unlimited number of downstream sites. For more information, see the System Architecture for Business Partners reference document. Installation When a new downstream site is installed: A. The upstream site extracts a QuickStart file (QSF). The QuickStart file contains a copy of all the system and company data needed by the downstream site. B. The upstream site uses the QSF to install the downstream site. The QuickStart file also includes the address of the upstream site s synchronization server; after installing a new downstream site, the downstream site will immediately be ready to synchronize with the upstream site. From the Downstream Site Looking Upstream To view MPAY Services s upstream site information in Millennium, select the System > Synchronization > Upstream Site tab. The system displays the Upstream Synchronization Site page, as shown in Figure 53: 60 Millennium 3 Installation

61 Synchronization Figure 53: Upstream Synchronization Site page At your organization, the upstream site is MPAY Services. At your end client sites, the upstream site is still MPAY Services. Explanations of the fields on this page are as follows: Description Sync Hostname This field is automatically filled in by the upstream site. If the upstream site s (MPAY Service s) synchronization server address changes, the downstream site can adjust its settings to match. Normally, the upstream site will automatically send its synchronization server information to the downstream sites, so this change does not need to be made at the downstream site. Port This field should have the value 81. Last Transmit, Last Receive Company These fields are automatically filled in. They display the date time stamps from the last synchronization: Last Transmit is when the last upload was sent to the upstream site (MPAY Services) Last Receive is when the last download was received from the upstream site (MPAY Services) The list of companies shows the companies from the downstream site that are being synchronized with the upstream site. Release

62 Chapter 9 You can make modifications to the company list, but MPAY Services will override any changes made: If a company is removed from Company (the downstream site list), MPAY Services will send a new copy of that company during the next synchronization process. If a company is added to Company (the downstream site list), the new company will be removed from the downstream site list during the next synchronization process however, the company data will not be removed from the downstream site. Full Download Synchronize Now, Test Connection The Full Download check box is empty by default, which indicates the company is being synchronized normally; that is, only changes to the data are exchanged. If you put a check in this check box for any company, MPAY Services will download a full copy of that company during the next synchronization process. The Synchronize Now and Test Connection buttons create synchronization jobs that run a complete synchronization or just test the connection to the upstream synchronization server, respectively. After creating a job using either button, go to the System > Operations > Job Queue tab to monitor the progress of the synchronization or test job. Running Synchronization Initiating a Synchronization Synchronization is always initiated by the downstream site, never the upstream site. The downstream site can pull updates from the upstream, but the upstream cannot push updates to the downstream. A synchronization can be initiated in one of three ways: by explicitly requesting a synchronization with the upstream site, by submitting a payroll for processing at a nonprocessing site, or via a scheduled synchronization. An explicit synchronization can be initiated via the company main menu or through the upstream synchronization screen. Submitting a payroll at a non processing site will also initiate a synchronization. The upstream site will receive the data then submit the payroll for processing. If the upstream site is also not a processing site it will synchronize with its upstream site. The payroll will continue to be submitted and synchronized upstream until a processing site receives it. If you have a dedicated process server, you can use a job schedule to automate the synchronization process on a scheduled basis. The job schedule should be for a SyncUp job, and no properties need to be set. Beware that setting scheduled synchronizations to 62 Millennium 3 Installation

63 Synchronization run at client sites can cause a heavy load on the upstream site s synchronization server once many downstream sites are installed. It most cases it is recommended that service bureaus do not configure scheduled synchronizations at remote client sites unless absolutely necessary. Synchronization Jobs At the downstream site a single SyncUp job is used to implement the synchronization with the upstream site. This job will connect to the upstream site, verify the synchronization can be run, exchange and merge data changes, and confirm the synchronization. The job results show the number and type of changes made during the synchronization. At the upstream site three individual SyncDown jobs are used to implement the synchronization. These three jobs correspond to the extract, merge and confirm steps of the synchronization. Separate jobs are used in case the downstream site disconnects abnormally from the synchronization server and does not reply to one of the stages. The SyncDown jobs list the site name they are running for. Because a single SyncDown job may be synchronizing multiple companies, the SyncDown job does not list a company code. Versions and Synchronization Database Version Updates Sent Downstream The synchronization process requires that any two databases that are synchronizing have exactly the same structure. This ensures the same tables and fields will be updated at both sides. The particular database structure in use at a site is tracked using the database schema version. Note that this is not the same thing as the Millennium program version, which changes independently of the database schema version. Schema updates are automatically sent from an upstream site to its downstream sites during a synchronization. This automatically upgrades a downstream site to the same schema version as its upstream site and ensures the downstream site can always synchronize properly, regardless of the program version in use at either site. Schema updates originate at MPAY and are sent downstream throughout the entire synchronization network. Note A downstream site cannot have a higher schema version than its upstream site. If this occurs, the downstream site will not be able to synchronize with the upstream until the upstream is upgraded to at least the same schema version as the downstream site. This is because schema updates are only sent downstream. Release

64 Chapter 9 The Mechanics of Synchronization The following section explains what data is exchanged between two sites and how it flows between the sites. What Data is Exchanged The synchronization process works by exchanging all updates made by two sites between those two sites. During a synchronization, each site extracts and sends the other site a list of the changes that were made, then receives and merges changes made by the other site. Changes made at a site will propagate throughout the synchronization network via all of a site s upstream and downstream partners. For example, if two remote client sites both share a company code, employee changes made at one site will be synchronized upstream to the MPAY Services, then downstream to the other site. All data is filtered through the company list, so only data relevant to the companies being synchronized by both sites is exchanged. In general, system level data is sent from upstream to downstream only. Thus changes made at a downstream site are not sent upstream and are ignored. In general, company and employee level data is exchanged in both directions. For a list of tables that are: Exchanged, see Appendix B, Database Tables: Synchronized Not exchanged, see Appendix C, Database Tables: Not Synchronized The User Who Made a Change Changes made at a site are always logged with name of the user who made the change. When changes are transmitted through synchronization the log stores the remote site ID as the user who made the change. The individual at the remote site who made the change is not logged at the local site, although the original name is still logged at the remote site. Last Transmit and Receive Times Data is sent from one site to another based on the time when it was changed. All data that has been modified since the last time a synchronization was run successfully will be sent to the remote site. The Last Transmit and Last Receive synchronization times indicate the times when data was last sent from one site to the other. The Last Transmit time on an upstream site s record is the same as the Last Receive time at the downstream site, and vice versa. Figure 54 shows the synchronization times as stored at two sites: 64 Millennium 3 Installation

65 Synchronization Figure 54: Sync times as stored at two sites The times are always stored in the sender s time zone: The Last Transmit time is always the time (in the local time zone) that the local site last sent data to the remote. The Last Receive time is always the time (in the remote time zone) that the remote site last sent data to the local. The synchronization times are automatically maintained by the synchronization process. The times should never be changed manually. In the event that the times disagree, the Last Receive time at the receiver s site has precedence over the Last Transmit at the transmitter s site. In the example in Figure 54, it appears a two hour two minute discrepancy exists between the Transmit and Receive times. If these two computers are in time zones that place them two hours apart, the difference is really only two minutes. Verification and Security Many checks are performed during synchronization to verify the integrity of the databases being synchronized as well as the identity of the sites synchronizing. Each site is assigned a unique identifier that is placed into a QuickStart file when it is created. A new downstream site created with the QuickStart file can only synchronize to the site that created the QuickStart file. The upstream s unique ID is used as a key to ensure that only downstream sites that have the key can be synchronized to the upstream site. Both sites must always have each other s key before the synchronization can proceed. Before any data is synchronized both sides must agree on the schema (structure) of the databases they are synchronizing. An upstream site will automatically send schema changes to its downstream sites to ensure they are both using the same schema and thus synchronizing the same tables and fields. Release

66 Chapter 9 During synchronization, each field in each table synchronized is compared to ensure the same fields exist at both sides and each field has the same type. This guarantees data will not be lost due to changes in field types, or the addition or deletion of fields in a table. The data files in transit are encrypted using Triple DES and can only be read by the remote site receiving the files. Triple DES is a widely recognized encryption standard that uses 168 bit keys and provides a high degree of security. Conflict Resolution This section describes how conflicts are resolved during synchronization. What Conflicts Are Recognized A conflict occurs when two sites synchronizing data make different changes to one piece of data. For example, an employee s middle name may be changed to Sean at the upstream site, but Shawn at the downstream site. The conflict must be found and resolved to ensure data integrity between the two sites. Millennium recognizes data that ultimately exists at both sites but has different values for at least one field. If a record is updated differently at the two sites, or the same record was created differently at two sites, a conflict occurs. If a record is deleted at one site and changed at the other, the delete prevails and the record is always removed. This case is not considered a conflict. Millennium uses a unique identifier to distinguish each record in a table internally. This identifier is typically used to recognize that the same record was changed at both sites. In addition to the unique identifier, the conflict resolution system can identify when two records have been added that have different identifiers (as they always will if they are created at different sites) but represent the same record. For example, if employee 5 is added to a company at two different sites, the identifiers will be different but the two records still represent the same employee and must be checked for conflicts. How Conflicts Are Resolved Conflicts are automatically resolved by selecting the upstream or downstream site as having precedence based on the data being changed. In general the downstream site has precedence for all employee setup data. Employee setup data includes any employee level information that is used for all payrolls, such as demographics, rates, deductions, taxes, direct deposit, and so on. The upstream site has precedence for all other data, including all system and company level data, as well as historical employee data such as payroll history. When conflicts are found during synchronization, both sites will log the table and record where the conflict occurred. Each field that is in conflict will be logged in the SyncUp and SyncDown jobs using the unique identifier. In addition, both field values that are in conflict will be logged at both sites in an internal table that can be reported on. You can 66 Millennium 3 Installation

67 Synchronization use the Synchronization Conflict Resolution report (available for Millennium 3 only, not Payentry.com) to determine what conflicts occurred and how they were resolved, including what field values were not used. Working With Conflict Resolution Conflicts can be easier to create than first imagined. If one site makes a modification to a record then restores the original value, the change will still be sent to the remote site when synchronizing. If the remote site were to change the same field, a conflict will occur. For example, if the upstream site changes a calendar from the Open to the Closed state, then resets it to Open, the final change sent downstream will be to Open. The upstream site may have only been testing or verifying that the calendar can be closed. At the same time, the downstream site may change the calendar from Open to Closed in preparation to submit the calendar. When the synchronization is run, the calendar will end up in the Open state after resolving the conflicting change (Open at the upstream vs. Closed at the downstream) in favor of the upstream (which has precedence for all companylevel data). Beware that other changes that may appear to be handled by the conflict resolution may not be. When creating records many tables only require unique identifiers on records, allowing them to be otherwise identical. Records created at two sites with different identifiers in these kinds of tables are not considered in conflict and will coexist. For example, an employee deduction can be created at two sites at the same time with identical values, except for the internal unique identifier. When these changes are synchronized each site will end up with two identical deductions, since each site asked for a the same deduction to be created without knowledge of the other site having done so. This problem is further complicated when trying to delete the duplicate records. If each site deletes only one record, but they each delete a different a record (upstream deletes the first copy, downstream deletes the second) both records will end up being deleted when the synchronization runs next. The problem of duplicate records being created is especially sensitive with respect to starting a payroll. Only one site should ever start a payroll on a calendar entry. If both sites start the payroll the calendar will have duplicate checks for each employee. The easiest way to avoid these issues is for only one site to make updates to a given table. Although either site can make a change and synchronization it to the other at any time, if only one site typically makes changes to a particular tables, the chances of conflicting changes and duplicate records are greatly reduced. Release

68 Chapter 9 Caveats The following are caveats in synchronization that may cause errors or problems if not handled carefully. Starting Payroll Starting Payroll creates the data entry checks along with the default details, and sets the payroll and batches to the Open status. Synchronization will send the new check records to any synchronization partner when synchronizing. If a synchronization partner also performs a Start Payroll on the same payroll, they will create their own new check records (with unique IDs). The new check records will then be exchanged between the partners, and each site will end up with double the expected number of checks. This is normal, since each site started payroll and created checks independently. To avoid this situation, be sure to always run Start Payroll at only one location for any given payroll. New Hires Each new employee created in Millennium is given the next available employee ID number. If two synchronization partners each enter a new employee in the same company, the two different employees will each be assigned the same ID number. When synchronizing, the ID numbers will cause a database error, since each employee must have a different ID. To avoid this situation, either enter new employees in only one location, or be sure to use different employee ID ranges at each site. Manual Checks When creating manual checks, Millennium automatically creates a VM batch to contain the checks. If two synchronization partners each create a manual check in the same payroll, they will each create a VM batch. When synchronizing, the two conflicting new VM batches are resolved into one, but the checks in the VM batch at the downstream site are deleted when the VM batch conflict is resolved. The checks from the downstream site are correctly uploaded to the upstream site and can be processed, but the entry checks will not appear at the downstream site. To avoid this situation, always enter manual checks at only one location. 68 Millennium 3 Installation

69 Deleting and Recreating Data Synchronization Millennium tracks all changes to records based on their internal unique identifier. If a record is deleted and recreated, the new record will have a different unique identifier. The identifier of the new record will always be different, even if the new record has the same field values as the old record. The old identifier can not be reused in the new record. Synchronization will transmit a delete of the old record and an insert of the new record. This is normally not a problem, but in some cases the deletion of the old record at a synchronization partner may cause the deletion of records that were dependent on the deleted record. These dependent records may have been created at a synchronization partner and may not exist at the site where the record is initially deleted and recreated. This is a problem with payroll batches in particular, as mentioned above with VM batches. To avoid this situation, do not delete an recreate records unless deleting the record is known to be safe. Full Company Downloads The full company download feature of synchronization allows all the data associated with a company to be sent downstream during a synchronization. A new company can be sent to a downstream site who has not had a copy of the company before, or an existing synchronized company can be sent downstream to overwrite the existing data. Sending a New Company Sending a new company downstream downloads all data associated with a company to the downstream site when that downstream has not previously had a copy of the company. The company does not have be a new company, just a company that a particular downstream site has not seen before. Only the upstream site can send a new company downstream. If the downstream site tries to add the company the request will be declined and the company removed from the synchronized company list at the downstream site. During the next synchronization all data associated with the company will be sent to the downstream site. The downstream site will then have a full copy of the company and the company will be synchronized the same as all other companies. Resending an Existing Company Resending an existing company will download all data associated with a company to the downstream site, overwriting all data currently at the downstream site. This can be used to refresh a copy of the company at the downstream site if it has become corrupt or if the downstream site has made changes they do not want sent upstream. Either the upstream or downstream site can request that a new copy of the company be sent downstream during the next synchronization. Release

70 Chapter 9 To resend an existing company downstream, select the company list for the remote partner (either upstream or downstream depending on who makes the request) and check the Full Download check box for the company code in the list. Network and Protocol Details This section describes the synchronization protocol in more depth in order to help technical personnel implement the system and troubleshoot any problems. Underlying HTTP Protocol Synchronization uses the HTTP protocol to transport data between the upstream and downstream sites. HTTP is a very common protocol that allows connections to be made reliably between the two sites. The Millennium synchronization server acts exactly like a web server in that it responds to HTTP requests, although it only understands the requests used by synchronization. A web browser can be used to verify that a synchronization server is operating by connecting directly to the synchronization server itself. Synchronization only requires connectivity between the process server at the downstream site running the SyncUp job, and the synchronization server at the upstream site. Typically this is done over the Internet, since each site only needs access to the Internet rather than direct access to each other. For increased security and privacy, a connection can be made directly between the downstream client and the upstream synchronization server using dial up modem lines or other direct connection methods. The only requirement is that the connection be able to handle TCP/IP and HTTP traffic. Synchronization uses the standard HTTP 1.1 protocol but uses URLs and request and reply content that is specific to synchronization. Previous versions of synchronization used proprietary headers for additional information; however, these are no longer in use, allowing synchronization requests to easily traverse proxy servers and firewalls. Some downstream sites may implement restrictive proxy servers that filter access to certain web sites or hosts on the Internet. Since the upstream synchronization server is often reached through the Internet, any proxy servers at a downstream site will need to allow access to the synchronization server via HTTP. Many proxy servers automatically forward traffic destined for port 80 and using the HTTP protocol. For this reason, it is highly recommended that the upstream synchronization server be running on port 80. Synchronization uses the standard Microsoft libraries at the downstream site when accessing the synchronization server. This means any configuration done at the downstream site to connect through proxy servers, and so on, will automatically be used by the downstream site when it attempts to contact the upstream synchronization server. In addition, any firewalls in use at the downstream site must be configured to allow access from inside the downstream network to the synchronization server. 70 Millennium 3 Installation

71 Files Exchanged During Synchronization Synchronization During synchronization the upstream and downstream sites exchange a series of files to verify a synchronization can occur and to transfer the data. The exchange of files is shown in the diagram below: Figure 55: The exchange of files during synchronization The upstream site uses three jobs to implement a synchronization. Each job runs in response to a single request from the downstream site. The three jobs cannot be combined into a single job because the downstream site is not guaranteed to follow one request with another, and the HTTP protocol can disconnect between requests. The upstream site cannot grantee it will ever see a follow request from the downstream site, so it does not leave the SyncDown job running for an arbitrarily long time. The downstream site runs the entire synchronization process in a single SyncUp job. The downstream site first requests a synchronization be started by sending a Start file upstream. The Start file contains relevant information about the downstream site. The upstream verifies the contents of the file and sends a Start confirmation back downstream in response. The Start confirmation may contain schema updates and other data. After the downstream site verifies the Start Confirmation file, both sites are ready to exchange data. Each site then extracts the data changes that have not been seen by the other site and exchanges them using the Upload and Download files. A series of verifications are performed again before merging the changes from the remote site. After the verifications are complete, each site merges the actual data changes from the other site. Once the merging of data is complete a confirmation is generated by each site and sent to the other site. The confirmation allows each site to know that the data it sent was successfully received by the other site. If at any point the synchronization process is interrupted, both sites can just run a subsequent synchronization to pick up where they left off. Any lost data files or confirmations are automatically regenerated during the next synchronization. Release

72 Chapter 9 72 Millennium 3 Installation

73 M3-Install-GD-BP Part 2 Appendices The chapters contained in this part of the book concern useful and supportive information about the Millennium 3 system. Release

74 2 Appendices 74 Installation Guide

75 Appendix A Installing SQL Server 2005 Express Edition SP4 This appendix describes the steps you must take to install and configure SQL Server 2005 Express Edition Service Pack 4 for use with Millennium 3. It is recommended that you install the 2008 R2 Express Edition. For those instructions, see Chapter 2. This appendix includes the following: Requirements & Download Installation Configuration Note Any links provided in this appendix were current as of the time of this writing. Microsoft and other vendor sites change URLs without notice; therefore, be prepared to use an online search engine if a link fails. Requirements & Download Requirements for SQL Server 2005 Express Make sure to visit Microsoft s Web site and verify you have met all the requirements needed to install and run this application: requirements.aspx Download SQL Server 2005 Express After the requirements have been met, download the SQL Server 2005 Express Edition SP4 from Microsoft s site: Microsoft has two versions: one is for 32 bit versions of Windows, and another is for 64 bit versions of Windows. Make sure you download the correct version for your edition of Windows. Release

76 Appendix A Installation This chapter was written with screen shots from the 32 bit version of SQL 2005 Express. The install process for the 64 bit version of SQL 2005 Express is the same. When you download the files mentioned above, do not run the installation from the Microsoft site. You should save the files first, then run/open the files for installation. To install SQL Server 2005 Express Edition, perform the following steps: 1. Locate the file you downloaded in the previous section (for example, SQLEXPR32.EXE). 2. Double click the downloaded file to launch the SQL Server installation. The Windows operating system displays the following warning: Figure 56: Open File - Security Warning dialog It is safe to continue the installation. 3. Click the Run button. The installation program displays the End User License Agreement page in the Microsoft SQL Server 2005 Setup dialog: 76 Millennium 3 Installation

77 Installing SQL Server 2005 Express Edition SP4 Figure 57: End User License Agreement dialog 4. Read and accept the license agreement to continue. 5. Click the Next button. The installation program displays the Installing Prerequisites page, as shown in Figure 58: Figure 58: Installing Prerequisites page 6. Click the Next button. The installation program scans your system s configuration, then displays the Welcome page: Release

78 Appendix A Figure 59: Welcome page 7. Click the Next button. The installation program searches your system for potential problems, then displays the System Configuration Check page: Figure 60: System Configuration Check page 8. Each line should have a status of Success. If not, you should read the message(s) and fix the problems before continuing. Once any problems are fixed, proceed to the next step. 9. Click the Next button. The installation program displays the Registration Information page: 78 Millennium 3 Installation

79 Installing SQL Server 2005 Express Edition SP4 Figure 61: Registration Information page 10. Enter the appropriate information in the Name and Company text fields. 11. Ensure the Hide advanced configuration options check box is empty. 12. Click the Next button. The installation program displays the Feature Selection page: Figure 62: Feature Selection page 13. Click on the X icon next to Connectivity Components. 14. Select the Will be installed on the local hard drive option to leave the defaults: Release

80 Appendix A Figure 63: Feature Selection page You should see the following in the dialog: Figure 64: Feature Selection page 15. Click the Next button. The installation program displays the Instance Name page: 80 Millennium 3 Installation

81 Installing SQL Server 2005 Express Edition SP4 Figure 65: Instance Name page This screen allows you change the name of the SQL Server instance. This can be helpful if you already have a previous version of SQL installed on the same machine. The server name that appears when you run Millennium Server Setup to connect to the database (Chapter 3, Installing Millennium 3 ) depends on the option you select on this page. If you select the: Default instance option (the default value), the server name will appear as the COMPUTER name Named instance option (as in Figure 65 above), the server name will appear as COMPUTER\SQLEXPRESS (or COMPUTER\<whatever you type in the text box>) In this example, the instance is named SQLExpress2005. You can normally use the default selection. 16. Click the Next button. The installation program displays the Service Account page: Release

82 Appendix A Figure 66: Service Account page 17. In most cases, you can leave the Service section setting as the default option of Use the built-in System account, unless otherwise requested to do so. The only other account type that should be used is a local or domain administrator account. 18. Ensure you put a check mark in the box under the Start services at the end of setup section (as in Figure 66 above). 19. Click the Next button. The installation program displays the Authentication Mode page: Figure 67: Authentication Mode page 82 Millennium 3 Installation

83 Installing SQL Server 2005 Express Edition SP4 20. Select Mixed Mode in the top section. 21. Enter an sa (system administrator) password in the two text fields in the lower section. WARNING It is very important to remember this password. The password should have a mix of letters and numbers. 22. Click the Next button. The installation program displays the Collation Settings page: Figure 68: Collation Settings page 23. Use the default settings (don t change them). 24. Click the Next button. The installation program displays the Configuration Options page: Release

84 Appendix A Figure 69: Configuration Options page 25. Remove the check mark from the Enable User Instances check box. 26. Click the Next button. The installation program displays the Error and Usage Report Settings page: Figure 70: Error and Usage Report Settings page 27. Use the default settings (don t change them). 28. Click the Next button. The installation program displays the Ready to Install page: 84 Millennium 3 Installation

85 Installing SQL Server 2005 Express Edition SP4 Figure 71: Ready to Install page 29. Click the Install button. The installation program displays the Setup Progress page. Once the installation has completed, it displays the following: Figure 72: Setup Progress page 30. Click the Next button. The installation program displays the Completing Microsoft SQL Server 2005 Setup page: Release

86 Appendix A Figure 73: Completing Microsoft SQL Server 2005 Setup page 31. Click the Finish button. Configuration This section is especially important if you will have more than one computer accessing the Millennium database. After the installation, perform the following steps: 1. In Windows, select Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager. The system displays the SQL Server Configuration Manager window. 2. In the left pane, expand SQL Server 2005 Network Configuration. 3. Highlight Protocols for SQLEXPRESS (or whatever you named the instance). In this example, the instance is named SQLExpress2005, so the selection that is highlighted is Protocols for SQLEXPRESS Highlight and right click TCP/IP. 5. Select the Enable option (as shown in Figure 74) to enable access via TCP/IP: 86 Millennium 3 Installation

87 Installing SQL Server 2005 Express Edition SP4 Figure 74: SQL Server Configuration Manager window Once you have enabled TCP/IP, you must restart both SQL Server services. 6. In the left pane, expand SQL Server 2005 Services. 7. Highlight and right click SQL Server Browser. 8. Select the Start option (as shown in Figure 75) to start the service: Figure 75: SQL Server Configuration Manager window 9. Highlight and right click SQL Server (SQLEXPRESS) (or the named instance). 10. Select the Restart option to restart the service. Release

88 Appendix A Once both services have restarted, your window should look like the example in Figure 76: Figure 76: SQL Server Configuration Manager window Note The default Start Mode setting for SQL Server Browser is Manual. To change it, rightclick on that line, select Properties > Service tab, then select Automatic from the Start Mode drop down list. 11. You are finished with the SQL Express installation and can close the SQL Server Configuration Manager. 12. Once all SQL Express components have been installed and configured, you should reboot the computer where you installed SQL Express, if possible. 88 Millennium 3 Installation