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

Similar Messages

Font smoothing settings doesn't consistently work for every login on Windows 2008 R2 when using a RDP client

I'm trying to use the MSTSC client on a Windows 8.1 machine to connect to a Windows 2008 R2 server. In the MSTSC experience tab I checked the font smoothing option. Font smoothing works some times and doesn't work the other times. I don't see a pattern here.
any kind of help is much appreciated.
Thanks,
Prasanna

Hi Prasanna,
Thank you for posting in Windows Server Forum.
As you have Server 2008 R2, there is GPO setting available to specify whether font smoothing is allowed for remote connections.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
Do not allow font smoothing
If you disable or do not configure this policy setting, font smoothing is allowed for remote connections.
You can configure font smoothing on the Experience tab in Remote Desktop Connection (RDC) or by using the {allow font smoothing:i:1} setting in a Remote Desktop Protocol (.rdp) file.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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

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 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

SharePoint 2013 Server OS upgrade from Windows 2008 R2 to Windows 2012 R2

Is it possible to have SharePoint 2013 farm to have mixed version of OS (Windows 2008 R2 and Windows 2012 R2).
We have a request to upgrade our farm servers from WIN 2008 R2 to Win 2012 R2. We have 5 servers in farm -
2 App servers - running with Central Admin, Service Applications, User Profile
3 Web Front End Servers- running web application, search and workflow manager
the database layer is separate on sql 2012 R2
We want to upgrade OS from windows 2008 R2 to windows 2012 R2 and SQL to SQL 2014.
What will be right approach to do OS upgrade in above scenario to minimize the impact of downtime.
May be add windows 2012 based servers in farm one by one and replace the windows 2008 R2 based servers from server.
Regards,
Kunal Abrol

Its possible, but I wouldn't recommend it. The problem is that you can only install SharePoint 20103 on Windows Server 2012 r2 using the slipstreamed SP1 version. I assume that you used the regular version to install on you Server 2008 r2 versions.
Even if you upgrade those servers to SP1 there are some minor differences in the builds between slipstreamed SP1 and upgraded SP1. So although it will work it isn't recommended.
Also, you should be aware the upgrade of inplace SharePoint servers running Windows 2008 r2 to Windows 2012 r2 is not supported.
To upgrade to server 2012 you'll need to add 2012 servers to your environment using the slipstreamed version os SharePoint and then remove the old server 2008 r2 servers as soon as possible. For the period of the upgrade you should be able to get away
with running the farm in a mixed state.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Inplace upgread Windows 2008 R2 to Windows 2012

Hello,
I am testing inplace upgrade from Windows 2008 R2 to Windows 2012 R2. My test server is Windows 2008 R2 Enterprise, Evaluation and is a domain controller. I tried to perform an inplace upgrade, however it failed. The compatibility report says that
Windows Server 2008 R2 Enterprise cannot be upgraded to Windows Server 2012 R2 Datacenter Evaluation (Server with GUI).
I also update the schema first. It went fain and it was completed without error.
Thank you.

Hi,
Based on my experience, it is not supported to upgrade
from a Windows server evaluation version to another Windows server evaluation version. If you want to use Windows server 2012 R2 Datacenter evaluation version, you need to delete the previous operate system and perform a clean installation. Or
you can convert the evaluation version of Windows Server 2008 R2 to a full retail version and then upgrade it to Windows server 2012 R2 Datacenter version.
For more detailed information, please refer to the link below:
Upgrade Options for Windows Server 2012 R2
Best regards,
Susie

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 Server and Windows 8 clients

Hey Guys,
I have had this problem for sometime now and really need a solution. I have Windows 2008 Enterprise Server running about 200+ terminal services clients. All Windows XP clients are fine, Windows 7 clients have issues when they get an updated version of
remote desktop client(to solve the issue we simply rollback the update), Windows 8 clients cannot connect and use out remote app. The issue stems from the newer version of remote desktop client (on windows 7 and embedded in windows 8) cannot connect to our
terminal server and generates an error and immediately disconnects. The error says "
Your computer can't connect to the remote computer because an error occurred on the remote computer that you want
to connect to
So my questions are, how can i update my Windows 2008 Terminal server version to support these clients, or do u have migrate to Windows 2012? Or is there a solution to my current problem which will allow my client to connect and use the remoteapps?

Hi,
Thank you for posting in Windows Server Forum.
Please follow the below steps and verify result.
LAN manager authentication level settings (Local security policy->Local Policies->Security Options->Network Security: LAN Manager Authentication level).
Try to change it to "Send NTLMv2 response only"
Snap:
If still face the issue please install this Hotfix.
RDS client computer cannot connect to the RDS server by using a remote desktop connection in Windows
http://support.microsoft.com/kb/2752618/
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

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.

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.

Restore Exchange 2007 SP3 to Windows 2008 R2 from Windows 2003

Perhaps I'm being dense, but I had Exchange 2007 SP3 installed on a Windows 2003 Server, and I've used "setup /mode:recoverserver" to restore it to a Windows 2008 R2 server... how do I restore the databases which I backed up with the Windows backup tool
on 2003?
I installed KB974674, the restore tool onto the 2008 R2 server but when I try and restore the backup it comes up with "this feature is no longer supported". Something I'm missing here?

These things marked as answers are not answers.
I have now thoroughly tested using setup /mode:recoverserver and it works fine going from Windows 2003 to Windows 2008 R2 with Exchange 2007 SP3, done several installations now without a problem.
"Setup /m:RecoverServer cannot be used across operating systems. A server that was originally running Windows Server 2003 can be recovered only on Windows Server 2003, and a server that was originally running Windows Server 2008 can
be recovered only on Windows Server 2008."
This appears to be wrong, unless someone can tell me why it's right (I haven't tried moving Unified Messaging yet). I've done it to 2008 R2 several times now and also in the other direction, from 2008 R2 to 2003, I can't find anything that didn't work
afterward, although I haven't really thoroughly tested OWA yet, I admit (but it does appear to be working).
I think that documentation is out-of-date as it doesn't mention R2 plus I think it was written before SP3 came out and that paragraph is just wrong.
Basically how I do it is like this:
Dismount databases from the 2003 server and copy the storage group folders to a network location or removable media.
Install the Windows 2008 R2 server using the same machine account that was being used by the 2003 server. Install the prerequisites needed for Exchange 2007 SP3 installation on 2008 R2 (note in addition to the IIS components and RPC over HTTP this
also requires the AD tools in RSAT, which I haven't found mentioned in technical documentation). Install the relevant windows updates.
Install Exchange 2007 SP3 using setup /mode:recoverserver Install the update rollup.
Copy the storage groups into the relevant folders on the new server and mount them. Migrate any relevant certificates (e.g. for ActiveSync).
Obviously then check it all over with the diagnostic tools and check it with EXBPA. The backups are obviously totally different, but really I think you should be using DPM anyway.
To me that was pretty easy to do, to be honest. About 1.5 on a scale of one to ten. Basically install it, recover it, copy over some files and mount them.
Seriously on a halfway decent server I've done it in under an hour.

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 & Windows 2003 RDP Client

Similar Messages

Maybe you are looking for