| 73.Service Name:-BINLSVC |
| Executable Name:-tcpsvcs.exe |
| Log On As:-LocalSystem |
Description:-Remote Installation Services (RIS) is a Windows deployment feature that is provided on the Windows Server 2003 operating system family. With RIS, you can support on-demand, image-based or script-based operating system installations over a network connection from a RIS server to a client computer. RIS is designed to simplify the deployment of operating systems and applications and to improve failure recoverability.
You can use RIS in a variety of ways, including the following:
- Provide an operating system to users on demand. You can use RIS to create automated installation images of Windows Server 2003, Windows XP, and Windows 2000. When a user starts a client computer, even if that computer contains no operating system, the RIS server can respond by installing an operating system over the network; no CD is required. To support this, client computers must use the Pre-boot eXecution Environment (PXE), a remote-boot technology that allows the client computer to begin a boot sequence from BIOS, using the network adapter. For more information about the process through which RIS installs an operating system, see PXE architecture and Technologies and components used by Remote Installation Services.
- Provide operating system images which include specific settings and applications. For example, an image that complies with a corporate desktop standard. A particular group of users can be offered the image or images that you designate for that group. For more information, see Creating an installation image with RIPrep.
If the service is turned off, the PXE clients requesting RIS installations will fail to get a reply and remote operating system installations using RIS will no longer function.
*On Windows 2000, this service was called the Boot Information Negotiation Layer service.
|
| Avaliable on OS:-Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition. |
| Installed through:-Default: Add/Remove Programs, Add/Remove Windows Components, Remote Installation |
| Startup type:-Automatic |
| Service status:-Started |
| This service depends on the following system components:-RemoteServer,
TCP/IP Protocol Driver
|
| The following system components depend on this service:-None |
| Port Numbers used:-TCP: 1067, 1068 |
|
| 74.Service Name:-RpcSs |
| Executable Name:-svchost -k rpcss |
| Log On As:-LocalSystem |
Description:-Microsoft RPC is a powerful, robust, efficient, and secure interprocess communication (IPC) mechanism that enables data exchange and invocation of functionality residing in a different process. Different process can be on the same machine, on the local area network, or across the Internet. RPC serves as the RPC endpoint mapper and COM Service Control Manager (SCM). There are a lot of services which depend on the RPC service to start successfully.
This service cannot be stopped or disabled using either the MMC services snap in or the MSCONFIG utility. Disabling the Remote Procedure Call (RPC) service will result in the operating system not loading.
|
| 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:- Background Intelligent Transfer Service,
Cluster Service,
COM+ Event System,
COM+ System Application,
Cryptographic Services,
DHCP Server,
Distributed Link Tracking Client,
Distributed Link Tracking Server,
Distributed Tracking Coordinator,
DNS Server,
Error Reporting Service,
Fax,
File Replication,
Help and Support,
Human Device Interface Access,
IIS Admin Service,
Indexing Service,
Internet Authentication Service,
IPSEC Services,
IPv6 Helper Service,
Kerberos Key Distribution Center,
Logical Disk Manager,
Logical Disk Administrator Service,
Messenger,
MS Software Shadow Copy Provider,
Network Connections,
Print Spooler,
Protected Storage,
Remote Desktop Help Session Manager,
Remote Registry,
Removable Storage,
Resultant Set of Policy Provider,
Routing and Remote Access,
Security Accounts Manager,
Shell Hardware Detection,
Task Scheduler,
Telephony,
Telnet,
Terminal Services,
Terminal Services Session Directory,
Terminal Services Licensing,
Upload Manager,
Volume Shadow Copy,
Web Element Manager,
Windows Audio,
Windows Image Acquisition (WIA),
Windows Installer,
Windows Internet Name Service (WINS),
Windows Management Instrumentation,
Windows Media Services,
Wireless Configuration,
WMI Performance Adapter,
World Wide Web Publishing Service, |
Port Numbers used:-TCP: 135, 530, 593, 80 if RPC tunneling over HTTP is used, dynamically allocated
UDP: 135, 530, 2034, dynamically allocated
|
|
| 75.Service Name:-RpcLocator |
| Executable Name:-locator.exe |
| Log On As:-Networkservice |
Description:-Enables RPC clients using the RpcNs* family of APIs to locate RPC servers and manages the RPC name service database. This service is turned off by default.
For more information about the RpcNs family of APIs, see the Software Development Kit (SDK) information in the MSDN Library link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources/.
This RPC Locator service is by default Manual. If this service is stopped, depending on the role the particular server was playing in the discovery process, RPC clients that rely on RpcNs* APIs from the same computer may not be able to find RPC servers supporting a given interface, or if the service is turned off on a domain controller, RPC clients using the RpcNs* APIs and this domain controller may experience interruption of service while trying to locate clients.
If this service is stopped or disabled, RPC clients using RpcNs* APIs may be unable to locate servers. RPC clients that rely on RpcNs* APIs from the same computer might not be able to find RPC servers supporting a given interface. If the service is stopped or disabled on your domain controller, RPC clients using the RpcNs* APIs and the domain controller might experience interruption of service while trying to locate clients.
RpcNs* APIs are not used internally in Windows; you only need to start this service if third party applications require this service.
|
| 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:-Manual(Automatic on a domain controller) |
| Service status:-Stopped(Started on a domain controller) |
| This service depends on the following system components:-Workstation |
| The following system components depend on this service:- None |
| Port Numbers used:-TCP: 135 |
|
