cstephen100
asked on
Windows 2003 network setup with mdaemon mail server.
Hi All,
I am currently thinking about upgrading my network. I am installing a terminal server and I also want ot a mail server, the new server is windwos server 2003.
I believe you cant setup up ms exchange on a termainl server. I presently have a windows 2000 server without excahnge and a windwos 2000 pro pc that works as file server. I dont fancy getting a new server just for exchange so what I am thinking of doing is as follows.
Could I use the new terminal server as an the active directory server that contains all the user accounts for the network.
I was going to install MDAEMON mail software on the old windows 2000 server and use it as the mail server.
Would this work fine or could I run into problems with having users on differnet server.
Could I possibly setup MDAEMON on the new terminal server, The new terminal server would have about 20 terminal clients using it.
Hope someone can advise me on the best route to take.
Thanks
Stephen
ASKER
Sounds Good,
Would the old windows 2000 server be ok for being a domain controller,
Would the windows 200 sevrer contain the user accounts for the terminal server, i.e want different desktops accounts for each terminal client. Or would ther termianl server do this.
Also, is it ok to mix Windows server 2003 and windows server 2000.
Regards
Stephen
Would the old windows 2000 server be ok for being a domain controller,
Would the windows 200 sevrer contain the user accounts for the terminal server, i.e want different desktops accounts for each terminal client. Or would ther termianl server do this.
Also, is it ok to mix Windows server 2003 and windows server 2000.
Regards
Stephen
A machine that runs Windows 2000 can probably run Windows 2003, and being a domain controller will be fine.
Don't get user accounts and desktops mixed up. The user accounts live on the domain. Desktops etc live on the server. Therefore you could have all the accounts in the domain, and then when the users log in to the terminal server they will get their own desktop - whatever you have set the for the user accounts.
Mixing Windows 2003 and 2000 is fine. However remember that if you are running Windows 2003 terminal services, then the licensing needs to be on a Windows 2003 server.
Simon.
Don't get user accounts and desktops mixed up. The user accounts live on the domain. Desktops etc live on the server. Therefore you could have all the accounts in the domain, and then when the users log in to the terminal server they will get their own desktop - whatever you have set the for the user accounts.
Mixing Windows 2003 and 2000 is fine. However remember that if you are running Windows 2003 terminal services, then the licensing needs to be on a Windows 2003 server.
Simon.
ASKER
Hi Sembee,
Thanks for replys.
So that I have got you i will explain the way I am to set it up and also my terminal clients query.
1: Terminal Clients Query:
I assumed you needed a differnet user account for each termianl client so that they will have there own custom desktop.
Or is it possible configure this differnetly.
2: network Setup
I will use old windows 200 server as domain controller and also install msdaemon on it so it will act as mail server also.
The users will be setup on this server, but I will be using ther new server as terminal server, so I am a bit confused
what you ment by having licensing on windows 2003 serve i.e new server. Its just do I need a user for each client so they have custom desktop.
Thanks again
Stephen
Thanks for replys.
So that I have got you i will explain the way I am to set it up and also my terminal clients query.
1: Terminal Clients Query:
I assumed you needed a differnet user account for each termianl client so that they will have there own custom desktop.
Or is it possible configure this differnetly.
2: network Setup
I will use old windows 200 server as domain controller and also install msdaemon on it so it will act as mail server also.
The users will be setup on this server, but I will be using ther new server as terminal server, so I am a bit confused
what you ment by having licensing on windows 2003 serve i.e new server. Its just do I need a user for each client so they have custom desktop.
Thanks again
Stephen
Each user needs their own user account, how else are you going to give each user their own desktop. Plus having multiple users logged in with the same user account would cause a lot of problems for the server.
Windows 2003 Terminal Services requires a licensing server. You cannot have a TS server without one.
Furthermore, unlike Windows 2000 Terminal Services, you don't get an TS CALs with the operating system.
Therefore if you want to use Windows 2003 Terminal Services, then you will have to go and purchase some Windows 2003 TS CALs.
The licensing server is best placed on a domain controller, but the domain controller needs to be Windows 2003 to accept the installation of the Windows 2003 TS licensing component.
Simon.
Windows 2003 Terminal Services requires a licensing server. You cannot have a TS server without one.
Furthermore, unlike Windows 2000 Terminal Services, you don't get an TS CALs with the operating system.
Therefore if you want to use Windows 2003 Terminal Services, then you will have to go and purchase some Windows 2003 TS CALs.
The licensing server is best placed on a domain controller, but the domain controller needs to be Windows 2003 to accept the installation of the Windows 2003 TS licensing component.
Simon.
ASKER
Hi Simon,
So it looks like I will have to upgrade the windows 2000 server to 2003 as it will be the domain controller.
I have priced the new server with 25 terminal cals so that should be ok, except its windwos 2003 and domain server is 2000.
Would you highly advise against using the terminal server as domain controller because of security issues also.
Thanks for help.
Regards
Stephen
A terminal server should not be a domain controller. There will be too much on the server that the users shouldn't have access to - the active directory and network tools for example. Users are a curious bunch and may go looking around to see what there is. While you could lock it down, that may hinder the operation of the domain controller functionality.
Simon.
Simon.
ASKER
Hi Sembee,
Sorry for delay in replying as was away and also for dragging question out a bit.
I have took your advice and I am ready to order the following, hopefully the setup will be correct, its as follows.
Server 1: Domain controller, 50 client users and 25 Terminal Clients.
I have 25 terminal clients approx, I have also some local users so I need them to have local accounts, thats why I have 50 users, hope this is correct.
Server 2: Terminal server,
Should the terminal server be as powerfull (i.e high spec) as server 1 as it is not the domain controller and the terminal licenses are setup on server 2. Termial server will act as desktop for all clients to run system program,
Hope im going down correct route.
Regards
Stephen.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Simon.
That sounds perfect, Im clear now.
Thanks for all the help.
Stephen
That sounds perfect, Im clear now.
Thanks for all the help.
Stephen
You could put mail and domain controller on to the old server. That would work fine. I have done something similar a number of times.
Another option would be an Small Business Server. Yes it is another machine, but it would give you Exchange, domain controller etc. Microsoft have made the price of SBS to be very good, so that manufacturers like Dell, IBM, HP and the white box servers can bundle it with a low end machine.
Simon.