 |
|||||||||||||||||
|
MachSol® (http://www.machsol.com) a Microsoft Exchange Validated solution Vendor is to maintain the tradition of supporting latest Microsoft products and technologies as MachSol proudly announces to roll out MachPanel support for Microsoft Exchange 2013, Lync 2013 and SharePoint 2013. |
|||||||||||||||||
Be Ahead with Exchange 2013 – Lync 2013 – SharePoint 2013! |
|||||||||||||||||
| MachSol has been a trend setter in HSP industry by MachPanel – a cutting-edge control panel that gives you the ability to gain competitive edge over your competitors by means of providing support of latest Microsoft products. To keep up the tradition, MachSol is ready to launch new release of MachPanel that supports Microsoft Exchange 2013, SharePoint 2013 and Lync 2013 at the same time. | |||||||||||||||||
| Alongside this flagship product, MachSol provides comprehensive turnkey solution and services for various Microsoft technologies and helps you to stay updated with latest industry standards. We can quickly scan your requirements and come up with specific solution tailored to your business needs that may involve infrastructure design, maintenance, updates and migration, provisioning and automation, billing and customer support etc. – all under one umbrella. | |||||||||||||||||
| Contact us for Special Offer now! | |||||||||||||||||
| Sincerely, MachSol Team |
|||||||||||||||||
|
|||||||||||||||||
Archive for the ‘Microsoft Lync 2010’ Category
Complete Support for Exchange 2013 – SharePoint 2013 – Lync 2013
Monday, December 24th, 2012External DNS and Certificates Planning for Lync 2010 as Hosting Service
Tuesday, December 4th, 2012Microsoft released Lync Multi-Tenant Pack for hosting providers to offer Lync as a hosting service. Even before this pack, many companies were already offering Lync and OCS as hosting services to SMBs. The deployment guide for Multi-Tenant pack states to add few SAN entries for each new domain. If you try to login without adding SAN entry for the domain, login fails! This means that with every new customer, you will have to update your certificates, pay for any new SAN entries and then reassign the certificates. This does not seem to be a good idea in terms of cost and ease of provisioning a new tenant.
So, to help out those who are planning to offer Lync as a hosting service or those who already are, I suggest planning DNS and certificates as following:
Meet URL configuration:
For every hosted domain you will need meet URLs. These URLs are used to schedule online meetings. I would recommend first reading this article: Planning for Simple URL. For a hosting company, Option 3 mentioned in this article is best choice. Format for meet URL as per Option is:
https://lync.contoso.com/contosoSIPdomain/Meet
https://lync.contoso.com/fabrikamSIPdomain/Meet
Where lync.contoso.com is Provider’s domain and contosoSIPdomain and fabrikamSIPdomain are hosted domains. Following this format will minimize DNS and certificate requirements.
DNS for Hosted Domain:
If you have followed Option 3 for meet URL, you now only need three DNS records for every hosted organization. Frist one for client auto configuration; an SRV record _sip._tls.<hosteddomain> pointing to sip.<providerdomain>. Second, for federation; an SRV record _sipfederationtls._tcp.<hosteddomain> pointing to sip.<providerdomain>. Third one is for Lync Mobile Clients: ‘A’ record lyncdiscover.<hosteddomain> pointing to MCX Server.
Using such planning, there will be no need to update and reapply certificates. However, clients will display a pop up window while logging in, informing that you are being redirected to another server:
At this point user should check the box ‘Always trust this server’ (after seeing the certificate details and making sure that this is indeed service provider’s server).
Apart from being cost effective and easy, another advantage is that, if you expand the Certificate Details, your hosted organizations will not be exposed!