Headless Servers

[tmorten]

This isn't specifically NetRemote related, but I'm hoping others may have a similar server configuration...

Is anyone else out there running their music server without a monitor attached?

I notice that when I use XP Remote Desktop Connection, even if I select "Leave at remote computer" for Remote computer sound, I get a message that says "There was an error starting playback. Make sure that your system has a valid sound playback device and that it's properly configured in playback options."

Looking at the Sound and Audio Devices Properties when connected remotely, I note that the only possible selection is Microsoft RDP Audio Driver (which would seem to indicate that my desire to leave the audio playback on the server was ignored).

I'm running Server 2003 with all the latest updates on a Hush Mini-ITX, and connecting with XP SP2. Any advice?

Many Thanks,
Tim

[Ben S]

The one thing to know is that if you forgot to do this once, a server reboot is required (as far as I know).

[Aaron]

I've been using XP in a headless config for 3 years now as mu Homeseer server... works perfectly.

[tmorten]

I tried a reboot, but to no avail. Some web chatter seems to indicate that others have had this problem, and have had to resort to a local login running at all times.

That said, it definitely works for some people, so there must be something about my configuration. I saw one post elsewhere that indicated different results using different clients, so I may try from some alternate machines later today. Definitely frustrating though... thanks for the feedback!

- Tim

[Aaron]

If you are running applications that do not run as a service you must have it logged in at all times... definitely. But you never stated if you were.

I've run hundreds of Win2003 servers (last job I ran 1400 windows servers) and RDP works just fine, fantastic actually.


If you are running RDP and connecting to the console session remotely and you want to dicsonnect and give control back to the interactive session (local) then use this command to disconnect...

%windir%\System32\tscon.exe 0 /dest:console

If you are not running any apps that need to be logged in to run then I suggest rebuilding the OS if you've already applied all SPs and patches.

[avid]

An alternative that works well for me is VNC. I leave the HTPC logged in all the time and access that main logged-in session over VNC's remote control. Sound stays with the HTPC.

The HTPC has no monitor as such. Its monitor is the TV screen and only occasionally will I switch it on when playing music - just for the G-Force visualizations.

I have run this way now for over 2 years. But VNC works quite differently from RDP, so it might not suit everyone.

Brian

[tmorten]

Thanks for the tip; I'll check out VNC.

To Aaron's comments: I just run JRMC and Girder on my server. Remote Desktop works great except for the audio problem...

It seems that no matter what I do on the client side, Server 2003 insists on using the RDP Audio Driver when I connect remotely.

Cheers,
Tim