The information in this article applies to:
SUMMARYThis article describes some of the ways you can use Site Server Deployment in conjunction with the FrontPage Server Extensions. MORE INFORMATION
The biggest obstacle here is the fact that FrontPage locks files when they are in use. Site Server 3.0 offers the ability to skip locked files, but there is a chance that the locked file is an important one. It is preferable to have the deployment take place during a time when usage is low (for example, the middle of the night) in order to minimize the number of locked files. To improve things, you can run a batch file that stops and restarts the services on the source server before the replication. This will also help with the locked files.
Fpsrvadm.exe -o recalc -p 157.57.144.146:80 -m sample.microsoft.com -wFor more information regarding this utility and its uses, please see the online Server Extensions Resource Kit at the following location: http://officeupdate.microsoft.com/frontpage/wpp/serkNote: FrontPage is not designed to be used this way and there may be some problems with certain features of FrontPage (themes, shared borders, and navigation structure) when using Site Server to move the content. The best way to move FrontPage managed content is to use the Publish feature in the FrontPage Client. This article is only intended to give you a starting point for you own experiments. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: Q239833 How to configure FrontPage Authoring with Site Server Membership Additional query words: front page
Keywords : fpse2000 |
Last Reviewed: October 20, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |