{"id":216,"date":"2013-05-03T00:07:59","date_gmt":"2013-05-02T22:07:59","guid":{"rendered":"http:\/\/blog.lync2013.org\/?p=216"},"modified":"2014-05-13T13:25:41","modified_gmt":"2014-05-13T13:25:41","slug":"understanding-simple-urls-in-lync","status":"publish","type":"post","link":"https:\/\/modern-workplace.uk\/?p=216","title":{"rendered":"Understanding Simple URLs In Lync"},"content":{"rendered":"<p><span style=\"font-family: Georgia, Palatino;\"><em>Originally published on the Microsoft TechNet Wiki<\/em><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><a href=\"http:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/15396.understanding-simple-urls-in-lync.aspx\">http:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/15396.understanding-simple-urls-in-lync.aspx<\/a><\/span><\/p>\n<hr \/>\n<h5><span style=\"font-family: Georgia, Palatino;\"><strong><a href=\"http:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/15396.understanding-simple-urls-in-lync.aspx\">I<\/a>ntro<\/strong><\/span><\/h5>\n<p><span style=\"font-family: Georgia, Palatino;\">A Lync deployment that has to be available to users outside our internal network \/ firewall (the generic definition used is\u00a0\u201cexternal users\u201d) requires two additional servers :<\/span><\/p>\n<ul>\n<li><span style=\"font-family: Georgia, Palatino;\">a Lync Edge server (for IM and presence, Web conferencing and A\/V conferencing)<\/span><\/li>\n<li><span style=\"font-family: Georgia, Palatino;\">a reverse proxy to publish features, such as conferencing meetings, conference join locations, Mobility services, and so on.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-family: Georgia, Palatino;\">Note : a recent version of the document \u00a0<a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/gg425779.aspx\">Components Required for External User Access<\/a>\u00a0that Alessandro Appiani has signaled to me, states that the reverse proxy is<b>required<\/b>\u00a0for the external user access, so any configuration that does not include the reverse proxy should rationally be considered not supported.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">Anyway an important aspect of the aforementioned configuration is that we have two \u201cgroups\u201d of services and one of them (the second one) is stricly web based.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">If you want to deep dive the topic, a good starting point is the TechNet document\u00a0<a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/gg399048.aspx\">Planning for External User Access<\/a><\/span><\/p>\n<hr \/>\n<p><span style=\"font-family: Georgia, Palatino;\"><strong>Simple URLs<\/strong><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">The document we will\u00a0start from, \u00a0to talk about simple URLs is the TechNet article\u00a0<a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/gg398287.aspx\">Planning for Simple URLs<\/a><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">Back to the\u00a0\u201cweb\u201d services (i.e. services we have to publish from the Front End)\u00a0we are talking about three URLs (called \u201cSimple URLs) that we\u00a0have to make available :<\/span><\/p>\n<ul>\n<li><span style=\"font-family: Georgia, Palatino;\"><strong>Meet<\/strong><\/span>\n<ul>\n<li>used for conferences, this is the one we see, for a example, if we have an invitation to a Lync meeting, in the form\u00a0<a href=\"https:\/\/meet.domain.com\/username\/\">https:\/\/meet.domain.com\/<i>username<\/i>\/<\/a>\u00a0)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><span style=\"font-family: Georgia, Palatino;\">\u00a0<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><a href=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/5850.vlcsnap-2013-01-16-12h09m05s4.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1418\" src=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/5850.vlcsnap-2013-01-16-12h09m05s4-1024x576.png\" alt=\"5850.vlcsnap-2013-01-16-12h09m05s4\" width=\"500\" height=\"281\" srcset=\"https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5850.vlcsnap-2013-01-16-12h09m05s4-1024x576.png 1024w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5850.vlcsnap-2013-01-16-12h09m05s4-300x168.png 300w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5850.vlcsnap-2013-01-16-12h09m05s4-150x84.png 150w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5850.vlcsnap-2013-01-16-12h09m05s4-580x326.png 580w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5850.vlcsnap-2013-01-16-12h09m05s4.png 1280w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/a><\/span><\/p>\n<ul>\n<li><span style=\"font-family: Georgia, Palatino;\"><strong>Dial-In<\/strong><\/span>\n<ul>\n<li>used to configure the settings for a user that will partecipate to a meeting using a telephone (dialing in)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><span style=\"font-family: Georgia, Palatino;\">\u00a0<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><a href=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/0741.dialin.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1419\" src=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/0741.dialin-300x228.jpg\" alt=\"0741.dialin\" width=\"500\" height=\"381\" srcset=\"https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/0741.dialin-300x228.jpg 300w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/0741.dialin-150x114.jpg 150w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/0741.dialin-580x441.jpg 580w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/0741.dialin.jpg 944w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/a><\/span><\/p>\n<ul>\n<li><span style=\"font-family: Georgia, Palatino;\"><strong>Admin<\/strong><\/span>\n<ul>\n<li>used to access to the\u00a0Lync Server Control Pane<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><span style=\"font-family: Georgia, Palatino;\">\u00a0<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><a href=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/8877.admin_.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1420\" src=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/8877.admin_.jpg\" alt=\"8877.admin\" width=\"500\" height=\"381\" srcset=\"https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/8877.admin_.jpg 944w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/8877.admin_-300x228.jpg 300w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/8877.admin_-150x114.jpg 150w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/8877.admin_-580x442.jpg 580w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/a><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">A\u00a0first reflection : if we do not plan to enable dialin conferencin or Lync administration from outside our internal network, the only important URL is meet<\/span><\/p>\n<hr \/>\n<h5><span style=\"font-family: Georgia, Palatino;\"><strong>Configuring Simple URLs<\/strong><\/span><\/h5>\n<p><span style=\"font-family: Georgia, Palatino;\">The configuration os simple URLs can be done using the Lync Topology Builder\u00a0or the\u00a0Lync Server Management Shell cmdlets.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">The first time we run the Topology Builder we configure it\u00a0with a\u00a0global scope (i.e. for the whole organization) but we can use different simple URLs for each central site in our company.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">For an explanation on the site customization of simple URLs I suggest a great post from Justin Morris\u00a0<a href=\"http:\/\/www.justin-morris.net\/configuring-site-level-simple-urls-in-lync-server-2010\/\">Configuring Site Level Simple URLs in Lync Server 2010<\/a><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">Back to the configuration of simple URLs we have three basic options :<\/span><\/p>\n<p style=\"padding-left: 30px;\"><span style=\"font-family: Georgia, Palatino;\">1. a DNS name for every service, so we have :<\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/meet.domain.com\/<\/em><\/strong><\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/dialin.domain.com\/<\/em><\/strong><\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/admin.domain.com\/<\/em><\/strong><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><a href=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/5516.3names.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1421\" src=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/5516.3names.jpg\" alt=\"5516.3names\" width=\"500\" height=\"381\" srcset=\"https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5516.3names.jpg 944w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5516.3names-300x228.jpg 300w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5516.3names-150x114.jpg 150w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/5516.3names-580x442.jpg 580w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/a><\/span><\/p>\n<p style=\"padding-left: 30px;\"><span style=\"font-family: Georgia, Palatino;\">2.\u00a0 a single DNS name with a specific URL for every service like<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><strong><em>https:\/\/lync.domain.com\/meet<\/em><\/strong><\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/lync.domain.com\/dialin<\/em><\/strong><\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/lync.domain.com\/admin<\/em><\/strong><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><a href=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/8204.1name.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1422\" src=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/8204.1name.jpg\" alt=\"8204.1name\" width=\"500\" height=\"381\" srcset=\"https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/8204.1name.jpg 550w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/8204.1name-300x228.jpg 300w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/8204.1name-150x114.jpg 150w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/a><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">It is easy to understand that the above decision has an impact on the SSL certificates we will need for our Lync deployment.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">Option 1 requires three names (dialin, meet and admin)\u00a0in a SAN certificate, option 2 requires a single name (lync) for the \u201cweb\u201d services of Lync.<\/span><\/p>\n<p style=\"padding-left: 30px;\"><span style=\"font-family: Georgia, Palatino;\">3. The third option is interesting for organization that are using more than one SIP domain and need to keep the number of names in the SSL certificate as low as possible. If we have sipdomain1.com and sipdomain2.com the solution will look like<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><strong><em>https:\/\/lync.domain.com\/sipdomain1\/Meet<\/em><\/strong><\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/lync.domain.com\/sipdomain2\/Meet<\/em><\/strong><\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/lync.domain.com\/sipdomain1\/dialin<\/em><\/strong><\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> <strong><em>https:\/\/lync.domain.com\/sipdomain1\/admin\u00a0<\/em><\/strong><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">In the above configuration the only URL that is related to the different SIP domains is meet and that is due to the kind of service that the different links are related to.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">Also in option 3 we have a single DNS name and, so, a single name in the SSL certificate.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">Note : you could prefer to use a value different from \/sipdomain\/ .<\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> That is something you can do because\u00a0the\u00a0url string after\u00a0<a href=\"https:\/\/lync.domain.com\/sipdomain1\/admin\">https:\/\/lync.domain.com\/<\/a>\u00a0is something you are free to decide with no complication<\/span><\/p>\n<hr \/>\n<p><span style=\"font-family: Georgia, Palatino;\"><strong>Configuring Simple URLs Using Lync Server Management Shell<\/strong><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">The configuration of simple URLs from the management shell\u00a0is based on the <strong><em>Set-CsSimpleUrlConfiguration<\/em><\/strong> cmdlet (see Technet for more details\u00a0<a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/gg412991.aspx\">Set-CsSimpleUrlConfiguration<\/a>\u00a0) and usually requires the use of variables to define the different URLs<\/span><br \/>\n<span style=\"font-family: Georgia, Palatino;\"> To identify the configuration that is running in your Lync deployment use the <strong><em>Get-CsSimpleUrlConfiguration cmdlet (\u00a0<a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/gg398392.aspx\">Get-CsSimpleUrlConfiguration<\/a>\u00a0)<\/em><\/strong><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\"><a href=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/1030.cmdlet.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-1423\" src=\"https:\/\/modern-workplace.uk\/\/wp-content\/uploads\/2013\/05\/1030.cmdlet.jpg\" alt=\"1030.cmdlet\" width=\"500\" height=\"253\" srcset=\"https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/1030.cmdlet.jpg 567w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/1030.cmdlet-300x151.jpg 300w, https:\/\/modern-workplace.uk\/wp-content\/uploads\/2013\/05\/1030.cmdlet-150x75.jpg 150w\" sizes=\"auto, (max-width: 500px) 100vw, 500px\" \/><\/a><\/span><\/p>\n<hr \/>\n<p><span style=\"font-family: Georgia, Palatino;\"><strong>Changing Simple URLs<\/strong><\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">If we have deployed simple URLs using one of the options and we need to change our settings to a different option we are able to use again the Lync Topology Builder\u00a0or the\u00a0Lync Server Management Shell followed by an Enable-CsComputer launched on every Director and Front End.<\/span><\/p>\n<p><span style=\"font-family: Georgia, Palatino;\">It is really important to understand that the aforementioned operation has conseguences on our records on the public DNS and on the certificate we are going to use<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Originally published on the Microsoft TechNet Wiki http:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/15396.understanding-simple-urls-in-lync.aspx Intro A Lync deployment that has to be available to users outside our internal network \/ firewall (the generic definition used is\u00a0\u201cexternal users\u201d) requires two additional servers : a Lync Edge server (for IM and presence, Web conferencing and A\/V conferencing) a reverse proxy to publish features, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","twitterCardType":"","cardImageID":0,"cardImage":"","cardTitle":"","cardDesc":"","cardImageAlt":"","cardPlayer":"","cardPlayerWidth":0,"cardPlayerHeight":0,"cardPlayerStream":"","cardPlayerCodec":"","footnotes":""},"categories":[18,19],"tags":[554,702,32,33,34,35,556,555,36,37,26,38,39,40,41,42,43,44,171,45,46],"class_list":{"0":"post-216","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"hentry","6":"category-english","7":"category-lync","8":"tag-external-users-lync","9":"tag-lync","10":"tag-lync-2013-client","11":"tag-lync-2013-server","12":"tag-lync-best-practices","13":"tag-lync-client","14":"tag-lync-dialin-url","15":"tag-lync-meet-url","16":"tag-lync-microsoft","17":"tag-lync-reverse-proxy","18":"tag-lync-server","19":"tag-lync-simple-url","20":"tag-lync-simple-urls","21":"tag-lync-web","22":"tag-lync-web-services","24":"tag-lync2013-technet-wiki","25":"tag-microsoft-lync-2013","26":"tag-reverse-proxy","27":"tag-simple-url","28":"tag-simple-urls"},"_links":{"self":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/216","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=216"}],"version-history":[{"count":7,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/216\/revisions"}],"predecessor-version":[{"id":1426,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/216\/revisions\/1426"}],"wp:attachment":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=216"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}