Lower Riddings Farm, Denstone, UTTOXETER, ST14 5HW
01543 732032 info@msvconsultancy.co.uk
Committed to IT Excellence

Lync 2013 Powershell – Blank Screen

Lync 2013 Powershell – Blank Screen

Recently I have started carrying out my Lync 2013 installs on to Windows Server 2012 R2 and have noticed a strange issue from time to time.

When I open the Lync Management Shell (PowerShell) from the start menu, the command window opens but I never get a prompt displayed, it just sits there as a blank window, forever!

Lync_Prompt_Issue_1

This is all very odd, I checked the properties of the shortcut so I could check the module being loaded and run it manually.   Remember that the start menu is now located here; C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Lync Server 2013

I copied the string out of the target and ran it in a 'normal' PowerShell only to be returned not the expected prompt but the >> prompt for further input, odd indeed.

When I looked at the string in a little more detail I noticed that there was a missing closing double quote. So I ran the process again but added the " at the end, low and behold I got my command prompt and all my Lync Cmdletts.

So a quick edit to the Lync Management Shell shortcut from this

powershell.exe -noexit -command “cd $env:UserProfile; Import-Module ‘C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1′

to this

powershell.exe -noexit -command “cd $env:UserProfile; Import-Module ‘C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1′"

means that it loads every time.

I am assuming that this is a Windows Server 2012 R2 'bug' as I have never seen it before however it does not always seem to manifest its self as in my last install it happened on only two out of three front end servers.

2 Responses

  1. Babul Mukherjee

    Awesome! Your post saved me some troubleshooting 😀

  2. Cliff

    Hi Matt

    I have had the same problem but the problem seems to be variable. I followed your solution on one server and it worked fine. Then the next server I built had the double quote missing and it worked fine without any change. The third one did have the problem but adding the extra double quote didn’t fix it. In the end I removed the first double quote (the one just before the cd) and it fixed it. seems quite a random problem. Thanks for the original posting, saved a lot of time.

Leave a comment