microsoft.com Home  
Microsoft
http://www.microsoft.com/office/ork  
Microsoft Office 2000 Resource Kit Home
 Office 2000 and the Web
 Integrating Office 2000 with Your Intranet
Using Office with a Web Server
Using Office Documents in a Web World
Managing Communications on Your Intranet
Broadcasting PowerPoint Presentations over the Network
Managing Web Sites on Your Intranet with FrontPage
 Using Office Server Extensions
 Overview of Tools and Utilities
Glossary
Index
Broadcasting PowerPoint Presentations over the Network

Maintaining Presentation Broadcasting

A presentation broadcast on your network requires minimal ongoing maintenance. Two maintenance issues to consider are removing unnecessary files from shared broadcast folders and keeping client computer clocks synchronized with NetShow servers.

Cleaning up broadcast folders

Most Microsoft PowerPoint presentation files and streamed presentation broadcasts take a large amount of disk space. You can monitor the space these files use in the shared locations for broadcasts and archiving; and you can restrict broadcast file locations to a set of default folders so that you know which servers and folders to monitor.

For archive folders, ensure that ample disk space is available for users to archive broadcasts. Use the following usage rates to estimate the amount of disk space that users need.

Stream type and rate Archive rate
Audio only at 28.8 kilobits per second (Kbps) 165 kilobytes (KB) per minute
Audio only at 56 Kbps 420 KB per minute
Audio and video at 100 Kbps 750 KB per minute

For example, a half-hour broadcast with audio and video takes about 22 megabytes (MB) of disk space.

Top

Keeping client clocks synchronized with the server

The presentation broadcast lobby page has a remaining-time display that relies on the client system clock and on the scheduled start time of the broadcast. If the client system clock is not synchronized with the server clock, the remaining-time display on the lobby page is not accurate.

Typically, system clocks across a network vary by plus or minus five minutes. This error range can cause a discrepancy of up to ten minutes between a server and clients. If you do not have a solution in place to synchronize system clocks across your network, consider using the net time command in user logon scripts — to synchronize the server clock with client clocks when users log on.


Topic Contents
Next
Previous

Topic Contents   |   Previous   |   Next   |   Top

  Friday, March 5, 1999
© 1999 Microsoft Corporation. All rights reserved. Terms of use.

License