Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Why shouldn't WINS be on the same B
- Thread starter mwillia9
- Start date
Exchange is a very intensive app. You should run it on a BDC to avoid processing logons and have no other services running. Where possible, WINS, DNS, DHCP, file and print and so on should be run on other servers.
I once managed to run everything on the one server with 128MB RAM, but people complained about log on times, email response and so on.
Bottom line is the recommendation to keep Exchange separate.
I once managed to run everything on the one server with 128MB RAM, but people complained about log on times, email response and so on.
Bottom line is the recommendation to keep Exchange separate.
I have one box.. a Winterm box running exchange, WINS, DNS, BackupExec and a couple terminal sessions. No more then 5 users. Would I recommend doing this at a customers site?.. not at ANY time unless you are brave and have time to burn. This happens to be my own office server so I can handle the risk.
I tell all my customers that WINS/DNS/DHCP should be on their own box, tucked out of sight and ignored. No file shres, no print services, no login.. nothing at all unless required. THis has kept them stable and functioning pretty much the way they should function. Quietly and in the background.
Mike S
I tell all my customers that WINS/DNS/DHCP should be on their own box, tucked out of sight and ignored. No file shres, no print services, no login.. nothing at all unless required. THis has kept them stable and functioning pretty much the way they should function. Quietly and in the background.
Mike S
- Status
Similar threads
- Locked
- Question
- Locked
- Helpful tip
- Locked
- Question
- Locked
- Question