Hot answers tagged terminal-server-licensing
5
You need to install Terminal Server in application server mode, when you originally installed it looks like you did so in remote administration mode, which allows only 2 connections. You need to go into add/remove programs and and got to add/remove windows components, run through the process, with out selecting anything to install, it will then ask you what ...
4
You will need to purchase the 10 server CALs as well as the 10 RDP CALs.
The server CALs are needed so that the users are licensed to talk to the Windows 2008 R2 OS. If you already have Windows 2008 R2 CALs then you don't need to purchase more.
You can not use the default 2 admin RDP connections. Those are not RDP CALs as they are built in for remote ...
4
Uninstall Terminal Services. Windows Server has Admin RDP built in w/o TS.
Uninstalling/Reinstall usually isn't necessary, though some apps might break. It depends on what you have installed.
On a professional note: You should be carefully planning your server deployments, installing only what is necessary for the server to serve it's function. You should ...
2
Found the answer to my problem. From the note on the bottom of the page on Troubleshooting TS Licensing Installation:
Important
To view the configuration details of a Windows 2000
or a Windows Server 2003 license server, you must provide the
credentials of the built-in local Administrator account on the license
server. The credentials of any ...
2
@Sam: If I'm not mistaken, the process you outlined in your answer is valid for W2K, not W2K3. In W2K3 remote desktop for administratoin is "installed" by default and allows for 2 concurrent connections (3 if you include remote desktop to the console). Installing the Terminal Services role puts the server into "application" mode. The confusion (IMHO) comes ...
1
Microsoft licensing is so complicated they actually have a certification for it.
Okay, here's the lowdown:
For each client connecting to a Windows Server (any kind of service), you need 1 CAL
In addition, to activate Terminal Server so that it can serve more than 2 RDP sessions, you need 1 TS CAL per client who wants to connect.
When you've applied TS CAL ...
1
According to this link and this one, the attributes you mention were first introduced with Windows Server 2008; so, yes, upgrading the AD schema to 2008 level should fix your problem.
It's a totally safe operation, even if you don't plan to add any 2008 DC to the domain any time soon. Just ensure all your DCs are online, replication is properly working, the ...
1
The "security keys" you mention appear to be LDAP attributes (I'm not personally familiar with these ones, but they follow the standard naming convention) so you'll need to use adsiedit.msc (available in the Windows Server 2003 Resource Kit) to get at them.
The schema upgrade via adprep is a good idea. As well as bringing on these attributes it will give ...
1
adprep, schema update, etc would not solve your problem i think.
upgrading schema is no prob, cause you would have to do this also if new dcs come in.
in my case i have native 2008 r2, sure migrated from 2000 to 2003, to 2008 r2,
and also 2008 r2 ts, ts lic, everything nazive in 2008 r2.
but same effect.
do not see any problems in real environment but also ...
1
I was actually troubleshooting a different issue today and dcdiag threw this interesting tidbit up:
Time Generated: 05/04/2012 11:32:43
Event String:
The Remote Desktop license server cannot update the license attributes for user "firstname.lastname" in the Active Directory Domain
"myflo.enets.local". Ensure that the computer account for ...
1
The license allows you to run two VM on the same hardware without purchasing any other server license. However, in this case, you will not be allowed to run anything on the host OS (the one running on the hardware) than the hypervisor itself: you'll have to run AD, RDS and all other windows services in the VMs.
1
Also you have a choice when buying Remote Desktop Services CALs (RDP). User based or device based, there is no "concurrent" session option as there is with Citrix XenApp. User based will mean a single user account can connect from anywhere, but it's tied to their account. Device based means every device that connects will take a license and not give it ...
1
The two SBS servers wont live on the same network unless they're Premium. Then it takes some additional configuration.
Unless you've got the licenses on paper, or have access to them electronically, you don't really have those licenses. If you've got access to the license keys than its just a matter of setting up the licensing service. I'd recommend doing ...
1
We're a few versions back on Citrix PS 4.0. In our system we run the Citrix license server on a separate server and TS Licensing server runs on a domain controller. I think at some point the TS Licensing server would only run on a DC. This now reminds me I might want to look at putting that on the same server as the Citrix license server.
1
I cant really tell from your question if you're asking if you can host the TS license server in the "Citrix Control" server or not, but your best bet with any licensing questions is to go back to the manufacturer and check with them on the specifics of your configuration. You're loading up what I think is the latest XenApp so you s hould have some support ...
1
You can install Terminal Server Licensing on the Citrix License Server without problems. We have run that way for a while.
The best way to point the rest of your domain to the TS License Server is to use GPO...
http://technet.microsoft.com/en-us/library/cc737644(WS.10).aspx#BKMK_gp
1
I would suggest trying out Terminal Services License Server Viewer.
Terminal Services License Server Viewer (LSView) is a graphical tool that displays information useful for monitoring and logging the status of all available Terminal Services license servers in the current domain and current site of the computer.
Overview
Terminal Services License Server ...
1
There is no special version of Windows Server 2003 for Terminal Services-- it's a single product. (Obviously, the "Edition" that you need-- Standard, Enterprise, etc, would be dictated by your requirements.)
The OS itself will upgrade in-place without issue. I'd be most concerned about the Terminal Services Licensing service, which you might be running on ...
1
If you have 10 users who insist on software X, and you don't want to allow them access to a terminal server to reduce the number of licenses requires, your only real alternative is to just purchase the licenses and install it on their workstation.
If you don't run it from a central location your alternative is to use things like the app virtualization to ...
Only top voted, non community-wiki answers of a minimum length are eligible
