New
#1
RDP under Build 1607 killing running program on client, upon exit
I've been using Remote Desktop (RDP, mstsc.exe) for over 11 years to access my internet radio station server (Windows 10 64 Bld 1607). Before the 1607 upgrade, RDP always worked the way I need it to (and I PREFER to keep it working vs other options). There are no other programs running on the sever other than Windows Defender and Malwarebytes Premium. I use RDP to run/manage my radio software on the server (SpacialNet's SAM Pro) and for maintaining the server OS and applications, etc.
The server was upgraded first to 1607 (without my acceptance) but I allowed it to remain since the radio stream worked fine. I noticed each time I did a RDP session from my work PC (Win 10 64, Bld 1607), I would get connected just fine and able to do what I did before. HOWEVER -- as soon as I closed the session -- crap happens:
1. Closed the RDP session, the radio stream stopped airing. I RDP'd back in, had to exit the SAM program, restart it and voila, the stream began airing again. As soon as I closed the session, the stream stopped. For now, I have to leave the session connected via RDP if I want to keep it going (that's my current unacceptable option)
2. If the RDP session is in play and I then log into the server from its own console/keyboard, I kill the RDP session on my work PC and again (which kills the stream), I have to exit the radio software, restart it and get it airing again.
3. I tested an RDP session from a Windows 7 PC and the same issue occurs which gives me the conclusion RDP in the 1607 is dorked up. I tested if from my new MacBook Pro retina and same issue -- kills the stream of the program
4. I have triple checked the RDP (mstsc) settings to ensure to "play on remote computer" for sound and even tried the other options only to have the stream die upon exiting.
5. I opened a ticket with SpacialNet (vendor for SAM broadcasting software) and this is the first they have heard of the problem. SAM software has NOT changed in two years so it's not SAM here.
6. I posted the issue (a while back now) on the MS Community and cannot get anyone to give me feedback, direction etc.
Anyone have a decent insight for me on this one?
Will Mangold
Will's Computer Support, LLC