Simple URL Options
Topic Last Modified: 2011-03-23
Microsoft Office Communications Server 2007 R2 embedded links into meeting requests that were unreadable to most people, making it difficult to troubleshoot. Microsoft Lync Server 2010 communications software addresses that issue by publishing meeting information in an easy-to-read format:
Sample Office Communications Server 2007 R2 meeting request:
meet:sip:lstest01@contoso.com;gruu;opaque=app:conf:focus:id:86dddd778f0443feaad144739eb6d285%3Fconf-key=A3O3Mrxm9Sample Lync Server 2010 meeting request (shared simple URL syntax):
https://ls.contoso.com/meet/lstest01/D7RDV4KGSample Lync Server 2010 meeting request (dedicated simple URL syntax):
https://meet-us.contoso.com/lstest01/D7RDV4KG
When planning your simple URLs, you need to decide whether to use the shared or dedicated format. Selection criteria for each approach are listed in the following table.
Simple URL Formats
| Format | Use for |
|---|---|
Shared |
Single pool deployments Multiple pool deployments where each pool shares global simple URLs Multiple pool deployments where each pool has dedicated simple URLs and public certificate cost is an issue (you can save one certificate per pool by using shared simple URLs) |
Dedicated |
Multiple pool deployments where each pool has dedicated simple URLs Deployments where you do not want to potentially display internal server names externally |
Note
Simple URLs are defined globally, but in some cases you may want to create a different set of simple URLs (for example, dialin, meet, and, if internal, admin) per geography or pool. If so, you can use Windows PowerShell command-line interface to assign them at the pool level.