Services Utility: System Event Notification Service
Display Name (?): | System Event Notification | ||||||||||||||
Short Name (?): | SENS | ||||||||||||||
Executable (?): | svchost.exe | ||||||||||||||
Library (?): | sens.dll | ||||||||||||||
Depends On (?): | COM+ Event System | ||||||||||||||
Supports (?): | None. | ||||||||||||||
Description (?): | Tracks system events such as Windows logon, network, and power events. Notifies COM+ Event System subscribers of these events. | ||||||||||||||
OS (?): | NT4 Workstation, 2000 Professional, XP Home/Professional, Vista Home/Business, NT4 Server, 2000 Server, Server 2003, Vista Server | ||||||||||||||
Startup (?): |
| ||||||||||||||
Explanation (?): | The system event notification service is a subscribed subcomponent of the COM+ Event System service. This service receives notifications from the COM+ EVent System about events such as logons, logoffs, power events such as power outages, and network events such as having an actively powered network connection. This service also provides APIs for responding to programs about the state of these events it is meant to monitor. This syncronization manager (mobsync.exe) uses this service to coordinate offline file syncronization. If this service is disabled then a warning will be posted to the system event log saying that SENS is unavailable, specific APIs provided by SENS will be unavailable, the syncronization manager will not work, and any other services or programs that require this service will not function properly. Mobile devices such as laptops used this service to monitor power events, and some battery backup systems could use this service. Therefore I suggest leaving this service to automatic. You can safely disable this service if you need the extra memory, but I would suggest against it, especially it's a laptop. If you set this service to manual then it will be automatically started when your computer boots. |