ProblemI came across an interesting issue yesterday..opening the Lync Management Shell I was presented with a blank shell window (nothing unusual there, just wait a few seconds, right?). However it just stayed right there, no connecting.
The environment is really a 4 site deployment with a total of 4 2013 front ends all running on Windows 2012 R2.
What was really interesting was that there was no errors, nothing...
I fired up power shell and tried importing the Lync module just in case my Lync Server Management Shell shortcut had somehow been corrupted and that worked fine.
So off to have a look at the shortcut I noticed that the decided to fire up the target manually in an attempt to isolate the culprit.
Looking a little closer at the target I discovered that the closing quote was missing. Now how did that happen?
Interestingly this issue happened on 2 of the 4 front ends within the same deployment. I have done many of these and not seen this before so am not sure what the underlying cause is. Perhaps a bug :-)
SolutionSimply edit the target and add the missing close quote as seen below.
Ripleys- Believe it, or not
I went back to the Front End where the Lync Management Shell was working..to my disbelief its target is missing the closing quote BUT it works anyway. Adding the closing quote to the working target made no difference. Unbelievable.
Of course you can simply fire up Power Shell and then import-module Lync