Are you going to use NLB with them? If so and you are using Unicast mode, they won't be able to talk to each other directly and one won't get the licenses. Other thing to keep in mind is it's a royal pain to move your TS license server (calling the clearinghouse can take a while), so try to put it somewhere on a newer server that isn't going to be upgraded/migrated any time soon.
From: David Lum [mailto:david....@nwea.org] Sent: Friday, December 04, 2009 8:37 AM To: NT System Admin Issues Subject: RE: Terminal Server CAL's My DC's are 2003, my test environment is on 2003 but I could use 2008 Server for the production TS systems. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 From: Webster [mailto:carlwebs...@gmail.com] Sent: Friday, December 04, 2009 8:35 AM To: NT System Admin Issues Subject: RE: Terminal Server CAL's 2003 or 2008? 2003 put on DC OR for 2003 or 2008 Put on any server and use Group Policy to set the license server location. Webster From: David Lum [mailto:david....@nwea.org] Subject: Terminal Server CAL's I'm a victim of my own success, we had an issue here that I solved by creating a Terminal Server machine and loading apps on the server. Performance is great and I've been told to roll it out. Cool! Uh, ok now I need to plan it out :). I will have two Terminal Servers and we have 50 CAL's, does it make sense just to make one of these the Terminal Services License server as well? On my development TS servers running the Terminal Server Licensing tool it's pointing at my DC, for production I should just make one of the two TS server the TS license server right? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
