The Deep description on Windows Services
We have tried our best efforts to explore the deepth of windows services and all the given information is gathered from Microsoft notes (As its microsoft product)
|
| 122. Service Name:-WMServer |
| Executable Name:-WMServer.exe |
| Log On As:-NetworkService |
Description:-Provides streaming media services over IP-based networks.
The Windows Media Service replaces the four separate services that comprised Windows Media Services versions 4.0 and 4.1: Windows Media Monitor Service, Windows Media Program Service, Windows Media Station Service, and Windows Media Unicast Service. Windows Media Services is now a single service that runs on Windows Server 2003, Standard Edition, Enterprise Edition, and Datacenter Edition. Its core components were developed using the Component Object Model (COM), creating a flexible architecture that is easily customized for specific applications. It supports a greater variety of control protocols, including Real Time Streaming Protocol (RTSP), Microsoft Media Server (MMS) protocol, and Hypertext Transfer Protocol (HTTP).
The Windows Media Service platform is compliant with the following industry standards:
- Windows Management Instrumentation (WMI) for server event notification and messaging.
- Simple Network Management Protocol (SNMP) for networking components.
- Extensible Markup Language (XML), Synchronized Multimedia Integration Language (SMIL) 2.0, and the Document Object Model (DOM) for playlist implementation.
- Moving Picture Experts Group (MPEG) 1 and 2 for audio and video formats.
Most streaming scenarios can be accomplished using the core components installed with Windows Media Services. However, more advanced scenarios may require that you incorporate some custom programming and integration work. For developers and systems integrators, the Windows Media Services Software Development Kit (SDK) provides access to all elements of the server through a combination of plug-ins, a fully documented object model, and a rich set of external event notifications, all designed to be easily customizable.
If this service is stopped, streaming media services will not be available.
|
| Avaliable on OS:-Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition. |
| Installed through:-Add/Remove Programs, Add/Remove Windows Components, Windows Media Services or Configure Your Server, Manage Your Server |
| Startup type:-Automatic |
| Service status:-Started |
| This service depends on the following system components:-Remote Procedure Call |
| The following system components depend on this service:- None |
| Port Numbers used:-TCP: 1755 (MMS), 554 (RSTP), 80 (HTTP), 135 (DCOM, WMI)
UDP: 161 (SNMP), 1755 (MMS), 135 (DCOM, WMI)
|
|
| 123. Service Name:-WindowsSystemResourceManager |
| Executable Name:-Wrm.exe |
| Log On As:-LocalSystem |
Description:-: The Windows System Resource Manager (WSRM) service is a tool to help customers deploy applications into consolidation scenarios. It provides policy-based management of CPU and memory consumption of processes running on a single operating system instance. Planned scenarios include multiple heterogeneous server applications, multiple Terminal Services users, multiple SQL server instances, multiple Internet Information Server (version 6) application pools or Exchange and IIS6 running together on the same machine.
WSRM enables a system administrator to do the following:
- Set CPU and memory allocation policies on applications. This includes selecting processes to be managed, and setting resource usage targets or limits.
- Manage CPU utilization (percent CPU in use).
- Limit the process working set size (physical resident pages in use).
- Manage committed memory (pagefile usage).
- Apply policies to users or groups on a Terminal Services application server.
- Apply policies on a date/time schedule.
- Generate, store, view, and export resource utilization accounting records for management, service level agreement (SLA) tracking, and charge-back purposes.
WSRM maintains an updatable exclusion list of processes that shouldn't be managed because of the negative system impact such management could create. WSRM also applies limits to process working set size and committed memory consumption. WSRM does not manage address windowing extensions (AWE) memory, large page memory, locked memory, or OS pool memory. Primary option for CPU management is bandwidth targets (expressed as a % of system CPU). Targets are maintained by dynamically monitoring and adjusting process priorities. WSRM also provides affinity management which is provided using per-process APIs for hard affinity.
Memory management options include working set limits and committed memory maximum applied per-process. Working set limits are set in policy and applied by WRM via a kernel API. Subsequently, the kernel memory manager will apply and maintain the limits on working set size by paging the process as necessary. Committed memory is simply monitored against an upper limit. When the upper limit is exceeded the process is terminated, or an event is logged (at the users discretion).
Additional features include: full calendar features for scheduling desired policies, sophisticated pattern matching for identifying processes at runtime, WSRM-specific counters, and a basic job accounting system.
WSRM is implemented in a service which must be installed on each managed machine. For administration of the service, an MMC snap-in and command line programs are provided. These client pieces may be installed and run on any Win2K, XP Professional, or system. The service may only be installed and run on Windows Server 2003, Datacenter and Enterprise Edition. |
| Avaliable on OS:-Windows Server 2003, Enterprise Edition and Windows Server 2003, Datacenter Edition. |
| Installed through:-Windows System Resource Management CD or download from Web |
| Startup type:-Automatic |
| Service status:-Started or Stopped, based on user checkbox in setup |
| This service depends on the following system components:-Remote Procedure Call |
| The following system components depend on this service:- None |
| Port Numbers used:-None |
|
| 124. Service Name:-W32Time |
| Executable Name:-svchost.exe -k netsvcs |
| Log On As:-LocalSystem |
Description:-The Windows Time service maintains date and time synchronization on all computers running on a Microsoft Windows network. It uses the NTP (Network Time Protocol) to synchronize computer clocks so that an accurate clock value, or timestamp, can be assigned to network validation and resource access requests. The implementation of NTP and the integration of time providers make W32Time a reliable and scalable time service for enterprise administrators. For computers not joined to a domain, W32Time can be configured to synchronize time with an external time source. If this service is turned off, the time setting for local computers will not be synchronized with any time service in the Windows domain, or an externally configured time service.
If this service is stopped or disabled, date and time synchronization will be unavailable in the forest or an external NTP server. Stopping W32time on a workstation prevents the workstation from synchronizing its time with another source, but has no effect on any other external server. Stoppingw32time on a domain controller will have the same effect as in #1, but will also prevent any domain members from synchronizing time with it. This may adversely impact time synchronization.
|
| Avaliable on OS:-Windows XP Home, Windows XP Professional; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition and Windows Server 2003, Web Edition. | | Installed through:-Default operating system installation |
| Startup type:-Automatic |
| Service status:-Started |
| This service depends on the following system components:-None |
| The following system components depend on this service:-Cluster Service |
| Port Numbers used:-TCP: 123 (NTP port) |
|
