Microsoft FrontPage 2000 Server Extensions Resource Kit

Advanced Administrative Tasks

Installing Microsoft Visual SourceSafe for Use with FrontPage

Integration with Microsoft Visual SourceSafe versions 5.0 or later is available on all FrontPage-supported Web servers on Microsoft® Windows NT® Server 4.0 or later, Windows NT Workstation 4.0 or later, and Windows® 95/98.

On Windows 95, the Microsoft Personal Web Server requires the Windows 95 Distributed Component Object Model (DCOM) update to work with Visual SourceSafe. For information, see http://www.microsoft.com/com/dcom/dcom1_2/default.htm .

Enable SourceSafe Integration

To use Visual SourceSafe with FrontPage you must choose Enable SourceSafe Integration during Visual SourceSafe setup:

1. Run the Visual SourceSafe installation program, Setup.exe, from the Visual SourceSafe CD.
2. Select the Custom installation option.
3. In the Visual SourceSafe Custom dialog box, click the Enable SourceSafe Integration check box.
4. Click Continue.

Your Visual SourceSafe configuration

You can store your Visual SourceSafe database on the same computer as the Web server (a local database) or on a different computer (a remote database). 

While it is possible to configure the Visual Source Safe database on a separate computer from the Web server, it is not considered a common scenario and may not work in all circumstances.

If the database is on the same computer as the Web server but is accessed using UNC paths, the database is considered to be remote. For example, the following database is remote because the Srcsafe.ini file on the IIS computer has one of the following lines:

Data_Path = X:\vssdata

Data_Path = \\IIS-Machine\vssdata

You can also view the registry to find out whether the database is accessed with UNC or mapped paths.

You should note which configuration you have, because if you are using a remote database, you will need to complete a few extra steps.

Visual SourceSafe INI file

FrontPage Server Extensions must find a Srcsafe.ini file to perform Visual SourceSafe operations through OLE automation. Visual SourceSafe 5.0 usually uses the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SourceSafe\SCCServerPath. While this key points to the Ssscc.dll in the VSS\Win32 directory, the FrontPage Server Extensions will use the Srcsafe.ini file in the VSS directory. Visual SourceSafe 6.0 normally uses the Srcsafe.ini file in the Web server's installation of Visual SourceSafe.

The following procedures assume that the Web server is IIS running on Windows NT 4.0, that the Visual SourceSafe database is also on a Windows NT 4.0 computer, and that both are on NTFS partitions.

Visual SourceSafe directory permissions

You must set permissions on the Visual SourceSafe directory structure and files.

If you are using a remote Visual SourceSafe database, you must complete the following additional steps.

WWW Service properties

You must set the WWW Service properties on the Web server computer.

1. In the Internet Service Manager, open the Internet Information Server folder, right-click the Web server, and then click Properties on the shortcut menu.
2. In Master Properties, click WWW Service, and then click Edit.
3. Click the Directory Security tab, and then under Anonymous Access and Authentication Control, click Edit.
4. Select the Basic (Clear Text) check box and clear the Windows NT Challenge/Response check box.

Windows NT Challenge/Response is also known as NTLM. Because this option is not selected, users must type their user name and domain password when they open a Web. Use the format DomainName\UserName for the user name when working with multiple domains.

Allow Anonymous is optional.

Anonymous account permissions

If you are using an anonymous account (Allow Anonymous is selected in the procedure above), do the following on the computer with the Visual SourceSafe database:

1. In User Manager For Domains, on the User menu, click New User to add the Web server's anonymous account. For example, if the anonymous account on the Web server is IUSR_WEBSRV, add that user as a local account.
2. Give the account the same password as it has on the Web server.
3. Click OK.
4. Under Username, click the anonymous account.
5. On the Policies menu, click User Rights.
6. From the Right list, click Log on locally. Make sure that the anonymous account is listed in the

   Grant To box individually or as a member of one of the groups, and then click OK.