Share via

Installation Prerequisites

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Before installing any Office Developer components, verify that the configuration and software prerequisites are satisfied. There are three installations to review:

  • Server Prerequisites

  • Developer Workstation Prerequisites

  • End-User Client Computer Prerequisites

If you are using the Windows 2000 or Windows 95/98 operating systems, see Special Considerations When Using Windows 2000 and Special Considerations When Using Windows 95/98.

For additional installation and setup information, see the Readme files on the Microsoft Office Developer CD-ROM before installing any software or components.

Server Prerequisites

The Access Workflow Designer server components can be installed on a server when the following conditions are met.

  • You must have Microsoft Windows NT® Administrator permissions and SQL Server administrator permissions to install the server or developer components.

  • Set up one or more Windows NT domain user accounts. For more information, see Creating Accounts, Logins, Roles, and Users and the Windows NT documentation.

  • Back up your existing databases.

  • Shut down all services that depend on SQL Server. This includes any service that uses Open Database Connectivity (ODBC), such as Microsoft Internet Information Service (IIS).

Software Requirements

  • Windows NT 4.0 Server or Windows 2000 Server. NTFS partitioning recommended. Per seat mode required. For information about using Windows 2000, see Special Considerations When Using Windows 2000.

    Although NTFS is not required, it is recommended if you plan to take full advantage of security features. For more information, see in the Access Workflow Designer Developer's Guide.

    ****Note   ****Previous versions of MSDN Universal contain a version of Windows NT 4.0 Server that installs in per server mode only. This mode impacts SQL Server and interferes with the offline replication features of Access Workflow Designer. The per server setting can be changed to per seat using the License Manager tool available in Windows NT 4.0 from the Administrative Tools program group.

  • Windows NT Option Pack 4.

    Note   To use e-mail integration in your solutions, the Simple Mail Transfer Protocol (SMTP) service must be installed, and you must have an SMTP Smart Host.

    ****Note   ****If Microsoft Exchange Server is being used, the Exchange Server Internet Mail Service must be enabled.

  • Windows NT Service Pack 4 or later.

    Note   The service pack must be installed after the Windows NT Option Pack. If the service pack is already on your computer, you must reinstall the service pack after installing Windows NT Option Pack.

  • Microsoft SQL Server 7.0 (Standard or Enterprise) with Service Pack 1 must be installed with integrated security mode and in per seat licensing mode.

    Important   Access Workflow Designer does not work with the minimal installation of SQL Server.

    Note   Review the SQL Server 7.0 Service Pack 1 Readme to ensure any existing publications and subscriptions will continue to work after the upgrade.

  • Microsoft SQL Server and SQL Server Agent services must be configured to log in to a valid network domain account not to a local system account.

  • From the Microsoft Office 2000 Developer CD, minimally install:

    • Microsoft FrontPage® Server Extensions 4.0 or later (available on Office Developer CD in the FrontPage directory).

  • From the Microsoft Office 2000 Premium CD1, minimally install:

    • Microsoft Office 2000 Web Components (available from Office Tools option on Office 2000 CD). For details, see Setting Up Office Web Components on the Server.

    • Standard installation of Microsoft Internet Explorer 5.

      ****Note   ****Office 2000 has a new installation program. Many objects are set to install on first use. If you use a custom installation, these options are marked with a yellow 1.  If you want to install options during setup, click the option, and select Run from my computer.

After prerequisites are satisfied, install the Access Workflow Designer server components. For details, see Setting Up the Server.

Developer Workstation Prerequisites

To develop team solutions, you do not have to work directly on the production server. You can install the Access Workflow Designer development tools on any computer that has access to the server, or you can use the Microsoft Data Engine (MSDE) locally to emulate a server environment.

The Access Workflow Designer developer tools can be installed on a computer when the following conditions are met:

  • Verify that a server has been set up that meets the Access Workflow Designer server requirements.

  • The solution developer must be a member of the modAppOwner Windows NT group on the Access Workflow Designer server. This account provides the permissions required to create and to modify solutions. For more information, see Creating Accounts, Logins, Roles, and Users.

Software Requirements

It is recommended you install the prerequisites on the developer workstation in the following order:

  • Windows NT Workstation 4.0 with Service Pack 4.0 or later, Windows 95/98, or Windows 2000. For information about using Windows 95/98 or Windows 2000, see Special Considerations when Using Windows 95/98 and Special Considerations when Using Windows 2000.

  • Office 2000 Premium, minimally install:

    • Access 2000.

    • Office 2000 Web Components (available from Office Tools option on the Office 2000 CD).

    • The standard installation of Internet Explorer 5.

  • SQL Server 7.0 with Service Pack 1 or MSDE with Service Pack 1.

    Important   Access Workflow Designer does not work with the minimal installation of SQL Server.

    Install MSDE from either Office 2000 Premium or SQL Server 7.0 installation CD-ROMs. Do not use the redistributable version of MSDE provided on the Microsoft Office Developer CD.

    • To install MSDE from Office 2000 Premium, from the Office 2000 CD-ROM, locate the MSDE Setup program: Sql\X86\Setup\Setupsql.exe.

    • For information about using MSDE on a computer running Windows 95/98, see Special Considerations When Using Windows 95/98.

      ****Note   ****Although FrontPage 2000 is not a required prerequisite, it is recommended you install it to create Web sites for your team solution.

When all prerequisites are met, install Access Workflow Designer developer tools. For details, see Setting Up the Development Computer.

End-User Client Computer Prerequisites

For a user to access a team solution and take the solution offline, the client computer must have the required software components installed. The Access Workflow Designer client components can be installed on a computer when the following conditions are met:

  • Verify that the server Setup is complete and the client Setup program is available to the users on the server. For details, see "Notes to Administrators" in Setting Up the End-User Client Computer.

  • Ensure the user who installs the end-user client components on a computer is the only user who can take a solution offline on that computer.

Software Requirements

  • Windows NT Workstation 4.0 with Service Pack 4.0 or later, Windows 95/98, or Windows 2000. For information about using Windows 95/98 or Windows 2000, see Special Considerations When Using Windows 95/98 and Special Considerations When Using Windows 2000.

  • Office 2000 Premium, minimally install:

    • Office 2000 Web Components (available from Office Tools option on Office 2000 CD).

    • The standard installation of Internet Explorer 5.

    Data access pages depend on the Office Web Components. If users do not have the Office Web Components installed and they start a team solution that includes data access pages that have automatic downloading enabled, the Web Components are downloaded. For more information about the Office Web Components, see Setting Up Office Web Components on the Server.

For details about installing the client components, see Setting Up the End-User Client Computer.