Known Issues
- Known issues with Cisco AnyConnect Secure Mobility Client
- Windows 10 Home does not support Remote Desktop
- Windows 10 S on their home machine could not download the AnyConnect client and did not have remote desktop built in. The 'S' version of Windows 10 can only install apps from the Microsoft Store.
- Google Chrome books are incompatible with Remote Desktop. There is Google documentation that could help. Unknown if it works a t this time. https://support.google.com/chromebook/answer/1649523?co=GENIE.Platform%3DDesktop&hl=en
- SAPGUI has issues with the VPN when connecting from home
- Working from home without wifi > see Ticket #1278360
- Port Forwarding
Help with Microphone and RDP sessions
When using RDP/RDC there is a default setting that disables the local microphone connection from the remote computer. There is a simple fix that I have described in detail below. I offer this due to the large (and increasing) number of staff working off-site who may need to use remote resources for communication but who may not be literate enough with RDP/RDC to know about this nuance.
I start my RDP/RDC session by entering “MSTSC” from the Windows Menu as shown:
This brings up the well-known dialog box used to initiate the RDP/RDC session:
Instead of clicking “Connect” click on “Show Options”:
Then navigate to the “Local Resources” tab:
Under “Remote audio” click “Settings”:
Note that in my example I have selected “Record from this computer”. This is not the default setting and is the reason some users may not be able to use headset microphones when using RDP to access Teams, WebEx, Skype, or other teleconferencing utilities over an RDP/RDC session. Clicking “OK” does not reset the default, so this setting much be checked prior to each RDP/RDC session. This may be common knowledge for the CSC already, but in case not I wanted to make sure the knowledge was shared. If you think it would be worthwhile to build a KB with these instructions I would be happy to do so.
Very truly yours,
Cameron D. Ward