Product nomenclature for options
K2 Solo Media Server
nomenclature
K2 Summit Production
Client nomenclature
Option
NAK2-XDP-2SD, K2-XPD -4SDStandard
K2-SOLOK2-XDP-2HD, K2 -XPD-4HDWith HD license
NAK2-XDP-2SD-MPG,
K2-XPD-4SD-MPG
With MPEG card
K2- SOLO-MPEGK2-XDP-2HD-MPG,
K2-XPD-4HD-MPG
With HD license and MPEG
card
K2- SOLO-ELITEK2-XDP-2HD-AVCI,
K2-XPD-4HD-AVCI
With HD license and AVC-Intra
card
Managing the write filter
The following topics describe the K2 Summit Production Client and K2 Solo Media
Client write filter.
About the write filter
The K2 Summit Production Client and K2 Solo Media Server have a file-based write
filter, which is a feature of the Windows embedded operating system. With the write
filter enabled, files can be created, modified, and deleted, but these changes are held
in a memory cache. When the K2 system restarts, these changes are lost and the K2
system returns to its original state. This protects the K2 system from changes and
increases on-air reliability. For any system configuration change the write filter must
be disabled otherwise changes are lost at the next restart.
Some directories, such as C:\logs, C:\Profile\config, and
C:\Profile\ChannelSuites, are excluded from write filter protection, so that channel
configuration and logs are saved. Do not attempt to alter this list of excluded directories.
If you suspect that write filter configuration has been altered, use the recovery image
process to restore to the default configuration.
To enable the write filter, the K2 Summit Production Client or K2 Solo Media Server
must be restarted. Likewise, to disable the write filter, the K2 system must be restarted.
You can enable/disable the write filter remotely using the SiteConfig lock/unlock
feature on one K2 system at a time or on a group of K2 systems all at once. You can
also enable/disable the write filter from a local K2 system, but if you use the local
method, do not also use the SiteConfig method. If you enable/disable the write filter
locally, the change is not automatically sent to SiteConfig, so SiteConfig can not
reliably indicate the current lock/unlock state.
12 May 2010 K2 Version 7.2.7 Release Notes & Upgrade Instructions 95
Additional notes