How to Install Microsoft Office 2000 Server Extensions (216926)

MORE INFORMATION

IMPORTANT: If you are using an existing SQL Server, you must do the following BEFORE installing the Office 2000 Server Extensions:

1. Use SQL Server 6.5 or later.
2. Log in to Windows NT as the Administrator.
3. Create a SQL Database (including Name and Password of Administrator).

Note: To install the Office 2000 Server Extensions, you MUST be logged onto the server locally as the local Administrator (not a user with Administrator permissions).

1. Insert the Microsoft Office 2000 CD #3 into your CD-ROM drive. Alternatively, you may browse to G:\Setupse.exe (where G:\ is your CD-ROM drive) to begin the installation.
2. From the startup screen, click Install Microsoft Office Extensions.
3. In the Office Server Extensions User Information dialog box, type your user name and organization (if applicable), and then click Next.
4. Read and accept the End User License Agreement (EULA), and then click Next.
5. In the Install Office Server Extensions here: text box, confirm the correct path to which you are installing the server extensions.
   
   The default path is C:\Program Files\Microsoft Office.
6. Click Install Now at the top of the dialog box.
7. The Office Server Extensions Installation program then determines if you have a database engine to use as a discussion and notification server.
   
   If you do NOT have SQL Server 6.5 or later installed, the Office Server Extensions Installation program installs the Microsoft Data Engine (MSDE) for you. MSDE is a scaled-down version of SQL Server 7.0, which provides you with the discussion and notification functionality. MSDE creates a collaboration database for you.
   
   After the server and the database are set up, Office Server Extensions Installation needs to configure your extensions.
8. Click Configure to configure the Office Server Extensions.
9. When the Server Extensions Configuration Wizard appears, click Next to continue.
10. In the Web Collaboration Database dialog box, configure your SQL Server or MSDE database to be used for Discussions and Subscription Notifications.
    
    If you have SQL Server 6.5 or later installed, the setup program prompts you for the name of an existing database to use. If you have not created a database for discussions and notifications, you must exit setup at this time, create a BLANK database with a user name and password, and then run setup again. Otherwise, point to your pre-existing BLANK database. Documentation on creating new database is pending. When you use the default MSDE, the database is named <ServerName>_Collab (where <ServerName> is the name of your Web server.) You can change this name to be anything you want. When you use SQL Server 6.5 or higher, the database name is blank by default. You need to point to an existing database at this time.
    
    NOTE: Microsoft does NOT recommend using the master database as your collaboration server.
    
    
11. When you use SQL Server 6.5 or higher, the database name is blank by default. You need to point to an existing database at this time.Type a password for your database. The Administrator uses this password to gain access to the database for maintenance purposes. When you have added the appropriate password, click Next.
12. When you use SQL Server 6.5 or higher, the database name is blank by default. You need to point to an existing database at this time.You are now able to configure your Windows NT Groups to be used by the discussion server. This stage allows the Office Server Extensions Installation program to create four levels of access to discussions and notification servers:
    • Administrators - Administer discussions, subscriptions, permissions, and Webs.
    • Authors - Able to post discussions, subscribe to documents, and author webs.
    • Browsers - browse to the server's content.
    • Collaborators - Able to post discussions, subscribe to documents, and browse the server's content. The names of the Windows NT Groups begins with your server Name.
      
      For example: Server_Administrators, Server_Authors, etc)
      
      All of these groups (with exception of Collaborators) are empty by default, and must be populated manually by the Server Administrator. Click Next to continue.
    
    
13. When you use SQL Server 6.5 or higher, the database name is blank by default. You need to point to an existing database at this time.Configure Access Control to your server. It is recommended that your Server_Administrators group account administer the Office Server Extensions.
    1. Type the name of that account (given in step 12 above) in the appropriate box.
       
       As the administrator, you have to populate the groups created in the previous steps with Windows NT user accounts, using User Manager for Domains.
    2. Allow Basic Access ONLY if browsers in your intranet are using browsers OTHER than Microsoft Internet Explorer, or if they are gaining access to the server through a firewall.
    3. Enable Directory browsing so that your users can see the Office Server Extensions Start Page, and then click Next.
14. When you use SQL Server 6.5 or higher, the database name is blank by default. You need to point to an existing database at this time.Set up your SMTP Mail server for use with Office Server Extensions. This is primarily used by the Email Notification Service.
    1. Type the e-mail account that you wish to appear as your server's sending account.
    2. Type the e-mail account of the person to contact with problems.
    3. Type a valid Fully Qualified Domain Name (FQDN) or IP Address for your SMTP server, and then click Next.
       
       Note: The FQDN or IP Address entered here must point to an Exchange server or SMTP server on your LAN or WAN. If you are not certain what this FQDN or IP Address is, please consult your Mail Administrator.
15. When you use SQL Server 6.5 or higher, the database name is blank by default. You need to point to an existing database at this time.Click Finish to complete the installation. The Office 2000 Server Extensions are now installed on your server. A confirmation dialog box appears stating that the installation has been completed successfully.