membertriada.blogg.se

Skype for business 2013 server
Skype for business 2013 server











Now… What’s interesting is that if I go back to the same Lync Management Shell shortcut, without making any changes to the Target properties of the shortcut whatsoever, the Management Shell returns a prompt as expected: To test, I ran the Lync cmdlet Get-CsManagementStoreReplicationStatus, which returned what I was expecting: Powershell.exe -noexit -command “cd $env:UserProfile Import-Module ‘C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1’ “ Powershell.exe -noexit -command “cd $env:UserProfile Import-Module ‘C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1’ Note the difference in command, with the additional quotation mark at the end of the second command: Updating the command with the closing quotation mark on the end gave me the result I was after, returning a prompt: At this point I wasn’t sure if this was a problem, but worth investigating :Ĭopying the command and running it from a standard PowerShell instance confirmed it, with no Lync Management Shell prompt returned, but rather a sign of an incomplete string: Looking closer at the shortcut installed on the Start Menu ( C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Lync Server 2013), I noticed that a closing quotation mark was missing from the Target. I was unable to get a prompt from the Lync Management Shell CLI: The last few days I’ve been working on getting Lync deployed into my Hyper-V lab, on Server 2012 R2Īfter deploying the usual prerequisites and Lync 2013 Core Components, I noticed something unusual. Powershell.exe –noexit –command “cd $env:UserProfile Import-Module ‘C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1’” Powershell.exe –noexit –command “cd $env:UserProfile Import-Module ‘C:\Program Files\Common Files\Skype for Business Server 2015\Modules\SkypeForBusiness\SkypeForBusiness.psd1’”

#Skype for business 2013 server windows#

UPDATE: Run the following from an elevated Windows PowerShell session to resolve this issue:











Skype for business 2013 server