And so the announcement is [finally] made….. the next version of Lync, set for 1H 2015 will become ‘Skype for Business’. I think we all knew that this was going to happen, it was just a matter of when. I think we are all also in agreement that is the logical step for Microsoft to take, considering the audience and global presence that Skype has.
Me personally, I am keen to see the approach taken to upgrades (in place hopefully!), content sharing and federation now that we are essentially “one platform”. With new client and server releases and updates to Office 365 there are busy times ahead for all of us!
Check out the Skype blog for more info!
There has been a very (welcomed) recent addition to the Microsoft Open Interoperability Program, in particular, the ‘Infrastructure’ section.
Citrix VDI is now supported by Microsoft (and Citrix) in a Lync 2013 environment!
Citrix VDI now listed and supported by Microsoft
I have many clients that have held back on Lync due to the lack of Microsoft support for Citrix deployments, so this is definitely been an overdue requirement.
Microsoft has recently updated it’s client support for Lync Online, which now includes the Lync 2010 Windows Client. This is a significant piece of Information, particularly for migration scenarios and the client rollout process. A lot of demand has been made within the community for this, so I’m sure it will be very much welcomed!
Microsoft Lync 2010 desktop client must be version 4.0.7577.4419 (or later) released in January 2014, as described here: http://support.microsoft.com/kb/2912208.
I recently received information that I thought would be useful to share with the community, also in attempt to prevent a lot of support threads asking why federation is no longer working with Microsoft! 🙂
“The federated edge server that supports Instant Messaging and conferencing with external companies will be migrated on Friday, May 9, 2014.
After the server migration, the IP address for the sipfed.microsoft.com SIP domain will change to 22.214.171.124. External companies who are federated with Microsoft may need to make changes to their infrastructure outlined under Instructions below in order for the federation to continue to function successfully.”
Customers that originally configured their federation route with Microsoft to use an IP address will have to modify that entry and possibly firewall rules to ensure communications continue successfully.
Depending on how their infrastructure is configured, they may need to make one of the following changes:
- Companies configured as direct federations using IP address (not sipfed.microsoft.com) will need to update their configuration to the new IP address.
- Companies using their firewall(s) to filter by IP address will need to update their Access Control List (ACL) to the new IP address
Note: External companies that are configured as an Enhanced federation and have configured their firewall(s) to Allow All (inbound and outbound) on TCP:5061 according to Microsoft’s recommendations will not need to make any changes.