Microsoft KB Archive/183743

= How to Install Content Management on a Different Virtual Server =

Article ID: 183743

Article Last Modified on 2/27/2002

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition

-



This article was previously published under Q183743



SUMMARY
This article explains how to install Content Management on a different virtual server.



MORE INFORMATION

 * 1) Install Site Server Publishing on your server.
 * 2) In Internet Information Server (IIS), create an alternate virtual server. The alternate virtual server requires a unique port and proper mapping of Membership authentication.
 * 3) On the virtual server, create the following virtual directories:


 * Scripts (for example, [DRIVE:]\Inetpub\scripts). Ensure that this path matches the path on the default virtual server. The script directory contains the upload control and Posting Acceptor files. You may also need to modify the property of your Posting Acceptor in Publishing property page.
 * SiteServer (for example, [DRIVE:]\Microsoft Site Server\SiteServer). Ensure that this path matches the path on the default virtual server.
 * Use Publishing MMC snap-in, select the property of the server
 * Select the Posting Acceptor tab menu.
 * Modify the script to reflect the proper port of your virtual server. For example, if the port is 5555 then modify the TargetURL from: TargetURL = Scheme + "://" + Request.ServerVariables("SERVER_NAME") + SitesURL + "/users/" + Request.ServerVariables("LOGON_USER") to: TargetURL = Scheme + "://" + Request.ServerVariables("SERVER_NAME") + ":5555" + SitesURL + "/users/" + Request.ServerVariables("LOGON_USER")

NOTE: Port 5555 is specified at this time.


 * 1) Open the Microsoft Management Console (MMC).
 * 2) Right-click on the virtual server, and then choose Task. Map the server to the desired LDAP server.
 * 3) On the command line interface, run Makecm.vbs with the parameters for creating the site. For example, cscript makecm.vbs /s:[server] /v:[vroot] /a:[app-name] /d:[application directory] /l:[ldap server]:[port] /i:[virtual server instance]

Example
Create a content store called MyStore on MyServer that runs the LDAP service on port 1002; the content store physical directory is located in d:\Microsoft Site Server\Data\Publishing\MyStore and the content store is located on a virtual server called MyStore.
 * 1) Copy all files from d:\Microsoft Site Server\Data\Publishing\Cmsample to d:\Microsoft Site Server\Data\Publishing\MyStore.
 * 2) Cscript Makecm.vbs /s:MyServer /v:MyStore /a:MyStore /d:"d:\Microsoft Site Server\Data\Publishing\MyStore" /l:MyServer:1002 /i:3

The virtual server called MyServer is on instance 3. The quickest way to find out the instance is to do the following:  Go to the virtual server properties. Select Property for Logging. The log file name is indicated as follows:

Log file name: W3SVC3\exyymmdd.log

The number after W3SVC indicates the virtual server instance.

Additional query words: website

Keywords: kbhowto KB183743

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.