Best Practices for Maintenance of Exchange Server 2003

I work for a small firm of about 60 - 100 users. Lately we have been experiencing latency with our networked resources. We currently have one server(Dell PowerEdge 2900) running just about everything and we would like to implement more services. Currently the roles installed are exchange server 2003, file server, print server, database server (for various networked based applications), and in the near future an WSUS server.What are the best practices for managing exchange 2003 with all of these services installed on the same machine? Would it be wise to purchase more hardware to separate the services?Or is the load a bit much to handle on a single box?

Thanks,

tg
techguy57Asked:
Who is Participating?
 
B HCommented:
as it stands, how is your processor usage at idle, hard drive space, and memory usage?

adding wsus can easily add 75GB of used space to the drives, shouldn't add much more memory/processor usage after it's configured
0
 
Andres PeralesCommented:
I would separate you services if you possibly can to other hardware.  Does this machine have more than one CPU?  Is it maxed out on RAM?
But again best bet would be to separate your services especially Exchange and Database roles.
0
 
techguy57Author Commented:
It has single XEON processor, about 2TB of HDD space w/700GB free, and about 5GB of memory but not maxed out. If the services are separated, then what type of maintenance should be done on the exchange box. I am a newbie to this arena.
0
 
Andres PeralesCommented:
Typical maint. for exchange, patches, reboots, occasional exchange database defragmentation.
0
 
techguy57Author Commented:
Is there anywhere online that has some type of documentation on how to perform these tasks?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.