RDP Client Licenses; Server 2008 R2

MS documentation indicates that there is a 120 grace period for purchasing RDP licenses. From what I have read, there seems to be no restrictions on the number of users allowed to RDP in when licenses have not been obtained.
But Some have said that you may only be able to have a couple of users on the system -----which, again seems contrary to any literature I have seen,
Anybody got a clue?
thanks
a bunch,
Spatio

Hi,
There are no restrictions during the grace period. Without RD Session Host (RDSH) installed the limit is 2 Active sessions. The grace period begins when RDSH is installed.
-TP

Similar Messages

Printing problem with Konica Minolta BizHub282 using RDP on Windows Server 2008 R2

Hello,
I have an office setup as follows: Local office IP adress scheme 192.168.201.x. There is a Konica Minolta BizHub 282 printer connected to the 192.168.201.x network as well as around 10 workstations running Windows 7. There are also about
10 additional teleworkers WHO DO NOT NEED print access to the Minolta 282. All of their data is on a cloud server. I have them setup to first connect to the cloud server using a RRAS PPTP VPN and then to start an RDP session to the separate
RDP server. The Konica Minolta works ??okay?? with the easy print services and until now, we have just dealt with the lack of features and the occasional print job that goes crazy and prints out 400 blank pages (btw, this is usually on Excel) or a job
that cuts off the margins even when you have it set to "fit to page" (this usually happens in Adobe.) When I originally set this up, I tried loading the native Konica drivers on the server, but there was no joy because I couldn't get it to
work using the native drivers. The problem at hand is a feature called "account track." This feature authenticates your print job by using an account code. If there is no code, the job just disappears. When I load the native
Konica driver, the ability to turn on this feature is greyed out (see below):
When I use easy print, the codes seem to go through, but as I mentioned earlier, sometimes the print job just goes insane. After researching this, it seems to me that there are two ways to overcome this if we can't turn off the account track feature:
1) Overcome the driver problem. I've tried both of their current drivers without success: VXL and Visual Postscript. When I login to RDP, the (redirected) Konica 282 printer is listed, but when I try to print, it fails due to the missing account track code.
I'm hoping that there is a registry hack to turn this feature on by default with the code or a driver version that works with RDP. They have a WHQL driver available, but it didn't work any better. Is there a way to report this issue to the WHQL labs? Maybe
I can light a fire under Konica's rear end and motivate them to fix the driver.
2) I saw one discussion where the guy installed the printer out in the clouds as a local printer. He seemed to have a site-to-site VPN, not a client-to-site VPN, so this worked. Is there a way to do something similar when the customer connects to the
VPN through standard "connect to workplace" setup? I tried pinging the Konica 282 from the server while logged into the VPN, but the printer could not be found.
3) I considered setting it up as a google cloud print prnter, but that would require everyone to setup a google account and add a layer of complexity.
Anyone else run into this and have a solution? If not, does anyone have any ideas on a solution or workaround?
Thanks,
Jeffery Smith

Hi Jeffery,
Thank you for your comment.
Yeah, you can use universal print driver by configuring Remote Desktop Easy print on RDS Server. Install the driver on RDS server. Now to configure Easy print you need to have minimum client RDP 6.1(But suggest you to install RDP 8.1), .Net Framework 3.5 or
above and RDSH role.
Also under GPO setting need to check below settings.
Do not allow client print redirection: Disable
Use Terminal Service Easy print printer driver first: Enable
Computer Configuration > Administrative templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer redirection
For more information, you can refer below articles.
How to configure Microsoft RDS Universal Printing
http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/microsoft-hyper-v/how-configure-microsoft-rds-universal-printing.html
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx?Redirected=true
Hope it helps!
Thanks.
Dharmesh Solanki

RDP Printing on Server 2008 /R2

Hi, I have a server with windows 2008 r2 and clients running rdp 6.0 on windows 7, the problem is that the clients send to print to the server printer but nothing happens, I made a rdp installer and after this they can log on but not
print, before this rdp installer the printing was ok, they had a mstsc shortcut with printers enabled but now with the installer icon this option is not present.
thanks in advace

Hi,
Initially please try to use latest version of RDP client v8.1. After that also try to apply RD Easy Print service and see whether it can make any difference.
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
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]

Licensing Server 2008 R2 RDS with SPLA licenses?

I haven't used SPLA for doing any RDS licenses and am having trouble finding info on where to get the licenses.
Where do I get licenses from? I can't find any info on the SPLA site or on the Microsoft Volume Licensing Service Center site.
Thanks!

Hi,
Please contact Microsoft Volume Licensing Centers to get professional and accurate response, you can find corresponding phone number for your region here:
Microsoft Volume Licensing Activation Centers Worldwide Telephone Numbers
http://www.microsoft.com/licensing/existing-customers/activation-centers.aspx
In addition, here is a related blog below for you:
Licensing How To: When do I need a Client Access License (CAL)?
http://blogs.technet.com/b/volume-licensing/archive/2014/03/10/licensing-how-to-when-do-i-need-a-client-access-license-cal.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Rdp client to windows 2008

Are there possibilities to connect to win ser 2008r2 from a apple platform

And if there are TS/RD CALs involved on the server, go here:
http://social.technet.microsoft.com/Forums/en-ZA/winserverTS/thread/8e28b0af-b37 4-4ca0-a255-5fd854bdc7fa
Search for string "RESOLVED!" on the page and grab the leaked RDC 2.1.2. It solved the CALs issue for me.

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

Do I need to install user licenses to RDP to the server?

I have a 2003 terminal server running an app that is accessed by only a handful of users. Users remote desktop into the server to use this app. The app is licensed for the handful of users.
The app needs to update to the latest version and does not support server 2003. I have a server 2008 r2 (virtualized on hyper-v 2012 r2 server) with the RD session host role installed.
Before installing the RD licensing role, I checked the 2003 term. server license configuration and there's non. So, it looks like licensing per user or device has not been setup. My question is, do I need to setup licensing for this scenario?
Please let me know if you have any questions.
Thanks,
Alex

Hi Alex,
Thank you for posting in Windows Server Forum.
Based on your description, you have updated your server from 2003 to 2008 R2 and now need to take remote access for that server by users for running application.
Yes, you need to setup licensing for your scenario. Server 2003 license\CAL will not work with server 2008 r2 but vice versa is possible. So you need to install RD License server 2008 R2, activate the license server, upgrade\purchase the RDS CAL (Per User or
Per Device) and then configure that CAL to use by the users. You can directly contact MS Clearing house with all your license document, explain them whole scenario and they will help for your situation.
Please refer following article for more detailed information.
Remote Desktop Licensing Manager
http://technet.microsoft.com/en-us/library/cc732684.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

How do RDP clients obtain license from host/license server?

Hi,
I have a W2k8 R2 server setup with Remote Desktop Session Host and Licensing. This will be used to allow more than 2 RDP connections to a server.
Can someone explain the process from the client side, getting the license from the host/licensing server, then connect to the server they need to manage?
What configuration is needed on the client/server side to know it needs check for a RDP license?
Thanks in advance,
J

Hello,
Below is the licensing guide for Remote Desktop Services.
http://technet.microsoft.com/en-in/library/dd983943(v=ws.10).aspx
How the connection works,
The clients will first connect to Remote Desktop Session Host. The Session host will forward it to the License Server.
You have the option to tell the Remote Desktop Session host to say which is the license server it should contact. Check this link below to see how to do this.
http://hookorcrook.net/2011/12/19/configuring-remote-desktop-services-licensing-server-windows-server-2008/
All the CAL licenses will be installed and configured in the License Server.
There are two types of CAL licenses - Per User and Per Device CALs. Based on the type of license available in the License server, the license will be obtained and the user's connection is forwarded to the Remote Desktop Session host server.
If no license is available in the Licensing server, it will fail there.

Client License applicable in windows server 2008 R2

Dear Sir/ Madam
I have purchase a windows server 2008 R2 and install properly and make this machine a Domain Controller. I have connected 5 client user with this machine because Microsoft provide 5 client access default windows server 2008 R2, now we need to access more
client from this server machine. so we have purchase some more license from Microsoft then how we install / implements or apply these license for client.
does these license install on server. ?
does these license install on client. ?
we have the following details about license.
Authorization Number:
License Number:
Distributor Purchase Order Number:
License Date:
Agreement Information:
Reorder/Software Assurance End Date:
Please resolve my quire.
Thanks & regards
Krishna +91-8459060870

Hi Krishna,
Thank you for posting in Windows Server Forum.
From your description it seems that you have purchased CAL for your client to get access. Whether you have purchase simple server CAL or RDS CAL (Per user or Per Device).
If you have purchase RDS CAL then you need to have install RDS License role service and then first need to activate the RD License server. After activating we can configure the RDS CAL on RD License server and for this you might need to call the MS clearing
house, explain them your situation and they will help you to activate and configure everything. After that we also need to point our RD License server to RDSH server.
For more information, you can refer below article.
Configuring Remote Desktop Licensing
http://technet.microsoft.com/en-us/library/cc754309.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

RDP License Windows 2008 R2 activate at Windows Server 2012 R2

Hi,
Is it possible to activate Remote Dekstop License Windows Server 2008 R2 at Windows Server 2012 R2?

Hi,
Thank you for your posting in Windows Server Forum.
First please specify, are you talking for RDS CAL or RD License Server?
As suggested by diramoh, if you want to have Server 2008 R2 RDS CAL for Server 2012 R2 then it can’t be possible. You need to have CAL version corresponds the software version it access. Newer version of RDS CAL (say server 2012 R2 can be used for Server 2008
R2). Please check the below matrix for RDS CAL interoperability.
RDS and TS CAL Interoperability Matrix
http://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Remote desktop connection issue with an RDP client while connecting to some of windows 2008 and 2003 operating system flavors and not receiving SDin value choice 26 from DomainMCSPDU

Hi Team
We have our RDP client and i came across with one issue "Expected data got 3" with this client.
This issue is getting while connecting some of below operating system flavors.
Microsoft Windows 2008 Enterprise edition
Microsoft Windows 2008 Standard edition
Microsoft Windows 2003 servers
When we are trying to get RDP to those servers with our client, getting "Expected data got 3" error. One more main thing here is the specified error is not getting for all the servers of same operating system in above list.
Able to get the RDP console for those servers using mstsc client.
When i read the [MS-RDPBCGR] specification, i found the below points
mcsSDin (variable): Variable-length PER-encoded MCS Domain PDU (DomainMCSPDU) which encapsulates an MCS Send Data Indication structure (SDin, choice 26 from DomainMCSPDU), as specified in [T125] section 11.33 (the ASN.1 structure definitions
are given in [T125] section 7, parts 7 and 10). The userData field of the MCS Send Data Indication contains a Security Header and a Valid Client License Data (section 2.2.1.12.1) structure.
In my code i am not getting SDin value as 26. Is it the problem with Remote desktop Licensing in RDP servers as specified in the specification like "The userData field of the MCS Send Data Indication contains a Security Header and a Valid
Client License Data (section 2.2.1.12.1) structure."
Could you please explain me is this issue is happening due to Licence configuration in RDP server and please provide support with server side configuration if any because our code works for other servers ?
Thanks & Regards,
Pavan G.

Hello Pavan -
Thanks for contacting Microsoft Support. I'm researching this for you and request you to please send me mail at dochelp @ Microsoft dot com so that I can share tools and techniques to collect some traces and analyze.
Thanks.
Tarun Chopra | Escalation Engineer | Open Specifications Support Team

Server 2008 TS - some client could not connect to the server

Hi guys,
I have a Server 2008 x64 Terminal Server with license server (some machine) and installed device CALs.
I can connect with Windows 7 client to Terminal Server by RDP (TS assign device CAL to every connected machine automatically) without problem, but I get this error message if I try connection with Motorola (Symbol) MC8080 mobile scanners:
"Because of a security error, the client could not connect to the remote computer.
Very that you are logged on the network, and then try connecting again."
I tried different settings by KB2477176 and activate/deactivate server, but it didn't solve the problem.
http://support.microsoft.com/kb/2477176/hu
(These scanners can connecto to another Terminal Server.)
Is it client or server-side issue?
Have you another idee?
Regards,
Gabor

Hi,
Thank you for posting in Windows Server Forum.
Please again cross check whether you have properly configured certificate attached with the server. Because the error which you are facing is generally due to corrupted certificate on server side. As you have already tried, I again want you to back up the registry
setting and then remove the X509 certificate registry key under below mention path, restart the computer and reactivate the RD Licensing Server.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
You can also refer below article for additional information.
How to resolve the issue “Remote Desktop Disconnected” or “Unable to
Connect to Remote Desktop (Terminal Server)”
Hope it helps!
Thanks.
Dharmesh Solanki

Problems with RDP/RDC from Mac OSX to Windows Server 2008 on External IP

We have a customer that is using Mac and Microsoft's RDC for Mac to their servers.
They've just upgraded from Windows Server 2003 to 2008 and can't connect through RDP to their TS server on external IP.
Their servers is not in any domain and it work for them to connect to another Windows Server 2008 that is located in their office when they use internal IP.
The problem is that when using RDC to the external IP they get bellow:
"Remote Desktop cannot verify the identity of the computer you want to connect to. This problem can occur if:
The remote computer is running a version of Windows that is earlier than Windows Vista.
The remote computer is configured to support only the RDP security layer.
Contact your network administrator or the owner of the remote computer for assistance."
From here they can choose "Connect" as they did on the Server 2003 but now they get: "Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.Try reconnecting to the Windows-based computer, or contact our administrator."
and is only able to choose "Ok".
I've changed the settings on the "configuration for host server for remote desktop sessions" under General from "RDP-Security Layer" to "Negotiate" and in this case I get a logon windows where i type in all my information click logon. Here I get another
error message which says something like: (We get it in Swedish). "Connection to the windows-based computer broke since there was a problem associated with the licensificationprotocol... Try to connect again" Where I can choose "Cansel" or "reconect"
but it just keeps poping up if i chose reconnect.
I've tried all settings in the TS server and there is not much to change on the RDP client. We have installed the server certificate on the Mac client but it didn't help.
We've also tried with CoRD and it works fine as RDP from a normal Windows based computer.
The only solution I've found on google is to use CoRD instead but we got problems with that connection since it keep crasching on our computer.
In my eyes the problem is on the security requirements that the RDC for Mac needs but I can't find any inforamtion on MS sites about it.
Greatfull for all tips and trix!

I too was having the problem same as everyone else. However, for me the problem all started when I replaced my SSL certificate that was used/selected in the Remote Desktop Session Host Configuration utility, connections, RDP-TCP Properties. The security
layer is negotiate and the certificate is the one selected on that screen. It was not licensing related.
The certificate had expired and I didn't believe I needed it. But turns out I did, so I had to generate and validate a new one using GoDaddy (though they specifically were not part of the problem). As my Terminal Servers (Remote desktop servers)
do not have IIS installed, I was a bit stumped on how to create a new certificate request. I finally found some instructions on how to create a certificate request using the MMC snap-in, advanced operations, create custom request. The template
chosen was "legacy key", and without boring the rest of the details that part was the root cause of my problem. The legacy key was not able to be processed correctly by the Mac RDC client. Neither the official 2.1.1 client or the 2.1.2 download.
The Terminal Server system event log was showing the following two errors, 36874 and 36888. The first one contained the best details and said: "An TLS 1.0 connection request was received from a remote client application, but none of the cipher suites
supported by the client application are supported by the server. The SSL connection request has failed." Upon searching the internet for that, I found this page which described the legacy key problem:
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/3a2d2eec-000d-432a-abd7-6b965268c671
So, my solution most familiar to me was to use IIS and create the SSL certificate request, process that with my 3rd party CA, export the certificate with private key and then import that certificate into all of my terminal servers. Then using the session
host configuration tool, pick the new certificate and the problem was now solved.

Server 2008 R2 Terminal Server c0000005 and c0000006 errors with KERNELBASE.dll error in RDP sessions.

We installed a new Server 2008 R2 server this spring. It is configured as a Terminal Server with 16 Wyse t10 thin clients connecting with RDP. We are a small resort so we run Springer Miller Host and SpaSoft. Ever since moving from PCs to the thin clients
and TS we have been seeing SpaSoft randomly crash with KERNELBASE.dll errors and also a lot of c0000005 and c0000006 errors. Springer Miller support says its a Microsoft Networking issue so no help there. The company we worked with to install this has no clue
so I hope to reach out to this community to solve this. I can also open support case with Microsoft Support but I am not sure if they will be of any help. Here are some examples of the errors:
"Event 1000
Faulting application name: SpaWin.exe, version: 3.4.0.0, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86
Exception code: 0x0eedfade
Fault offset: 0x0000c42d
Faulting process id: 0x3718
Faulting application start time: 0x01cf9ac7922487e9
Faulting application path: \\spasoft\spaapps\TermServ\SpaWin.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: cfdcf9a9-06ba-11e4-a5af-000c298d9aa5"
Also:
"Faulting application name: VH.EXE, version: 18.80.430.0, time stamp: 0x3f73b447
Faulting module name: VFP8R.DLL, version: 8.0.0.3117, time stamp: 0x3f73c232
Exception code: 0xc0000006
Fault offset: 0x0001d598
Faulting process id: 0x2bc8
Faulting application start time: 0x01cf99297ee1742f
Faulting application path: J:\HOSTPLUS\fxp32\VH.EXE
Faulting module path: J:\HOSTPLUS\fxp32\VFP8R.DLL
Report Id: 5fbc65c4-055c-11e4-a5af-000c298d9aa5"
And:
"Faulting application name: SpaWin.exe, version: 3.4.0.0, time stamp: 0x2a425e19
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x2aa0
Faulting application start time: 0x01cf988e6770e619
Faulting application path: \\spasoft\spaapps\TermServ\SpaWin.exe
Faulting module path: unknown
Report Id: 01029179-04b9-11e4-a5af-000c298d9aa5"
There are no network specific errors in any of the logs. I am thinking that SpaSoft needs to be run as an administrator but I am not sure how to do that in this environment. We have disabled DEP for all but essential Windows processes. All of the firewall
and AV has been completely disabled, and still getting these errors. Is there a way to run these applications as admin without the user actually being an admin? Should I go ahead and open a Microsoft support case? Thanks

Hi,
Thank you for posting in Windows Server Forum.
Explanation
The indicated program stopped unexpectedly. The message contains details on which program and module stopped. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.
User Action
If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.
Yeah, you can open a support case with Microsoft as they will help and guide you for proper solution. You can go through
this source article.
Hope it helps!
Thanks.
Dharmesh Solanki

Cisco Security Manager Client running on Windows Server 2008 R2 (64 bit) in Terminal Service

Hello CSM Gurus,
Would there be any performance issues in CSM client software design if multiple instances of CSM client by multiple users ran concurrently on a Windows Server 2008 R2(64 bits) while CSM users accessing the server via Remote Desktop Services ?
In my environment, we have a CSM server at our major data center while security administrators from all over the world need to use this CSM server.
In order to overcome the latency of the CSM client due to the WAN network, the plan is to use a Windows Server 2008 R2(64bits) as a terminal server and all security administrators would need to access this terminal server via RDP and would launch CSM client on their desktop. The terminal server locates on the same LAN as the CSM server itself in order to minimize network latency in communications between the CSM clients running on the terminal server and the CSM server. there would be multiple instances of CSM clients running concurrently on the Windows Server 2008 R2, the terminal server.

Hi;
please check
Oracle Database 11g Release 1 (11.1.0.7.0) <<Oracle Database 11g Release 1 (11.1.0.7.0) for Microsoft Windows Server 2008 x64
http://www.oracle.com/technology/software/products/database/oracle11g/111070_win64_2008soft.html
Check Database 11g Release 2 Certification Highlights [ID 1065024.1]
But please check this thread
client 11gR2 install on Win 7 Pro fails java.lang.NullPointerException
Regard
Helios
Edited by: Helios- Gunes EROL on May 14, 2010 4:49 PM

RDP Client Licenses; Server 2008 R2

Similar Messages

Maybe you are looking for