Using a DC as a File Server?

[scottew]

I have a new client that I am setting up a small network with about 10 users to begin. Who knows how fast they will grow.

They had already purchased the following servers prior to my arrival:

2 Dell PowerEdge 2950
Dual Quad Core Xeon Processors
4 GB Ram
6 x 73GB Hard Drives (Raid 5)

Server A - This will be their DC along with DNS & DHCP.

Server B - This will host a custom application which uses SQL 2005. In speaking with the Tech Support from this company, there will be some FTP involved with this application as well.

My question is which one of these servers should I use as their File Server?

The company that they purchased the application from does not want anything else on the server and I prefer not to use my DC as a File Server.

So which server should I use for the file server?

Any comments would be appreciated.

Thank you,
Scott

P.S. The good news is that I convinced them to go with a Hosted Exchange server rather than throwing Exchange 2007 on one of these as well.

 

[technome]

Most of my clients are under 100 users.. on most I have DCs, even FSMOs running SQL, DNS, DHCP and are used as file servers. As long as you apply the correct security and you have a backup unit, there is nothing wrong with using DCs as general servers on small networks. With 10 users AD will not place any load on the other resident programs and in the reverse. Do not let ANYONE touch the server setup or run the server as a wks or it will be useless in a short time. Would be a sin to use a quad core 2950 just for AD services; if this was a large network, it would be a diffent story.

I just bowed out of a network where the owner allows TS connections to the server by users, after repeated warnings against TS use and other practices, a hacker got in due to multiple key logger downloads..I cleaned up the mess and told the owner to get someone else to manage the nightmare...I am not into needless, owner induced, crisis management.

"I convinced them to go with a Hosted Exchange server rather than throwing Exchange 2007 on one of these as well."
Excellent move. I have inherited a few very small networks which had Exchange installed, really foolish move... much more cost effective to have Exchange hosted if the network only has a few users.


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[Dublin73]

Use your DC as the file sharing server, it's no problem at all. If you were dealing with a larger security conscious organization you wouldn't do it, but in your case it's fine.

Also, regarding DHCP, you typically wouldn't put this on a DC, but again, with a small business it's fine.

...and technome, I'm reading your post, nodding my head and laughing because I've been there before myself, where the higher ups in the small business decided that they were IT gurus and wreaked all kinds of havoc on the servers (which of course caused all kinds of damage which I had to fix)!!!!!

 

[LWComputingMVP]

So Windows Server has already been purchased? If not, I'd strongly suggest SBS - that really makes the most sense for a small business... and 1 core per 2.5 users is insane... performance should NOT be an issue. Philosophically, each server should have only ONE function... but economically, in a small environment, this is a HUGE, HUGE waste. It's very common for small environments to have DCs also act as file servers. Though it's far more common to have small environments that run SBS that act as DCs, file servers, and exchange servers.

-Lee

Those who ask why, learn

http://www.lwcomputing.com

 

[technome]

Just my opinion, due to the fact that most SBS setups I run into are setup incorrectly.
For ten users, personally I would not use SBS. Most of the add-on will not be used, though all are generally installed, absorbing resources... having Exchange running on the server for a few mailboxes is not efficient, no less if the server acts up, no email, no website etc. If it needs rebuilding, owners is on your back due to a few email accounts.

"decided that they were IT gurus and wreaked all kinds of havoc on the servers (which of course caused all kinds of damage which I had to fix)!!!!!"
Owners in general can be the worst network threat, some well beyond viruses and malware threats.
My favorite..15 years ago, a client refuses to backup. I keep telling him about the dangers. He got tired of hearing it, gets another tech... a year later I talk to the "new" tech...states the server disk died 2 months after I left, 3 accountants spent 6 solid months re-inputing data, an equivalent of a 6x10x8 foot room of paper (stiffed me on the last bill, justice prevails).


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[scottew]

Thanks to all of you for your responses. I had originally suggested SBS for this client, but they are hoping to grow quickly and decided to just go with Server 2003 Standard.

I ended up using the DC as the file server with the proper security. I always create a Security Group in AD with the proper permissions.

Thanks again,
Scott