Site Server 3.0 Content Deployment FAQ

ID: Q181162

The information in this article applies to:
Q: Why do I need Publishing?

A: To provide a way to deploy content to mirror servers through a reliable and secured file transfer.

Q: Show me how Publishing works!

A: On the Microsoft Management Console (MMC), use the Project Wizard to start Publishing. Please also refer to the online documentation.

Q: How do I troubleshoot Publishing problems?

A: Event Viewer and Event Reports in the MMC provide an instance error reporting. You can also turn on FullLogging for more detailed error logging.

Q: My project is frequently aborted due to file locking. How can I set Publishing so that it ignores the locked files?

A: You can set the SkipLockedFiles to Yes through the Command Line Interface (CLI) or the MMC. This is a new feature that is not available on the previous version.

Q: Publishing seems to delete files on the endpoint server. How can I prevent this from happening?

A: Select "preserve content on destination" in the MMC, or set the /nodelete switch in CLI.

Q: Can Publishing set a virtual directory for me automatically?

A: The easiest way to set this up is using the MMC, where you can set this option in the IIS tab menu. The virtual directory setting is set on the endpoint server.

Q: Can I deploy component or applications?

A: Publishing allows you to deploy component. Please consult the documentation for more information about deploying component.

Q: I don't need to deploy the graphics-related files such as .bmp or .gif. Can I exclude these files?

A: You can exclude multiple directories and different file extensions.

Q: I want to run certain scripts after the replication is completed. How can I do that?

A: Publishing allows you to run a script before or after replication is sent or received.

Q: I am replicating ACLs (permission) and I notice it's running very slow, why?

A: Deploying ACLs is slow because the replication process needs to communicate with the domain controller. If possible, you can select the "deploy directory ACLs only and apply to files" option, or change the ACLs to only contain local group instead of domain users/group.

Q: How can I delegate some tasks such as starting deployment but limit other administrator functionality to a certain group of users?

A: You can control the granularity of permission through the Security tab in MMC.

Q: How do I use Publishing to replicate over the Internet from our intranet?

A: You have to open port 507 on the firewall before you can replicate over the Internet. You can assign different port if port 507 is not available.

Q: How do I deploy my content from a Web server that doesn't have Publishing installed?

A: You can use Publishing on the endpoint server and take advantage of Internet Retrieval feature of Publishing. Internet Retrieval pulls the content from a Web server that doesn't have Publishing installed.

Q: How do I "undo" a deployment?

A: You can accomplish this by doing a "rollback"

Q: How many types of scheduling I can use with Publishing?

A: You can set the Publishing project to be "automatic", deploy the content at a specified period, schedule apply at a specified period and manual deployment.

Q: What is "Schedule Apply"?

A: "Schedule Apply" allows you to deploy the content to the endpoint now, but the content is not available on the directory until you apply the content at a specified time or apply the content using "crs apply" command.

Q: How can I use Publishing to deploy to 20 servers that need various content deployments?

A: You can set up a route that defines the path of the endpoint servers and use this route for all the subsequent projects. The projects then will be created automatically for all the endpoint servers within this route.

Q: How do I monitor the deployment remotely?

A: You can set Publishing to notify you the results of the deployments through SMTP mail. You can also use Publishing WebAdmin to administer the project remotely.

Q: Which mode is better: fastmode or framemode?

A: If you do local deployment within an intranet, you can use fastmode. If you are deploying to the Internet, where you expect a lot of network link failures, use framemode.

Additional query words: 


Keywords          : 
Version           : WinNT:3.0
Platform          : winnt 
Issue type        : kbinfo

Last Reviewed: July 15, 1999