Looking for relevant Exchange Whitepapers? Visit the SearchExchange.com Research Library.
carrybagman | Sep 17 2006 2:12PM GMT
Once you have installed your server in non-TS mode (i.e. Anti-Virus, other apps) you’ll be forced to re-install 3rd party apps. Consider, if budget allows, another server or Virtual Server and keep TS away from your normal server
ursulus | Sep 17 2006 4:09PM GMT
Hang on… unless something has changed in recent times.. Terminal Server beyond the 3 administrative logins is expressly disabled in SBS2003 installations.. Well, that’s what I thought.. please correct me if I’m wrong as I have had to spec some installations quite differently because I assumed Terminal Server was not available.
Ursulus
carrybagman | Sep 18 2006 5:39AM GMT
I didn’t know that! If you could forward any URL that states this, I would be very interested.
HHMagicman | Sep 18 2006 5:53AM GMT
This should answer its a MS blog
<a href="http://www.microsoft.com/technet/community/chats/trans/sbs/sbs0421.mspx" rel="nofollow">http://www.microsoft.com/technet/community/chats/trans/sbs/sbs0421.mspx</a>
Ive installed a number of SBS systems recently, and yes for Terminal Services you definetely need to add in a new server to the domain with windows 2003 server on and make this a TS server
cadsystems | Sep 18 2006 4:05PM GMT
If you are running SBS2003 you can put in a Windows 2000 server as a terminal server, and you only have to pay for a Windows 2000 server license; user CALS and TS CALS are legally provided by the SBS2003 server (if you use a Windows 2003 server as the TS you have to pay for TS CALS which are really expensive). We did this to keep costs down for our TS solution.
<a href="http://go.microsoft.com/fwlink/?LinkId=49921" rel="nofollow">http://go.microsoft.com/fwlink/?LinkId=49921</a>