I am deploying the Lync management pack in SCOM and trying to get healthy states for a Lync Distributed App 

Event 14584 is showing up on my Lync servers and the SCOM management pack is alerting:

______________

"Connection attempts to the following services have failed. Another attempt will be made for each service every 10 minutes.
Service Address: [IP of remote DC]:5061; Pool FQDN: [domain name]; Down Time: 0:00

Cause: The specified service(s) are unavailable.
Resolution:
Check the servers in the pool(s) on which the service(s) are installed.

Please see the 'Product Knowledge' and the 'Alert Context' tab on Alert Properties view for more information.

______________

Now over the months I seem to get a lot of these events, for numerous remote DC's. 

Why is the Pool FQDN my domain name, and why does Lync keep trying to connect to the domain name (which resolved to a large number of DC's, many of which are remote and sometimes uncontactable).

Is this a configuration issue or should I override in SCOM?

Hi,

It may cause by the network latency when connecting to Lync service in SCOM alert system, you can ignore it if there is no effect on Lync function.

Here is a similar case may help you:

http://social.technet.microsoft.com/Forums/lync/en-US/49cb3507-2ee6-4993-b81a-a131cf10ef17/event-id-14584-ls-protocol-stack-connection-attempt-to-at-least-one-service-in-a-pool-failed?forum=ocsmonitoring

Best Regards,

Eason Huang

I think the odd stand out factor is that the alert concerns an event complaining about a Pool FQDN that is my domain name. Pool FQDN = domain name / SIP domain. I had seen the article you linked, their alert is on a few servers from an expected pool name.

Why is that? Get-CSPool returns no pool named after my domain name. My front end pool is called lyncpool01.domain.com

I guess there is a configuration issue, Lync should not be trying to talk to 200 remote domain controllers thinking they are pool servers?

If you are using a domain based DFS file store in your Lync topology then it will show up as a pool when you run get-cspool.

Identity       : domain.com
Services       : {FileStore:domain.com}
Computers      : {domain.com}
Fqdn           : domain.com
BackupPoolFqdn :
Site           : Site:CENTRAL

This event can likely be ignored.

• Edited by JSKY1 14 hours 51 minutes ago

JSKY1, maybe that is it! File store is on a DFS server. Although, when I run get-cspool I do not have any pool with domain.com. 

For the file store I simply have:

Identity  : file-server
Services  : {FileStore:file-server}
Computers : {file-server}
Fqdn      : file-server
Site      : Site:CENTRAL

If you are using a domain based DFS file store in your Lync topology then it will show up as a pool when you run get-cspool.

Identity       : domain.com
Services       : {FileStore:domain.com}
Computers      : {domain.com}
Fqdn           : domain.com
BackupPoolFqdn :
Site           : Site:CENTRAL

This event can likely be ignored.

• Edited by JSKY1 Thursday, March 13, 2014 8:04 PM

If you are using a domain based DFS file store in your Lync topology then it will show up as a pool when you run get-cspool.

Identity       : domain.com
Services       : {FileStore:domain.com}
Computers      : {domain.com}
Fqdn           : domain.com
BackupPoolFqdn :
Site           : Site:CENTRAL

This event can likely be ignored.

• Edited by JSKY1 Thursday, March 13, 2014 8:04 PM