windows 2003 sbs concerns
Posted on 2004-10-21
My company's website and email are hosted by a third party web server. We also have two in-house servers. One, a Windows 2000 machine, is mainly a file server - it's used for employee access to several programs and files through the network. The other one is a WinXP Pro machine, and is set up as with IIS as a web and ftp server for web utilities, reports, and documents, which are mainly accessed by employees - both in-office, and at home or on the road.
I would like to consolidate all these functions (web, file, program, ftp, email) into an in-house, new Windows 2003 SB server machine (which I have not purchased yet).
Here is a breakdown of functions I need for a new server, and questions/concerns that I have:
* Function as a web server - anyone should be able to access the company website from the internet.
* Function as an email server - be able to set up company email accounts using company domain (e.x. email@example.com) - employees will be able to keep their existing company email addresses; they will just be set up on the new server instead of the third party server as of now.
* Function as a file server - Employees will be able to connect (e.x. map a network drive) to the new server and be linked to several company-essential applications and files.
* Function as a terminal server - select employees will be able to login to the server remotely from home or on the road like they are doing now to the win2000 machine.
Now, how hard would it be to setup DNS on the new server (for web and email use), and switch it over from the third party server we are currently using?
Also, what's the deal with CALs for Windows 2003 Server? I'm assuming only the office machines will need them. How much time would it take to setup a client (WinXP or 2000) machine to be able to connect and communicate with the 2003 server through the office LAN?
Any additional information that you think is important would be appreciated.