Windows server 2008 TS licensing

Associate
Joined
12 Aug 2005
Posts
1,025
Location
Team 10
I've just installed windows server 2008 on a virtual machine to have a play around with it and so far, everything is as complicated as I expect it to be for someone who's never looked at a server before. However, there's something I don't quite understand.

Terminal services. At the moment, for my fileserver, I'm using XP Pro which allows 1 remote desktop connection at a time. Any more and it just kicks the other user. As I understand it, I can have multiple logins on my 2008 server which, after much faffing around and changing group policy settings, managed to get working on a non-admin account.

At the moment, I'm running the server with the 120 day grace period for the CAL(s). I don't understand how it works though. After the 120 days, can I only have 1 user logged in at once? Or is it something that I don't even need to be looking at? Do you have to pay for the user licenses?

Any help would be appreciated.


*mods*
I posted this in the windows software section but I think I'll get a better response from here. Delete if necessary.
 
You shouldnt have had to faff about with group policy to get TS working, so dont know what you've done.

After the 120 days expires, the server will still allow admin connections (ie one at a time) unless you purchase the CALs
 
You do have to set the Local Security Policy up for remote logins if not using the builtin groups.

Either use the builtin "Remote Desktop User" group on the users AD account or create a new Security Group, something like "TS User" add your users and add this account to the Terminal Server Security Policy.

Admin Tools> Local Security Policy > Local policies > User Rights Assignment > Allow Logon Through TS.
 
What are you actually trying to achieve and why? If you want a terminal server, you need to pay for it...
 
What are you actually trying to achieve and why? If you want a terminal server, you need to pay for it...

Given his OP I think he's after just mucking about and testing it? A "cool to have" type feature?
 
Unfortunately they give you 120 days to muck about with it - after that you gotta wedge up or reinstall :)
 
@burns: Yea it was a DC, removed the AD now so it's just a stand alone server as I decided that there wasn't any point me messing around with domains.

@DRZ: Pretty much nail on the head there. I've got access to the MSDNAA so I have 90% of the microsoft products available for free. Downloaded them all of course so I was giving a few a go.

All I'm wanting to do was to have the ability for more than 1 person to login to my server at once. I knew I could do this with windows server so that's where I went first but if I'm going to have to pay for it, I might as well just do the XP hack.
 
@burns: Yea it was a DC, removed the AD now so it's just a stand alone server as I decided that there wasn't any point me messing around with domains.

@DRZ: Pretty much nail on the head there. I've got access to the MSDNAA so I have 90% of the microsoft products available for free. Downloaded them all of course so I was giving a few a go.

All I'm wanting to do was to have the ability for more than 1 person to login to my server at once. I knew I could do this with windows server so that's where I went first but if I'm going to have to pay for it, I might as well just do the XP hack.

Do you know how many CALs come with the MSDNAA licence? Should be documented somewhere. You might find you have 5, which would mean you could use it instead of hacking XP.
 
I've no idea how many CALs I get with it but I came up with a better idea. Running an XP VM on my existing XP host and that gets me exactly what I was wanting to achieve :)
 
Back
Top Bottom