Our editors thoroughly review and fact-check every article to ensure that our content meets the highest standards. Our goal is to deliver the most accurate information and the most knowledgeable advice possible in order to help you make smarter buying decisions on tech gear and a wide array of products and services. ZDNET's editorial team writes on behalf of you, our reader. Indeed, we follow strict guidelines that ensure our editorial content is never influenced by advertisers. Neither ZDNET nor the author are compensated for these independent reviews. This helps support our work, but does not affect what we cover or how, and it does not affect the price you pay.

When you click through from our site to a retailer and buy a product or service, we may earn affiliate commissions. And we pore over customer reviews to find out what matters to real people who already own and use the products and services we’re assessing. We gather data from the best available sources, including vendor and retailer listings as well as other relevant and independent reviews sites. Please remember to mark the replies as answers if they help and un-mark them if they provide no help.ZDNET's recommendations are based on many hours of testing, research, and comparison shopping. If you have feedback for TechNet Subscriber Support, contact Dave, Please remember to mark the replies as answers if they help and un-mark them if they provide no help. Microsoft does not guarantee the accuracy of this information. Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Locate the Microsoft Clearinghouse Telephone Number for Your Country or Region ĭeploying Remote Desktop Licensing Step-by-Step Guide

If the issue persists, I suggest you Microsoft Clearinghouse to get more efficient support regarding RDS licensing: Please ensure that licenses have been installed correctly, and licensing mode should be configured as Per User. Required for each end-user or device that accesses Windows Server.

In addition a Microsoft Windows Server Client Access License (WS CAL) and a Microsoft Remote Desktop Services Client Access License (RDS CAL – formerly known as a Microsoft Terminal Services Client Access License or TS CAL) are The problem is now with the vSpace software on the host, all of the clients cannot connect to it, they state some 'not valid licensing' error.Īs far as I know, for applications where multiple interactive users are simultaneously sharing a single Windows operating system, standard Microsoft Windows Server licensing applies.

Vspace software