You use Remote Desktop Connection to establish a connection to the server from the client computer. In this situation, no local audio device is assigned to the session. Note On a Windows Server based terminal server, you can see and use the audio device that located on the server during the remote session.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request.
The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:.
If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows Server R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:. The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time DST bias.
My first thought is to install a virtual audio driver to emulate the sound stream over the RDP session. But here is a much easier way. All you need to do is turn back on the Audio Redirection option that is disabled by default from the beginning. Go to Client Settings tab, and uncheck Audio and Video playback option from Disable the following list section.
The Remote audio playback option on Remote Desktop Client is also need to be configured in order to make the redirection work. The option is enabled by default. Great tip! As well, if I log in directly and start an audio application like Foobar and then go to my notebook and RDP into the computer, the audio stream is stopped.
I'm not sure what else I can do and any additional help would be appreciated. I'm not sure what else this can be. Yea, I had mentioned this in the first post. When I'm logged on directly to the console, all audio works perfectly. Probably worth finding out if the audio channel over RDP is broken or not Redirecting audio to my notebook, by seletcting 'Bring to this computer', does work which makes this even more frustrating to understand.
The switch also allows connections when a TS is in drain mode. All sessions in Vista and are virtualized, there is no more "console" session that you can log into. However, it's not relevant to your problem, so I'll drop that now. Thanks for the info, cluberti. Hmmm - I'd like to see what happens with an RDP 6. I hate to say it would be time to contact Microsoft for help, but you do get some free support with that Server license. Since it might be a bug, you'd probably want to contact them directly at this point, since you know the client side of things did indeed work I still haven't found a solution wihen using RDP.
There might be a limitation that a RDP server can not be rebooted without local login more than once a day. This however results in that session 0 console loades the audio-driver or mixer. But when you connect using RDP another session session 1 will be started and thus results in windows complaining that "can not load driver" due the fact that it has already been loaded.
To get around this try connecting to session 0. But it has been replaced with mstsc. Using mstsc. You might have to change that user's permissions to be able to load drivers. I'm experiencing this same issue on my Windows x64 Server. Very annoying!
0コメント