分类： 云计算
2011-12-15 17:56:05
Lync Cumulative Update 4 is now available for . While combining a number of fixes, it also includes some new PowerShell cmdlets to manage upcoming mobility functionality (actually a couple were slipped into CU3 but had no help files in CU3). Full details of the mobility service have not yet been released, so I would assume you should not be using these cmdlets yet. So what are the new cmdlets? Glad you asked.
CsAutodiscoverConfiguration
New-CsWebLink
Test-CsMcxPushNotification
CsMobilityPolicy
CsMcxConfiguration
CsPushNotificationConfiguration (Get,New,Remove,Set)
Info gathered from the Lync CU4 PowerShell help files.
Full Descriptions:
CsAutodiscoverConfiguration DESCRIPTION
Get-CsAutodiscoverConfiguration
New-CsAutodiscoverConfiguration
Remove-CsAutodiscoverConfiguration
Set-CsAutodiscoverConfiguration
DESCRIPTION
For client applications to make the most effective use of Microsoft Lync Server 2010 those applications need to know the location of key Lync Server 2010 components. For example, authenticated users must be able to locate their home pool; after all, they can only be authenticated by that home pool. Likewise, unauthenticated users must be able to do such things as locate the URL used for joining a conference.
If all your users logged on from behind the organization’s firewall discovering these locations would be a relatively simple task. However, this relatively simple task gets more and more complicated as users access the system from external locations using Microsoft Lync Mobile or Lync Web Access.
This is especially true in split-domain scenarios, scenarios in which some of an organization’s users have accounts on the on-premises version of Lync Server while other users have accounts on Microsoft Office 365. In cases such as this, user accounts might be located in different Active Directory forests. That can pose a problem: for example, if a US-based user logs on from Europe the system must be able to recognize his or her forest and then refer the logon request to the proper pool.
The Autodiscover service was introduced in the November 2011 release of Lync Server in order to address these issues. When a client application attempts to access Lync Server, the Autodiscover service parses the client SIP address and then redirects that request to the appropriate pool. Client applications connect to the Autodiscover service by sending an HTTP request to a n Autodiscover URL; these URLs must be configured by administrators in order for the Autodiscover service to work. (Note that, in addition to configuring URLs, administrators must also create DNS records that correspond to these URLs.)
Autodiscover URLs are assigned to Autodiscover configuration settings; in turn, these settings can be applied to the global scope or to the site scope . When you install Lync Server a global collection of settings will be created for you. (However, no Autodiscover URLs will be assigned to that collection.) If a single collection of Autodiscover settings will not fill your needs, then you can use the New-CsAutoDiscoverConfiguration cmdlet to create additional configuration settings at the site scope. From there, you can u se the Set-CsAutoDiscoverConfiguration cmdlet to add or remove Autodiscover URLs from the global collection or from any site-scoped collection.
New-CsWebLink DESCRIPTION
Managing Autodiscover configuration settings typically means adding Autodiscover URLs. These URLs must be created using the New-CsWebLink cmdlet, with the resulting URL stored in a variable and then added to a collection of Autodiscover configuration settings. Autodiscover URLs are based on the SIP domains used in your organization; administrators will typically create one URL for use by users outside the organization’s firewall (for example, ) and a second URL (for example, DiscoverInternal.litwareinc.com) for use by users inside the firewall.
CsMcxPushNotification DESCRIPTION
Test-CsMcxPushNotification
The Apple Push Notification Service and the Microsoft Lync Server 2010 Push Notification Service enable users running Lync 2010 on their Apple iPhone or Windows Phone to receive notifications about Lync 2010 events even when Lync 2010 is suspended or running in the background. For example, users can receive notice for events such as these:
Without the push notification service, users would receive these notices on ly when Lync 2010 was in the foreground and serving as the active application.
The Test-CsMcxPushNotification cmdlet provides a way for administrators to verify that the push notification service is working.
CsMobilityPolicy DESCRIPTION
Get-CsMobilityPolicy
Grant-CsMobilityPolicy
New-CsMobilityPolicy
Remove-CsMobilityPolicy
Set-CsMobilityPolicy
Lync 2010 Mobile is a client application that enables users to run Microsoft Lync 2010 on their mobile phones. Call via Work provides a way for users to make calls on their mobile phone and yet have it appear as though the call originated from their work phone number instead of their mobile phone number. Users who have been enabled for Call via Work can achieve this either by dialing directly from their mobile phone or by using the dial-out conferencing option. With dial-out conferencing, a user effectively asks the Microsoft Lync Server 2010 Mobility Service server to make a call for them. The server will set up the call, and then call the user back on their mobile phone. After the user has answered, the server will then dial the party being called.
Both of these capabilities – the ability to run Lync 2010 Mobile and the ability to use Call via Work – are managed using mobility policies. These policies can be modified at any time by using the Set-CsMobilityPolicy cmdlet.
Other than a description of the policy, mobility policies have only two properties. The first, EnableOutsideVoice, determines whether or not Call via Work is enabled; the second, EnableMobility, determines whether or not user s are allowed to use Lync Mobile. Both of these properties must be set to t rue before a user can take advantage of Call via Work. If EnableMobility is set to True and EnableOutsideVoice is set to False, the user can run Micro soft Lync Mobile but will not be able to use Call via Work. If EnableMobility is set to False and EnableOutsideVoice is set to True the user will not be able to run Microsoft Lync Mobile. In turn, that means that the user will not be able to use Call via Work, regardless of the value of the EnableOutsideVoice property.
Note that users must also be enabled for Enterprise Voice before they can use Lync 2010 Mobile. To use Call via Work, users must be managed by a voice policy that allows simultaneous ringing.
CsMcxConfiguration DESCRIPTION
Get-CsMcxConfiguration
New-CsMcxConfiguration
Remove-CsMcxConfiguration
Set-CsMcxConfiguration
Microsoft Lync Server 2010 Mobility Service extends many of the capabilities of Microsoft Lync 2010 to mobile devices such as Apple iPhones, Windows P hone, Android phones, and Nokia phones. Among other things, users can use these phones to exchange instant message and presence information, and to receive notifications of new voice mails. Thanks to the push notification service (Apple Push Notification Service and Microsoft Lync Server 2010 Push Notification Service), users with iPhones or Windows Phones can receive these notifications even if Lync 2010 is running in the background. The Mobility Service also provides the opportunity for organizations to enable Call vi a Work. With Call via Work, users can make a call from their mobile phone and make it appear as though the call originated from their work phone; for example, Caller ID systems will display the user’s work number instead of h is or her mobile phone number.
The Mobility Service itself is managed by using Mobility Service configuration settings that can be applied to the global scope, the site scope, or the service scope (for the Web server service only). These settings control such things as the maximum length of time for a Mobility Service session; whether or not the Microsoft Lync Server 2010 Autodiscovery Service (which directs Mobility Service users to the appropriate Registrar pool) is available to users who log on outside the organization’s firewall); and the location of the push notification service provider.
The Set-CsMcxConfiguration cmdlet provides a way for administrators to modify any of their existing Mobility Service configuration settings.
CsPushNotificationConfiguration DESCRIPTION
Get-CsPushNotificationConfiguration
New-CsPushNotificationConfiguration
Remove-CsPushNotificationConfiguration
Set-CsPushNotificationConfiguration
The Apple Push Notification Service and the Microsoft Lync Server 2010 Push Notification Service enable users running Lync 2010 on their Apple iPhone or Windows Phone to receive notifications about Lync 2010 events even when Lync 2010 is suspended or running in the background. For example, users can receive notice for events such as these:
Without the push notification service users would receive these notices only when Lync 2010 was in the foreground and serving as the active application.
Administrators have the ability to enable or disable push notifications for iPhone users and/or Windows Phone users. (By default, push notifications a re disabled for both iPhone users and Windows Phone users.) Administrators can enable or disable push notifications at the global scope by using the S et-CsPushNotificationConfiguration cmdlet. They can also create custom push notification settings at the site scope by using the New-CsPushNotificationConfiguration cmdlet. These custom settings can also be modified by using the Set-CsPushNotificationConfiguration cmdlet.
With the push notification configuration settings there are only two property values for Administrators to manage: EnableApplePushNotificationService, which determines whether push notifications are sent to iPhone users; and EnableMicrosoftPushNotificationService, which determines whether push notifications are sent to Windows Phone users. Note that these property values d o not have to be set to the same value. For example, you could enable push notifications to Windows Phone users (by setting EnableMicrosoftPushNotificationService to True) yet, at the same, disable notifications to iPhone users by setting EnableApplePushNotificationService to False.
