Parameters

In Microsoft Office Communications Server 2007 R2, meetings had URLs similar to this:

https://imdf.litwareinc.com/Join?uri=sip%3Akenmyer%40litwareinc.com%3Bgruu%3Bopaque%3Dapp%3Aconf%3Afocus%3Aid%3A125f95a0b0184dcea706f1a0191202a8&key=EcznhLh5K5t

However, such URLs are not especially intuitive, and not easy to convey to someone else. The simple URLs introduced in Lync Server 2010 help overcome those problems by providing users with URLs that look more like this:

https://meet.litwareinc.com/kenmyer/071200

Simple URLs are an improvement over the URLs used in Office Communications Server. However, simple URLs are not automatically created for you; instead, you must configure the URLs yourself. In addition, you must also do such things as create Domain Name System (DNS) records for each URL; configure reverse proxy rules for external access; add the simple URLs to the your Front End Server certificates; and so on.

Lync Server enables you to create three different simple URLs:

Meet – Used for meetings. You must have at least one Meet URL for each of your SIP domains.

Admin – Used to point administrators towards the Lync Server 2010 Control Panel.

Dialin – Used for the dial-in conferencing webpage.

Simple URLs are stored in simple URL configuration collections. When you install Lync Server, a global collection is created for you; you can also create custom collections at the site scope. This gives you the ability to use different simple URLs at each of your sites.

Simple URL configuration collections are created by using the New-CsSimpleUrlConfiguration cmdlet; you can then use additional cmdlets (such as New-CsSimpleUrlEntry and Set-CsSimpleUrlConfiguration) to populate these collections with simple URLs. If you later decide to delete one or more of the site-scoped collections, you can do so by using the Remove-CsSimpleUrlConfiguration cmdlet.

Who can run this cmdlet: By default, members of the following groups are authorized to run the Remove-CsSimpleUrlConfiguration cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets –match "Remove-CsSimpleUrlConfiguration"}

Microsoft.Rtc.Management.WritableConfig.Settings.SimpleUrl.SimpleUrlConfiguration object. Remove-CsSimpleUrlConfiguration accepts pipelined instances of the simple URL configuration object.

None.

-------------------------- Example 1 ------------------------

	Copy Code
Remove-CsSimpleUrlConfiguration -Identity "site:Redmond"

The command shown in Example 1 deletes the simple URL configuration collection applied to the Redmond site. This command deletes all the simple URLs assigned to the specified site.

-------------------------- Example 2 ------------------------

	Copy Code
Get-CsSimpleUrlConfiguration -Filter "site:*" | Remove-CsSimpleUrlConfiguration

In Example 2, all the simple URL configuration collections applied at the site scope are deleted. To do this, the command first uses Get-CsSimpleUrlConfiguration and the Filter parameter to return all the simple URL collections configured at the site scope; the filter value "site:*" limits the returned data to those collections that have an Identity that begins with the string value "site:". The filtered collection is then piped to Remove-CsSimpleUrlConfiguration, which deletes each item in that collection.

Other Resources