The ability to send a generic Archiving Disclaimer to federated partners is nice, but not nearly sufficient for many organizations. For instance, some may have legal departments that wish to convey more than a simple Archiving Disclaimer - they may wish to remind both parties that the conversation is taking place with a Federated Partner, and not with an internal contact (sometimes we can glaze over things with the tabbed ...more »
There are a few 3rd-party vendors out there with Ethical Firewall solutions (granular control of which groups of users or individual users can communicate with other users), but none are complete solutions, and in most cases, business requirements warrant pricey customization by the vendor. It is been a long-time ask that Ethical Firewall functionality be built into the Lync/Skype for Business product, and this would ...more »
We've been seeing an increase in the number of Lync folks that have native Lync clients connected to a non-open environment. Largely these appear to be US government folks. When we attempt to invite them to a meeting, their native client takes priority and attempts to connect but fails due to their non federated environment or firewall. We then have them back track and open up the web client. While this is a workaround ...more »
Right now, the audio test service account has a long SIP address, such as sip:RtcApplicationfirstname.lastname@example.org. If you want to enable federation for this so you can test externally, you have to know this long address. It would be nice to be able to change it for easier use. By the way - changing it in adsiedit breaks it.
while there is a privately owned Lync directory that is very handy, http://www.lyncdirectory.com/ it would be better if each Lync server automatically listed in a Microsoft owned Lync Federation Directory to speed up searching for lync contacts.
Skype does auto search address book/contacts and find who's connected. This fast tracks adoption. It's kind of clunky that we say Lync integrates with Outlook contacts, but then you have to add lync contacts all over again one by one?!? People expect this to be at least like Skype, so ping each contact to Skype while you're at it. To make things 'usable' you have to make it easy to use from the beginning and show ...more »
Persistent Chat is a fantastic tool for collaboration and knowledge sharing. What would make it better would be to have it support federation, allowing people from outside the Lync AD Domain to be members of Chat Rooms and participate. Anything in the near future?
It would be nice if this was an option, maybe through policy. We sometimes have lots of federated clients, and need to appear busy to them, but available to internal resources. I know we could set privacy relationships, but this is several users with a substantial number of federated contacts.
As most Lync Pros know, these are going away. I know the hedge fund types love to use Yahoo IM, and aren't inclined to move to Lync if Yahoo federation is dying.
When running open federation the only way of checking which organizations that are federating with your organization is to go into your edge server (in that workgroup in that DMZ), open the event viewer and look for Event ID 14601. Here you will find a list of all active domains (organizations) that are currently federating with you. My suggestion is that this list should be visible in the Lync Server Control Panel ...more »
This would allow for more granular control of specific users/groups being able to federate with specific allowed domains, while other users/groups have access to other allowed domains.