Software infrastructure installation for Component Engineers Workstation

Overview

This document describes the software infrastructure required to build a Component Engineers box.

Last Updated: 6/10/2000

This consists of installing

Base build of Win2K Advanced Server including HiEncryptionPack, WinZip and Adobe Acrobat Reader
SQL Server 7.0
Office 2000
Site Server 3.0
Commerce Server 3.0
Visual Studio 6.0
Commerce Interchange Pipeline Manager
Win2k SP1

Pre-Installation Suggestions

Site Server 3.0 requires Windows 2000 server, Advanced Server, or Data Centre
Do not install Site Server 3.0 on Windows 2000 Professional
Do not install Site Server 3.0 on a computer functioning as a Backup Domain Controller (BDC). (Q184760)
Do not install Microsoft Exchange Server on a computer with Site Server installed. Because both server products are resource intensive, performance decreases greatly when these products are installed on the same computer. In addition , Site Server 3.0 and Exchange Server compete for the same TCP ports (389 and 25). Note that this does not apply to a Back Office Small Business Server 4.5 installation of these products. Q230735, Q229758
Do not install Site Server 3.0 on a computer running Microsoft Cluster Service (MSCS). You can however install Site server onto Windows NT Load Balancing Service (WLBS). Q228999
Do not install SQL Server on a computer running WLBS. You can however install SQL Server on a computer running Microsoft Cluster Service (MSCS)
Do not change any default settings in Microsoft Internet Information Server (IIS) before you install Site Server (on a new installation). In particular, do not disable NTLM support, change IP binding from "all unassigned", or change port 80 on the Default Web Site. Q234519
Ensure that the root of the installation drive for Site Server 3.0 has NTFS permissions of at least Everyone - Read. If you need to change this setting for security purposes, you can change it when Site Server 3.0 is successfully installed, but do not replace permissions on subdirectories.
At this time, Microsoft Commercial Internet System (MCIS) is not compatible with any version on Windows 2000
Do not use computer-cloning software to create a Site Server computer. Some of the Site Server components install computer-specific information that cannot be cloned.
You can install Site Server 3.0 onto a Windows 2000 computer running Terminal Services.

1. Install Microsoft Windows 2000

Install Windows 2000 as a stand alone server
Install Winzip and Adobe Acrobat Reader
Install HiEncryption Pack
Install the Indexing Service
Install IIS 5.0

Install the FrontPage 2000 Server Extensions for integration of SourceSafe with Visual Studio
Install SMTP
Leave all sample web sites as developer resources.
Leave all unnecessary application mappings as these workstations are sitting behind a firewall and developer may need them at some later stage.

Do not substitute Windows 2000 SP1 at this stage

2.Install Microsoft SQL Server 7.0 Enterprise Edition

3. Install SQL Server 7.0 Service Pace 2. (Q254561)

4. Configure the SQL Server client Default Network Library to Named Pipes.

In this configuration SQL Server is installed on the same computer as Site Server. Therefore, the SQL Server default Network Library should be set to Named Pipes. This step is different from the instructions for a computer running Site Server without SQL Server installed. To ensure that the default Network Library is set to Named Pipes, run the SQL Server Client Network Utility. On the Net Library tab, select "Named Pipes" as the Default Network. Click Done. IIS should now use Named Pipes when connecting to SQL Server.

5. Verify that the MSDTC service is started and that MSDTC is configured to start automatically. (Q222000)

6. IMPORTANT: Before you install Site Server 3.0, run Ss3w2k.exe file. This program is included in Site Server Service Pack 4

This program executes quickly. It does not explicitly tell you when its finished executing. This program prepares Windows 2000 for Site Server 3.0.
The Ss3w2k.exe file allows Site Server to work with the FrontPage 2000 Server Extensions.
It is safe to run the Ss3w2k.exe file multiple times if you are unsure that the file has executed.
If you do not run the Ss3w2k.exe file prior to installing Site Server 3.0, you will experience the problem described in Q243564

7. Install Office 2000

If you are installing Office 2000 on this computer, you must install it before Site Server 3.0. Office 2000 removes the FrontPage registry entry that Site Server 3.0, Commerce Edition needs to successfully run the Site Foundation wizard. Q248625

8. Install Site Server 3.0

Insert the Site Server 3.0 cd and double-click on setup.exe. Setup wizard starts and choose Server Installation
When you are prompted with a dialog box stating "This program does not run correctly on this version of Windows" click Run Program to continue installing.
Select Features screen appears, Uncheck just Analysis component and leave defaults. It will install Site Server's Publishing, Push and Search Services and P&M.
Install sample sites
IMPORTANT: When you are prompted to overwrite existing files, click "No to All". Windows 2000 installs newer versions of some DLL files. The Site Server 3.0 Setup program attempts to overwrite those DLL files.
Do not create new membership instances prior to installing Site Server 3.0 Commerce Edition, because the Trey Research Web Site will not install or configure correctly.

9. Install Commerce Server

Create individual databases for Ad Server or Commerce Server, respectively. The databases may reside on different database servers or share the same server.
Create a System DSN for the Ad Server and/or Commerce Server databases. When you create each DSN for Ad Server or Commerce Server, do the following
- Use SQL Server standard authentication rather than Windows NT authentication.
- Specify a SQL Server account with at least DBO rights.
- Do not use the default master database. Specify the corresponding database for each DSN
- During the installation of Commerce Server, the following two error messages occur. Q241833
```
    File(s) failed to self-register.
    D:\Microsoft Site Server\Bin\Xenroll.dll
    
    Cannot set attribute description
    Details:
    Error:80071392
```
  These error messages can be ignored. Site Server 3.0, Commerce Edition will install correctly with these error messages.

10. Install Visual Studio

Do not install Visual Studio 97 on a computer running Windows 2000.

11. Apply Visual Studio 6.0 Service Pack 3

12. Install Site Server Service Pack 4

13. Install the Commerce Interchange Pipeline Manage (CIPM) for Site Server 3.0, Commerce Edition

14. Re-apply Site Server 3.0 Service Pack 4

15. Apply Windows 2000 SP1

Post-Installation Suggestions

Remove the SQL Server TCP/IP sockets Net Library DBmssocn.dll file from the WinNT\System32\Inetsrv directory. The latest version of DBmssocn.dll is located in the WinNT\System32 directory (Q253272)
Configure database connectivity.
- It is not necessary to create a database or DSN for Personalization and Membership (P&M). If you choose to create a SQL Server-based membership instance after you install Site Server, create your database prior to setting up the membership instance.
Follow the steps in Q226474 to enable "Parent Paths" in IIS 5.0 if our applications depend on it

If you do not enable the Parent Paths option, you must edit the Site Server Web Administration Pages per the instructions in the Site Server 3.0 Service Pack 4 Readme file (Readme_sp4.htm)

If you installed Site Server 3.0, Commerce Edition, replace the Account.asp, Directory,asp Finish.asp and Setup.vbns files as specified in the Readme_sp4.htm file. The Readme_sp4.htm file is included with Site Server 3.0 Service Pace 4.
If you installed Commerce Server, use the Site Server Microsoft Management Console (MMC) to access Commerce Host Administration, Remove ":80" from the non-secure host name field and ":443" from the secure host name field for all sample stores. Repeat this procedure for all stores that you create.
If you have not customized any of the CMSample of FPSample .prf rule set files, update the CMSample and FPSample rule set files Q188289
- Copy all the files and folders from the Microsoft Site Server\Sp4\Samples\CmSample directory to the Microsoft Site Server\Data\Publishing\CmSample directory to overwrite the existing files and folders.
- Copy all files and folders from the Microsoft Site Server\Sp4\Samples\FpSample directory to the Microsoft Site Server\Data\Publishing\FpSample directory to overwrite the existing files and folders.
If you have not customized any of the Search ASP pages, update the Search ASP pages:
- Copy all files and folders from the Microsoft Site Server\Sp4\Samples\Search directory to the Microsoft Site Server\Sites\Samples\Knowledge\Search directory to overwrite the existing files and folders.

Hosted by www.Geocities.ws