July 28, 2008 K2 Media Client Service Manual 59
Services on a stand-alone storage K2 Media Client
If you suspect that services have been tampered with or for any reason are not set
correctly, you can check their current settings in the Windows Services Control Panel.
The table below provides the settings for the services that are critical to a correctly
operating K2 Media Client.
Services on a stand-alone storage K2 Media Client
When a stand-alone storage K2 Media Client is operating in the online mode, in the
Services control panel services appear as follows:
Service Status Startup
Type
Comments
Grass Valley AppService Started Automatic Depends on Status Server service
Grass Valley Catch Server Ingest
Engine
— Automatic Used with Capture Service features.
Grass Valley Catch Server Monitor
Host
— Automatic Used with Capture Service features.
Grass Valley File-Import Watcher
Service
— Manual Used with the HotBin feature.
Grass Valley FTP Daemon Started Manual Started by Status Server service on
stand-alone storage models
Grass Valley K2 Config Started Automatic Not used on a stand-alone storage
K2 Media Client
Grass Valley MegaRaid Server Started Manual —
Grass Valley Pathfire Bin — Automatic Used with the K2 Pathfire Capture
Service feature.
Grass Valley RTS Service Started Automatic —
Grass Valley Storage Utility Host Started Automatic —
Grass Valley System Status Server Started Automatic At startup the Status Server service
makes sure the following services
are started:
-AMP TCP Service
-AppService
-FTP Daemon
Grass Valley Transfer Queue Service Started Automatic —
Grass Valley XML Movie Importer — Manual Used with the K2 XML Import
Service feature.
Microsoft iSCSI Initiator Service Started Automatic Not used on a stand-alone storage
K2 Media Client
MSSQLSERVER Started Automatic The K2 software installation for
stand-alone storage clients sets
startup type to automatic.
MSSQLServerADHelper Manual —