![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
RE: Licences
For terminal services, you'll need a terminal services user or device CAL for
each user or device connecting to the server. You will also need a Windows CAL for each user connecting to the TS. For SQL Server, you will need a SQL CAL for each user or device connecting to the SQL Server. A processor licence might be appropriate if you have over a certain number of connections (see links) or running SQL Server as a backend database for your website - i.e. you might not know how many connections you will have. See the links below for a 'clearer' picture from Microsoft. SQL Server Licensing: http://www.microsoft.com/sql/howtobuy/licensing.mspx Terminal Server Licensing: http://www.microsoft.com/windowsserv...ng/ts2003.mspx Unfortunately, you cannot get away with just having 1 licence per server!!! "Glenn Clark" wrote: > Hi all > > If I have a server used for terminal services login and a separate server > running sql server. As well as the ts licences do I need windows cals for > both servers of just 1 licence for each user? > > Many thanks > > Glenn > > > |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|