Core Functionality
Applies To: Windows Server 2008 R2
In order for a BITS peer caching client to download content from BITS peer caching servers, at least one peer server must be available on the network to serve the content. The client must also be able to receive peer server announcements, to discover available servers. A peer server announces itself after it starts. If more servers are needed for its peer list, the client must be able to broadcast a request for peer servers.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-Bits-Client |
BITS started listening for peer-server announcements. | |
Microsoft-Windows-Bits-Client |
BITS stopped listening for peer-server announcements. | |
Microsoft-Windows-Bits-Client |
BITS has sent an inquiry for peer servers. | |
Microsoft-Windows-Bits-Client |
The peer list rejected an incoming server announcement. This event is generated if the request looks invalid, not if the server is merely in a different Windows domain. | |
Microsoft-Windows-Bits-Client |
A peer search for a URL has begun. | |
Microsoft-Windows-Bits-Client |
A peer search ended. | |
Microsoft-Windows-Bits-Client |
A search request is being sent. | |
Microsoft-Windows-Bits-Client |
A search request has completed. | |
Microsoft-Windows-Bits-Client |
A search request has completed unsuccessfully. | |
Microsoft-Windows-Bits-Client |
The peer's record %2 matched the request. | |
Microsoft-Windows-Bits-Client |
BITS search for peer-servers has started. | |
Microsoft-Windows-Bits-Client |
The peer computer's response to a search was invalid. | |
Microsoft-Windows-Bits-Client |
The peer-cache client startup phase of startup has completed. | |
Microsoft-Windows-Bits-Client |
The BITS peer cache was unable to find any peer computers in the network. |