In the previous recipe, we outlined the steps required to establish a remote PowerShell session with Lync Online. We have less than 50 cmdlets, as shown in the result of the Get-Command -Module command in the following screenshot:
Some of them are specific for Lync Online, such as the following:
Get-CsAudioConferencingProviderGet-CsOnlineUserGet-CsTenantGet-CsTenantFederationConfigurationGet-CsTenantHybridConfigurationGet-CsTenantLicensingConfigurationGet-CsTenantPublicProviderNew-CsEdgeAllowAllKnownDomainsNew-CsEdgeAllowListNew-CsEdgeDomainPatternSet-CsTenantFederationConfigurationSet-CsTenantHybridConfigurationSet-CsTenantPublicProviderUpdate-CsTenantMeetingUrl
All the remaining cmdlets can be used either with Lync Online or with the on-premises version of Lync Server 2013. We will see the use of some of the previously mentioned cmdlets.
- The
Get-CsTenantcmdlet will list Lync Online tenants configured for use in our organization. The output of the command includes information such as the preferred language, registrar pool, domains, and assigned plan. - The
Get-CsTenantHybridConfigurationcmdlet gathers information about the hybrid configuration of Lync (we will talk about this scenario, starting with the Introducing Lync in a hybrid scenario section). - Management of the federation capability for Lync Online (the feature that enables Instant Messaging and Presence information exchange with users of other domains) is based on the allowed domain and blocked domain lists, as we can see in the organization and external communications screen of LAC, shown in the following screenshot:
- There are similar ways to manage federation from the Lync Online PowerShell, but it required to put together different statements as follows:
- We can use an accept all domains excluding the ones in the exceptions list approach. To do this, we have put the
New-CsEdgeAllowAllKnownDomainscmdlet inside a variable. Then, we can use theSet-CsTenantFederationConfigurationcmdlet to allow all the domains (except the ones in the block list) for one of our domains on a tenant. We can use the example on TechNet (http://technet.microsoft.com/en-us/library/jj994088.aspx) and integrate it withGet-CsTenant. - If we prefer, we can use a block all domains but permit the ones in the allow list approach. It is required to define a domain name (pattern) for every domain to allow the
New-CsEdgeDomainPatterncmdlet, and each one of them will be saved in a variable. Then, theNew-CsEdgeAllowListcmdlet will create a list of allowed domains from the variables. Finally, theSet-CsTenantFederationConfigurationcmdlet will be used. The domain we will work on will be (again)cc3b6a4e-3b6b-4ad4-90be-6faa45d05642. The example on Technet (http://technet.microsoft.com/en-us/library/jj994023.aspx) will be used:$x = New-CsEdgeDomainPattern -Domain "contoso.com" $y = New-CsEdgeDomainPattern -Domain "fabrikam.com" $newAllowList = New-CsEdgeAllowList -AllowedDomain $x,$y Set-CsTenantFederationConfiguration -Tenant " cc3b6a4e-3b6b-4ad4-90be-6faa45d05642" -AllowedDomains $newAllowList
- We can use an accept all domains excluding the ones in the exceptions list approach. To do this, we have put the
- The
Get-CsOnlineUsercmdlet provides information about users enabled on Office 365. The result will show both users synced with Active Directory and users homed in the cloud. The command supports filters to limit the output; for example, theGet-CsOnlineUser -identityfab will gather information about the user that has alias= fab. This is an account synced from the on-premises Directory Services, so the value of theDirSyncEnabledparameter will beTrue.
All the cmdlets of the Remote PowerShell for Lync Online are listed in the TechNet post Lync Online cmdlets at http://technet.microsoft.com/en-us/library/jj994021.aspx. This is the main source of details on the single statement.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.