We’ve seen this on a few different Windows Server 2012 R2 deployments. You’ve installed Lync Server 2013 and when you start the Lync Server Management Shell it just sits there, blank. Do we need a picture for this blog to illustrate? Yes.
This is pretty much a known issue. The workaround I’ve found is to simply open a regular PowerShell first. I’ll type a test command in there such as get-service to make sure it’s working. Once that’s open you have a few options, you can run Lync PowerShell commands directly from there. You can run “import-module lync” if it makes you feel better, but Lync commands should work automatically. Or, you should be able to just open your Lync Server Management Shell now. You should be fine until the next login. I’m sure this one will be fixed soon, and it doesn’t always seem to occur, but for now chalk it up to minor annoyance and not something you’ve misconfigured.
If you’re using your Lync Mobile client to make a VoIP call, and a cell call comes in, your Lync call is put on hold. This isn’t so much an issue with Mobility or the Lync client as it is with the design of your phone. A smartphone with a poor cellular calling experience is bad news, so when a cellular call comes in it is given priority over all apps. There’s not much an app designer can do about this. Your best bet when taking Lync calls if you want to avoid this issue is to only make calls via the cellular network. This isn’t a great workaround, however it’s better than unexpectedly having a conference call paused. To enable this, go into the options section of Lync mobile and set Require WI-FI for voice to on. When you make, answer or join a call from Lync make sure you’re not connected to WI-FI. Lync will call your mobile device using your mobile carrier and connect the call this way. An incoming cell call won’t put an existing cell call on hold and your conference or VoIP call will continue uninterrupted. Of course, this workaround only works if you have Enterprise Voice enabled to make an outbound call.
Your other option is to simply enable Do Not Disturb (for iPhone: http://support.apple.com/kb/HT5463) on your device to avoid incoming calls during your conference. This may be easier, but you might miss an equally important call.
As you may have guessed, this isn’t just a Lync issue, it will be an issue with all VoIP applications as long as your phone is accepting incoming cellular calls.
Why? Why would you want to use audio for Lync in an RDP session? Well, many reasons, for me I want to make a test call to watch QoS markings to a tiny office without getting on a flight. That being said, it doesn’t necessarily work out of the box. Here’s a tip that will help you.
First, when you connect, make sure that your local resources in the RDP client allow for both audio playback and audio recording as seen in the following screenshot.
However, you can’t stop here. By default in Windows 7 and 2008 R2 you’ll find that the remote workstation/server will report that there’s no audio recording device available, even if it plays back sound and you can here it. That’s because audio recording redirection is disabled by default, and you’ll need a registry hack (or GPO) to get it going. As seen in this article http://support.microsoft.com/kb/2020918, we need to change the value of HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fDisableAudioCapture to 0 (that’s a zero). Almost immediately, you should be able to record audio, however you might need to bounce the Lync client.