调查SharePoint前端上的一些巨大日志后，我发现运行SharePoint Application App Pool的帐户正在服务器场中的每个网站集中运行。
我添加了我的ULS日志的摘要。 你们有没有经历过类似的经历？
-----First Site:
Authentication Authorization RunWithElevated: 68baf19e-7314-4032-4aed-7866e30599d5
Topology SecurityTokenServiceSendRequest: RemoteAddress: 'http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustChannelContract' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:[guid]' 68baf19e-7314-4032-4aed-7866e30599d5
Topology SecurityTokenServiceReceiveRequest: LocalAddress: 'http://[SERVER].local:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:[guid]' 68baf19e-7314-4032-4aed-7866e30599d5
Monitoring Entering Monitored Scope (ExecuteSecurityTokenServiceOperationServer). Parent=None 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication STS Call: Creating Claims Operations Scope for Applies To Uri: 'https://[DNSNAME].local/sites/SITE-46216' 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication Not creating SPClaimsOperationContext since there is one on the thread already. Uri: 'https://[DNSNAME].local/sites/SITE-46216' 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication Building cookie signature. 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication STS Call Claims Windows: Successfully requested sign-in claim identity for user '[USER]'. 68baf19e-7314-4032-4aed-7866e30599d5
Monitoring Leaving Monitored Scope: (ExecuteSecurityTokenServiceOperationServer) Execution Time=4.6971; CPU Milliseconds=4; SQL Query Count=0; Parent=None 68baf19e-7314-4032-4aed-7866e30599d5
-----Second Site:
Authentication Authorization RunWithElevated: 68baf19e-7314-4032-4aed-7866e30599d5
Topology SecurityTokenServiceSendRequest: RemoteAddress: 'http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'Microsoft.IdentityModel.Protocols.WSTrust.IWSTrustChannelContract' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:[guid]' 68baf19e-7314-4032-4aed-7866e30599d5
Topology SecurityTokenServiceReceiveRequest: LocalAddress: 'http://[SERVER].local:32843/SecurityTokenServiceApplication/securitytoken.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue' MessageId: 'urn:uuid:[guid]' 68baf19e-7314-4032-4aed-7866e30599d5
Monitoring Entering Monitored Scope (ExecuteSecurityTokenServiceOperationServer). Parent=None 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication STS Call: Creating Claims Operations Scope for Applies To Uri: 'https://[DNSNAME].local/sites/SITE-46217' 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication Not creating SPClaimsOperationContext since there is one on the thread already. Uri: 'https://[DNSNAME].local/sites/SITE-46217' 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication Building cookie signature. 68baf19e-7314-4032-4aed-7866e30599d5
Claims Authentication STS Call Claims Windows: Successfully requested sign-in claim identity for user '[USER]'. 68baf19e-7314-4032-4aed-7866e30599d5
Monitoring Leaving Monitored Scope: (ExecuteSecurityTokenServiceOperationServer) Execution Time=5.2639; CPU Milliseconds=5; SQL Query Count=0; Parent=None 68baf19e-7314-4032-4aed-7866e30599d5
-----Third Site:
Authentication Authorization RunWithElevated: 68baf19e-7314-4032-4aed-7866e30599d5
… etc.