In the November 2011 Cumulative Update of Lync 2010, Microsoft added the ability to disable file transfers via the edge server. This feature enhancement undoubtedly was the result of customers voicing concerns about data loss protection and was a welcomed addition to the IT administrator’s arsenal. In short, the feature allowed administrators to block all file transfers that would traverse an organization’s edge server but allowed file transfers within the confines of the internal network (assuming the user was assigned a conference policy that allowed it).
We take you through 10 best practices, considerations, and suggestions that can enrich your Microsoft Teams deployment and ensure both end-user adoption and engagement.
In Lync 2010, to block all file transfers on the edge server you would use the following command:
new-csfiletransferfilterconfiguration -identity edgeserver:pia-ls2013-ed01.widgets.com -blockfileextension $true -action blockall -enabled $true
The same file transfer blocking capabilities exist in Lync 2013, but the commands are a bit different from what was used in Lync 2010.
In Lync 2013, to block all file transfers on the edge server you would use the following command:
new-csfiletransferfilterconfiguration -identity edgeserver:pia-ls2013-ed01.widgets.com -action blockall -enabled $true