The Microsoft Support team recently released the following Knowledge Base articles with solutions to four Lync PowerShell and Hybrid issues.
Author: Darrin Hanson, Microsoft Technical Readiness Engineer
Editor: Susan S. Bradley
Published: April 16, 2013
Product version: Lync Online PowerShell, Lync Online, Office 365
The Microsoft Support team released the following Knowledge Base articles with solutions to these issues:
Issue: An administrator is trying to set up a Microsoft Lync hybrid deployment. When the administrator tries to connect to Microsoft Lync Online PowerShell for the first time, she receives the following error message:
New-PSSession: [admin.online.lync.com] Processing data from remote server admin.online.lync.com failed with the following error message: Remote Windows PowerShell session creation is restricted by tenant Windows PowerShell policy. For more information, see the about_Remote_Troubleshooting Help topic.
Issue: When an administrator creates a new remote Lync Online PowerShell session for Microsoft Lync Online, he or she receives the following error message:
Get-CsWebTicket: Getting web ticket for the given user is failed. Error Code: 28037, Error Reason: The AppliesTo element of web ticket request points to a different web server or site.
Issue: In a Microsoft Lync hybrid deployment, when you try to move users from the on-premises server that is running Microsoft Lync to Microsoft Lync Online in Microsoft Office 365, you receive the following error message in Lync Online PowerShell:
Move-CsUser: HostedMigration fault: Error=(510), Description=(This user’s tenant is not enabled for shared sip address space.)
Issue: In a Microsoft Lync hybrid deployment, when you try to move a user to Microsoft Lync Online by using Lync Online PowerShell, you receive the following error message:
Move-CsUser: HostedMigration fault: Error=(507), Description=(User must has an assigned license to use Lync Online.)
|Darrin Hanson has been a Microsoft Technical Readiness Engineer for Lync Online in Office 365 for three years, with a total of seven years supporting Office Communications Server, Lync, and Lync Online. He spends much of his time creating robust solution assets for Lync Online, but also enhancing diagnostic and troubleshooting tools to help identify and resolve issues quicker.|