IT Employment
Hello,
I was wondering if you could or it would be wise to put exchange on the primary domain controller. We initially were going to get a separate server, but due to budget contraints, have to re-evalutate the situation. Any ideas?
by luyasu
PDCs are for authentication of networking resources on the LAN whether its topology; so web server services to support additonal network resources so as to group those resources to sustain a high ratio of business/technical balance by centralizing storage for backup, security (secure all possible accessible points), and extremely important: administration.
Exchange is best on BDCs.
TSP
by timwalsh
While it is always desirable to place different functions on separate servers, it isn't always economically feasible (as is apparently your case).
There are several factors that should be considered:
What else is the PDC being used for?
Howmany users do you support?
How much do these users rely on email?
What is the daily volume of email?
What is the configuration of the server?
Look at from the standpoint of how Microsoft Small Business Server (which bundles not only Windows Server, but also Exchange, SQL and Proxy (or ISA depending on the version)) works on a single machine. All these components MUST be installed on the same computer and will support up to 50 users.
The bottom line here is that unless you are trying to support a LARGE number of users (several hundred or more), or have a marginal server (only exceeds the recommended minimum hardware by a slim margin), you probably won't experience any performance hits large enought to be noticed by placingExchange on your PDC.
by areets
Issues - continues and continues but never get resolved!
While it is always desirable to place different functions on separate servers, it isn't always economically feasible (as is apparently your case).
Economics? Define the goal and achievewith the budget by using an advanced road mapping technique. How many companies? suppliers and vendors budgets are based on assessment of the TARGET EFFECT before signing the contract? I am sorry but business can continue with balance but cash flow remains.
to be continued.....
by areets
There are several factors that should be considered:
What else is the PDC being used for?
THE PDC?s PURPOSE ON THE NETWORK IS FOR ATHENTICATTION amongst other light services.
This is a crucial point for network resources? and potential networking application authentication, hence why not centralize your needed resources.
How many users do you support?
It is not machine quantity, it is the quality, and you assess the performance; expandability and stability requirements.
by areets
How much do these users rely on email? What is the daily volume of email?
The great illusion! Why are you still asking the same questions; technology can allow us to send MAN TO THE MOON, and we cannot decide in 2003 e-mail quantity by FORMULA
BY TOPLOGY:
TIME+SPEED+QUANTIY=REQUIRED PERFORMANCE
Now multiple by users.
by areets
What is the configuration of the server?
Assess, please.
And for this all Exchange stuff! PLEASE STOP REFERING TO IT AS AN EMAIL SERVER.
EXCHANGE IS A COLLABORATION SERVER
ALL WHO SUPPORT EXCHANGE ENVIRONMENTS PLEASE STAND UP.
I SAY THAT COMPANIES ONLY USE A SMALL PERCENTAGE OF THE BUSINESS POTENTIAL THAN IT IS PRESENTLY DOING. I AM NOT CONTESTING ITS SUPERIORITY OVER SIMILAR PRODUCTS.
RULE OF THUMP:
DO NOT COMPLICATE THINGS
by lgarvin
I absolutely agree. I've been supporting Exchange servers in small and medium scale businesses for five years. I rarely see one of them being used for more than an enhanced email server. It's terribly disappointing, I must say.
Having said that... in most of those organizations Exchange was running on a lone PDC and easily supported 25 or more users with light email loads as just an email server.
The picture will be quite different with Exchange Server 2000 on Windows 2000 Server, or eventhe forthcoming Itanium on Windows Server 2003.
The questions that several responders have asked previously all need to be considered. The short answer is there is insufficient information to answer the original question.
If I were approached with that simple question by a client, I would immediately pursue about a 2-3 hour interview to discover everything about what the current server is doing and how the email services will be used. It may be that Exchange isn't even the right solution for this company; for example, a simple SMTP/POP/IMAP server on a Linux or *BSD box can easily meet the needs of a small organization for email only.
by areets
Small Business Server packs are indeed interesting for all companies:
With the business output in terms of infrastructure resources generated!
Measuring tools can allow us to achieve and use thresh-holds that facilitate both the technology for the business and its technical support in its entirety. But allow me to not enlarge the scope at this moment.
Business Technology requirements
mid-point S.M.A.R.T
Support Technology requirements
=
Business Technical Operational Support
TSP
by amadeus hack
by lgarvin
I can share two extremes of how Exchange function on specific hardware.
Network #1 currently consists of a single NT Server and Exchange v5.5 running on a Pentium 200 with 64MB RAM. It supports about a dozen mailboxes, many of which have several hundred messages in the IS. Two of the boxes have over 1,000 messages. The network runs on a 10MBit/sec hub, supports two clients (one Win2K and one XP Pro), and associated special purpose BSD and OS/2 systems. Performance in this environment has never been noted as an issue.
Network #2. Approx 200 PC users across 10 sites connected by Frame Relay ranging from 128K to full T-1 port sizes. Corporate network has about 35 users, mostly on 10MBit/sec connections. The Exchange server sits on a non-DC Pentium III/550 Compaq Workstation with mirrored IDE drives. The system more than adequately supports those 200+ users, including considerations for network latency to the slower Frame Relay connected users.
by iplaspalmas
Putting Enxchange 2000 on a W2K Domain Controller is fine. (Look at SBS 2000, it has domain controller, SQL and Exchange and ISA all in one package)
Just ensure that you have powerful enough hardware for the loads you want to handle. You'll need more memory, more processing power and more disk space to hold the Exchange database and an enlarged IIS metebase, plus all the user emails.
And make sure you stay on top of managing it. Remember, apply service packs and hotfixes as soon as possible (and apply them properly) and keep up with defragmentating.
Regards,
Isaac
isaacp@sympatico.ca
This discussion is closed to new replies.
Sort by Trending