Hey Guys,
I have it working the way you described… Basically I have a PC that auto logs in and I can remote into it when I need to update it. Then I restart the machine and everything comes back the way it should…
I really appreciate your help on this… Great job!
I use Teamviewer all the time. You can get into an issue with your graphic drivers and Teamviewer, but generally it plays nicer than Remote Desktop in every way.
I am in the middle of setting up a Roon/HQPlayer demo unit to try and test DSD512 with a T+A DAC8DSD dac. Currently, I have the computer to auto-login to Win10, Teamviewer, RoonServer and HQPlayer and the local Wifi network setup with my phone’s hotspot functionality. As of now. I turn on the hotspot, turn on the pc, wait a bit and I can start using Roon on the phone directly to the stand alone. I have Teamviewer avaialble if I need to see the desktop and I’ve pre-loaded the T+A drivers. Deciding now, whether to add a NVIDIA card in or chance that the i7 4790 will have the horsepower to do DSD512. Can’t test it at home and there are other people from Computer Audiophile forums who might be meeting up with me to do the listening and I don’t want to waste their time if it goes south.
Must check this out on my W10 headless setup when I move my ps audio USB connection back to it
There are a couple of things that can be done here. First off, you want to be sure that remote desktop isn’t redirecting audio to the client (viewer). This is an option on the client. On the Mac RDP client you select “Sound: Play on Device” in the redirection settings.
This fixes issues during the session, but once you close the session it goes into a limbo state where it isn’t connected to anything (and therefore no devices). If you close the session by either closing the client or selecting “Disconnect” on the host PC then you’re stuck. You can, however, close the session by redirecting it back to the console and for this you need to use the command line.
Open up a comand window and enter:
query session
This will return a list of all of the currently active remote desktop sessions. If you look in the ID column it will give you the Session ID number. Find the one for your current session (likely 1 or 2). Then:
Say, for instance, your session ID is 2. You would enter:
tscon.exe 2 /dest:console
That will disconnect your current session and re-connect it to the console (at which point it will have access to all of the system devices)
At one point I wrote a batch file to automate the discovery of the Session ID and then feed that value to the tscon command, but I’ve since lost it.
Ultimately, I found it easier in the long run to use VNC to connect to the machines which need to interact with local audio or HID devices. TeamViewer and Splashtop work equally well, but I prefer the light footprint of VNC for local control.
I find this as well, and not just for local audio interaction, but to avoid all the issues that come with the unique model of WIndows Remote Desktop.
I haven’t seen Quad ESLs in years!!!
Lust…
They’re still going strong…
That network diagram in this thread is now outdated. I have my Core Server now on a NUC running ROCK, using HDMI to connect to the home cinema AVR.
Same problem with logon works, log off=not,
I am using Server 2012r2 with HyperV, Roon server was on the host originally but that was flaky at best, so built up a dedicated VM to run as the roon server, as soon as I tell it to log off it kills roon. Is there NO way to run this as a background service and not an App?