No Sound on virtual Windows 2008 R2 terminal servers

Hello. I have a hyper-v server with 3 terminal servers (in fact there are two hyper-v with a totall of 6 terminal servers).
Hyper-V server is W2K8R2 and so are the terminal servers.
Users connect to the terminal servers using RDP and are unable to play sounds locally on their thin and fat clients.
I installed Desktop Experience and offcourse done the steps below.
Win2008
Start -> Run -> services.msc
Change the Windows Audio service from 'Disabled' to 'Automatic' - and start it.
Lauch the Remote Desktop Session Host Configuration utility by going to START -> RUN/SEARCH -> and typing entering the following command: tsconfig.msc <ENTER>
On the right-hand pane, double click on 'RDP-TCP'
Select the 'Client Settings' tab
Clear/Uncheck the Audio and video playback check box
Log off the system and launch your RDP client.
Before you connect to the system, click the Options button/arrow to expand the RDP session options.
Click the ‘Local Resources Tab’ and under ‘Remote audio’ click the ‘Settings’ button.
On the window that pops-up, under ‘Remote audio playback’ click ‘Play on this computer’ and click OK.
Connect to the virtual machine and you now have sound!
(quick test, you can use START -> RUN -> c:\windows\media\tada.wav (it may prompt you to configure Media Player for first usage).
After this, the users are still unable to play audio in their terminal session.
They have boxes or headphones connected to their devices and are able to play audio local on their fat clients. (Windows pc's)
Does anyone has more idea's?

Hi Brinkman79,
Please ensure that the "Audio service" is running , if it is not enabled please refer to following steps :
To start the Windows Audio service
1.On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
2.If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3.In the Services pane, right-click Windows Audio, and then click Properties.
4.On the General tab, in the Startup type box, select Automatic, and then click Apply.
5.Under Service status, click Start.
6.Click OK to close the Windows Audio Properties dialog box.
7.Confirm that the Status column for the Windows Audio service displays Started.
http://technet.microsoft.com/en-us/library/dd759165.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

How do I enable users to attend on Lync 2013 meeting on Windows 2008 R2 Terminal Services/XenApp 6?

Hi,
We are not using Lync internally. But some of my users need to attend Lync 2013 meetings. We run a Windows 2008 R2 Terminal Services/XenApp environment. Users are not allowed to install applications.
In the past, I was able to install administratively a Lync 2010 attendee client.
How do I enable my users to attend a Lync 2013 meeting?
Thanks.

This is not viable. I don't know which user is going to be attending Lync meetings from suppliers or customers ahead of time and have no contacts to request a test meeting. This is a loop. How does Microsoft expect sysadmins to support their products if
the client software is not easily available.
At this point if I have a user who needs this, I will only know about it after the meeting has failed. At that point the user is not very receptive to the idea of involving his contact in troubleshooting and setting up test meetings. It's even worse if it's
an executive.
Is there any way of pre-installing the pre-requisites for attending Lync 2013 meetings?
My only choice is to inform my user community that we have no way of supporting Lync and request that they use GotoMeeting or WebEx with their contacts who try to do a Lync meeting.
I am very disappointed in Microsoft's approach with Lync 2013.
Thanks for your time.

Windows 2008 R2 Terminal Services, ODBC and Oracle 10.2.0.5 32-bit client

Hi All,
I am setting up an application to work under windows 2008 R2 terminal services/Citrix XenApp which is 32bit. This application uses ODBC connections and not relying directly on TNSName for connection resolution.
I installed 10.2.0.3 and patched to 10.2.0.5, and when trying to create an ODBC connection I only see "junk" in the connections list for TNS Server Name without regard to what exists in the TNSNAME.ORA file.
We have JDE on the same server which uses TNSNAMES and work fine, so I don't think it is Oracle client related directly, but I've not seen this before.
Has anyone seen this before and know how to resolve?
Geoff

Patches are only available to Oracle customers with valid support contracts. If you do have such a contract, pl contact the person in your team who has access to My Oracle Support to download the needed patch. Patches cannot be posted on public servers as this violates ones support contract
Srini

Time Zone Redirect Doesn't work on Windows 2008 R2 Terminal Server

Hello All,
A client has two Windows 2003 and two Win 2008 R2 Terminal servers.
When users from a different time zone login to the Win 2003 server, the time zone of the server changes to reflect their own time zone.　 However when they login to the Win 2008 R2 servers, the time zone on the server doesn’t change.
I already enabled the "Allow time zone redirection" on both Win 2008 R2 Terminal Servers in :
Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Device and Resource Redirection
Yet when the clients login to the 2008 server and checks the time on the server, it still shows local/server time and not their own time zone.
Any input will be appreciated.

Hi,
How are things going? I just want to check if the information provided was helpful. If there is any update or concern, please feel free to let us know.
Best Regards,
Aiden
If you have any feedback on our support, please click
here
Aiden Cao
TechNet Community Support

Windows 2008 R2 Terminal Server.

Hi,
I was wondering about running Adobe Acrobat Std X (10) on a Windows 2008 R2 Terminal Server for two users. Anyone else that have any experience with this? Best solution?
Best regards
Vegard

Although Server 2008 R2 is a supported install platform, you'll have to be extremely careful about licensing - Acrobat is not a server product, so the only person who would be legally permitted to connect to it would be the one who owns the copy of Acrobat in question. Sharing a copy between multiple users is not an option; for that there are dedicated server-based solutions such as LiveCycle.

How to add Windows 2012 R2 RDS to Existing Windows 2008 R2 Terminal Server

I currently have a Windows 2008 R2 Terminal Server running and I am looking to add a Windows Server 2012 R2 server to it. All I see when I google the setup is only for Windows Server 2012 R2 RDS, cant find anything to integrate with a current 2008 R2 Terminal
Server.
Can anyone help with this or point me to a blog I possibly missed?
Thanks.

Hi,
Thanks for your comment.
Yeah, agree with diramoh; as already commented. If you want user session from RDS Server 2012 R2 then you need to install RDS License role on server 2012 R2, purchase and install RDS CAL (per user or per device) according your requirement and then you
can use user session for server 2012 R2 and also for lower version.
But as you already have Server 2008 R2 RDS CAL, then with that you can simply access lower version but can’t manage Server 2012\R2.
For more information, you can refer following document.
Licensing
Windows Server 2012 R2 Remote Desktop Services
Hope it helps!
Thanks.
Dharmesh Solanki

Problems with RH 8 and Windows 2008 64-bit servers with IIS7?

I have been informed that my company's servers are being upgraded to Windows 2008 64-bit servers with IIS7, from Windows 2003 & IIS6. Probably will be online in April 2011.
I have a project created using WebHelp, RoboHelp HTML v5. I have RoboHelp HTML v8 (haven't had a chance to use it yet). We are currently using IE7 on XP. Does anyone have any info on issues with RoboHelp v8 WebHelp projects running on Windows 2008 64-bit servers & IIS7 that I need to be concerned about? I thought I should convert the project developed using RH 5 to and RH 8 project, then FTP it to the new server when it becomes available.
Any helpful info would be much appreciated.
Thanks,
Alden

Acrobat 8 is not certified for Win7, particularly the x64 version. If you got the installation to go, the first step is to update AA8 to at least AA8.2. The x64 with XP required at least AA8.2 and I suspect that has not changed. I would suggest updating to the latest, either from the help menu (until no more updates are available) or by downloading the updates from the adobe.com>downloads page. For the latter, download ALL updates after your current version and install them in ORDER. They are not cummulative in most cases. You only need to reboot after the final update. The updates may get you going. If not, you may simply have to upgrade to AA9 or search for what others have been able to do in your situation.

BSOD Error Windows 2008 R2 Terminal Server

Hi guys
I have a unique issue on a Windows 2008 R2 Enterprise Terminal Server where it keeps blue screening every so often (from every 2 or 3 days to some times once a week) with the exact same BSOD error. After countless hours Googling and researching I am simply
at a dead end and desperately require some guidance if possible. I have ran malware bytes and other tools and the TS does not have any malware or viruses. I have ran a chkdsk and everything is also okay with that.
It has happened about 5 times now with the same errors every time:
29/05/2014 09:42:18
Bug Check String: CRITICAL_OBJECT_TERMINATION
Bug Check Code: 0x000000f4
Parameter 1: 00000000`00000003
2: fffffa80`243c5060
3: fffffa80`243c5340
4: fffff800`01bc70d0
Caused by driver: ntoskrnl.exe
Caused by address: ntoskrnl.exe+75b80
Processor: x64
I have uploaded the DMP to OneDrive: edit: it won't let me post a link until my account is verified?
Thanks
Dan

Hi,
Thank you for posting in Windows Server Forum.
The problem which you are facing seems to be due to ntoskrnl.exe. There might be some corruption in ntoskrnl.exe file.It’s responsible for various system services such as hardware virtualization, process and memory management, thus making it a fundamental part
of the system. It contains the cache manager, the executive, the kernel, the security reference monitor, the memory manager, and the scheduler.
Please check below articles to fix the issue of ntoskrnl.exe.
1. NTOSKRNL.EXE is missing or corrupt
2. How to Fix Ntoskrnl.exe Missing or Corrupt Error
Hope it helps!
Thanks.
Dharmesh Solanki

Java 1.6 u38 stopps working on Windows 2008 R2 Terminal Server

Hello,
I have got a strange behavior on our Terminal Server Farm. We have updated our Servers to Windows 2008 R2. Java 1.6 u38 runs fine, but it stops working suddenly.
Reinstall solves the Problem, but only for several hours. Then some users are not able to use Java from Internet Explorer or direct starting JNLP Applications.
Java starts, but nothing happens. You can see the Java6 Startup Windows with the dots running and thats all.
Admin Users are ables to use Java and some "normal" Users are able, too. After reinstall all user are able to use Java. Next day all servers from our RDS Farm are falling out again.
No eventlog entries or anti-virus entires are present.
Does anybody have an idea whats going on here?
best regards,
Björn

It was a problem with Novell SecureLogin
http://www.novell.com/support/kb/doc.php?id=7007306

Windows 2008 R2 Terminal Services.

Hi,
I am implementing Terminal services in Windows 2008 R2. I have following setup
1. tsgwserver.test.com as TS Gateway+Web Access server (will be accessed using internet). This server is in DMZ zone.
2. tssessionbroker.test.com as TS Session Broker server.
3. tsappserver1.test.com, tsappserver2.test.com, tsappserver3.test.com as TS SH & RemoteApp servers (Application which will be accessed remotly are installed in these servers). Farm01.test.com is created and configured on these servers.
4. Client1 will access the RemoteApp using TS Gateway server using internet. however client2 will access the RemoteApp using local network. These users will be authenticated by AD.
I have installed the above setup but unable to View the applications on remote desktop using web access (client1 and client2). I am missing somewhere in installation/configuration/setup. License server is not installed yet. I am not using certificates
Please correct me if I am wrong with above setup. Please help me to create this setup
Regards,
Rajiv

RD CAP & RD RAP policy are configured and configured RD Gateway setting in RemoteApp manager. Port 443 for ext firewall and 3389 in int firewall are configured. I have checked WMI using MMC and found TS Web Access Computers is listed
for each SH in security setting.
When I select Source Name : localhost in RD Web Access portal, it gives blank in RemoteApp programs and if I use session broker or server farm name, then it gives following messages
RD Web Access was not able to contact the RD Connection Broker server specified. Ensure that the RD Connection Broker server name was entered correctly, and that the server is running and available on the network.
RD Web Access was not able to access server_farm. Verify that the RD Session Host server name was entered correctly, that the server is running and connected to the network, and then try again.
Please let me know which ports I need to configure in firewall to allow Windows Management Instrumentation (WMI) traffic from the RD Web Access server to the RD Session Host server and what authentication settings I need to configure?

Office 2007 Licencing on 2008 R2 Terminal Servers

Hi All,
Is Office on terminal server licenced per user accessing Office? or per user accessing the terminal server?
I am in the process of moving to terminal servers and thinclient rollout.
There are currently around 200 users, connecting to 4 Windows 2008 Terminal servers and all is looking good.
Exactly half of these users will not have access to Office at all, I currently restrict those users by software restriction policies.
I currently have 200 licences for office, 100 of which are being used.
As the rollout continues, eventually there will be 400 users on the terminal servers, 200 of which will use office.
Do I need a total of 400 licences for office? Or will the 200 we currently own suffice?

Hi Brinkman79,
Please ensure that the "Audio service" is running , if it is not enabled please refer to following steps :
To start the Windows Audio service
1.On the RD Session Host server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
2.If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
3.In the Services pane, right-click Windows Audio, and then click Properties.
4.On the General tab, in the Startup type box, select Automatic, and then click Apply.
5.Under Service status, click Start.
6.Click OK to close the Windows Audio Properties dialog box.
7.Confirm that the Status column for the Windows Audio service displays Started.
http://technet.microsoft.com/en-us/library/dd759165.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 2008 R2 Certificate Servers

We have a Windows 2008 R2 Certificate Server that we would like to protect in case of a failure. It is a virtual machine. What are some options for us to consider in protecting this server in case of a business failure to the hardware
or a natural disaster?

In order to restore a CA you need the following:
Backup of the CA's key(s): These only change when you renew the CA certificates, thus to be backed up after setup or renewal, e.g. by using
certsrv.msc, All Tasks, Backup CA, Private key and certificate.
Backup of the CA's database: To be done frequently and automated, e.g. daily by a scripts based on
certutil -backupdb. In case of a disaster you would lose the certificates and requests added since the last backup. You need the database for revoking certificates, issuing or denying requests, and general accounting - so losing some requests does
not break operations.
Backup of the configuration, that is the CertSvc registry key. If you used scripts to configure the CA initially backup those, too, and any
capolicy.inf file that might been used.
In addition or as an alternative you could do a full backup of the VM of course. But I had seen weird things happening to CA keys sometimes so I would recommend to have at least a backup of the key plus a full backup of the machine.
Restore based on the components listed is then equivalent to setting up a new CA with the option 'Existing key and certificate', and restoring the DB and config. after the setup. I would recommend training this process from time to time.
In addition to the CA the services hosting CRLs or OCSP are critical. They could be re-created in principle based on the information available at the CA and new OCSP certificates. So you need a backup and restore or at least the 're-creation' procedure for
those, too.
Elke

Best Practice - IPv6 Turn Off? Windows 2008 (and R2) Servers

Hi,
I work for a large organization. We have close to 10,000 servers globally. A question has come up if we should disable IPv6 on our Windows 2008 servers. Our network is not yet capable of using IPv6.
It seems like you have to go out of your way to disable IPv6; therefore, I would assume that it is best to leave IPv6 turned on.
Does anyone have any thoughts about this. It would be most helpful to have links to pros/cons - best practice.
Thank you.

No, do not disable IPv6. There is no reason to do so unless you have a very specific application issue which is highly unlikely (although there are a few documented ones out there).
http://blogs.technet.com/b/ipv6/archive/2007/11/08/disabling-ipv6-doesn-t-help.aspx
http://blogs.technet.com/b/jlosey/archive/2011/02/02/why-you-should-leave-ipv6-alone.aspx
Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
Whoever marked this as an "answer" obviously doesn't remember that bad-old-days of "Everything's on by default! It just works!!" and the billions of dollars in lost productivity that ensued from the hundreds (thousands?) of exploits that followed this
painfully short-sighted decision. You'd think Microsoft would have learned their lesson from the "IIS is on by default!" debacle, but that doesn't seem to be the case.
Best practices for system administration say "turn off the services and protocols you don't use." As such,
IPv6 should ALWAYS be disabled on servers and business workstations if you're not currently using it, just like any other protocol or service you haven't implemented or aren't using. Not using FTP? Don't install or enable
an FTP server. Not using IPv6? Why would you have IPv6 enabled? Just because IPv6 is the newest, shiniest thing on the block doesn't mean you have to use, and it definitely shouldn't require you to start hacking about in the registry to turn it off.
The only exception to this rule would be laptops or mobile devices where the user might (conceivably) take them into an IPv6 environment. Even then, though, you have to balance the "convenience" of not having to switch-on IPv6 against the risk that
your unconfigured IPv6 stack might be exploitable by nefarious patries. Even so, the fact that almost nobody has switched their internal networks to IPv6 means that turning it off on laptops is still probably a "good idea."
For example, my laptop wireless interface might make sense to leave IPv6 enabled--I don't have any idea when I'll walk into an environment that uses IPv6 and want to use my wireless. But in the office when I'm hard-connected? We don't use IPv6 so it needs
to be "off." Even if it's just a bit of code in the Windows firewall that can be used to say "just reject IPv6 traffic on x interface" is still a big improvement. An absolute home-run would be the addition of logic that allows Windows to dynamically disable
IPv6 when there aren't any NICs or WNICs that are allowed to use it.
Finally, none of this should be construed to mean I'm advising against implementing IPv6, because I'm not. However, like any major technology project you should plan carefully, making sure you understand ALL of the consequences (not just the marketing hype,)
and making sure you'll be able to administer the changed environment as well as your administer the current one. You definitely should not let a vendor (of all things) force the decision to use it upon you because it's "on by default."

Installing Adobe Acrobat 9.0 on a windows 2008 R2 terminal server

We have had Adobe Acrobat 9.0 with our volume license installed on a Windows Server 2008 r2 acting as a terminal server and when clients remote into the server they cannot create pdf's. The box is also a domain controller which is not suggested by microsoft but we inherited it like this. I have tried uninstalling the product and reinstalling it. I ran all updates and still did not work. I also removed everything and then re-installed Adobe Acrobat 9.0 using the "Install Application on Remote Desktop Server" and that did not work (it actually assigned the printer port to a COMM Port instead of the Documents\*.pdf normal port)
Any assistance would be greatly appreciated.

Hi bestteksupport1,
Please check if you meet the system requirements : http://helpx.adobe.com/x-productkb/policy-pricing/system-requirements-acrobat-family-produ cts.html#id_69342
Acrobat 9 has compatibility issues with 2008 R2 Server.
Support on 2008 R2 has been implemented from Acrobat 10.

Windows 2008 R2 Terminal & Windows 2003 RDP Client

Hi
I have Terminal Server Windows Server 2008 r2 and Terminal Server Licensing Windows Server 2012 with RDS CAL installed and activated.
I have the clients with Windows Server 2008, Windows Server 2003, Windows 7 and HP Neoware thin client CA21 with SO 5.0. On my client 2008, Windows 7 able to connect RDP but on the clients Windows Server 2003, and HP Neoware thin client CA21, when connect
to RDP to Terminal Server 2008 r2 receive the error. "Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again".
My question is, How to Fix this error? and able to connect RDP from my clients 2003 and HP thin client to Terminal Server.
Thanks

Hi,
Thank you for posting in Windows Server Forum.
Which version of RDP client you are using for your client systems?
Please update to the latest available RDP client for machine.
On RDS Server 2008 R2, please check following setting and verify. (Part 1 from below article)
1. Start the System tool. To start the System tool, click Start > Control Panel > System Icon and then click OK.
2. Under Control Panel Home, click Remote settings.
3. Click the Remote tab. Under Remote Desktop, Select either option depending on your security requirements:
Select the option “Allow connections from computers from computers running any version of Remote Desktop (less secure)”
4. Click OK and verify.
Apart the issue may occur if a certificate on the terminal server is corrupted. Please try to
delete the registry key for “X509 certificate” to verify. (Part 4 from below article)
You can get all above step by step guide from following article.
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

No Sound on virtual Windows 2008 R2 terminal servers

Similar Messages

Maybe you are looking for