Exchange Server - Exchange 2007 + Quad-core 64-bit processors
Asked By John Aldrich
16-Oct-07 12:56 PM
We're looking to get an Exchange server early next year and the folks
who spec-ed the server for us spec-ed a dual-core Xeon instead of a
Quad-core. When I asked why, they said that "Quad Cores hav been
sketchy with x64 Ex07." I spoke with an expert at Dell, who said that
that's NOT true.
I'm wondering if any of the early adopters here have seen any issues
with Quad-core Xeons and X64 Exchange 07? Please feel free to CC any
replies to my personal email address. The address is valid.
PSTs
(1)
X64
(1)
Cores
(1)
Quad
(1)
Xeon
(1)
Processors
(1)
Footprint
(1)
Smackdown
(1)
Oliver Moazzezi [MVP] replied...
There are no known issues.
Lay the smackdown with 'Planning Processor Configurations'
'http://technet.microsoft.com/en-us/library/aa998874.aspx' as you may find
you will actually need quad core procs if your server architecture doesn't
provide enough footprint for CPU sockets.
Oliver
John Aldrich replied...
Thanks for the info. What about stability? Our consultant has stated that
Ex '07 is "flaky" and that 03 is much more stable. Do you buy that or is
that just FUD from a consultant that has not actually worked much with 07?
Oliver Moazzezi [MVP] replied...
Exchange 2007 is not 'flaky'. In regards to scope and capacity it is
actually far more resilient than Exchange 2003.
It however takes some getting used too. Not all configuration changes are in
the GUI, you will find you will have to get used to Powershell. There are
what some people consider backwards steps where contact, group and mail
enabled users are now added in the EMC or Shell, rather than through ADUC.
Whether you need E2K7 is another question, are you looking at it because of
the new features E2K3 cannot provide?
Oliver
Sabo, Eric replied...
We just implement Exchange 2007 on Quad processor with ISCSI storage, we
have been very pleased with it so far. Plus Exchange 2007 Service Pack 1
is right around the corner. My my two cents go with Exchange 2007.
Ed Crowley [MVP] replied...
What a sweet licensing deal!
--
Ed Crowley
MVP - Exchange
Combined Hub / CAS cores in Exchange 2007 Exchange Server For Exchange 2007 the recommendation for separate hub and cas servers is 4 processor cores each. When combining the hub and roles on one server should we be looking at 8 cores along with 8GB ram ? The current front-end for Exchange 2003 is 4 cores and %CPU is low on average, supporting up to 3000 users. TIA gwp Exchange Setup a lot trickier. My personal take is that MS are not saying you need 4 cores + 4 cores = 8 for the CAS / HT consolidated role, and your real-world examination with your existing sizing for a client with 3000 users right now and I will spec 4 CPU cores with 8 GB RAM for dual CAS / HT server. Thanks for the input - that is of sizing I am looking at. Interestingly when getting quotes recently it turned out that quad cores are as cheap (or cheaper!) as dual cores. Assuming there is no disadvantage to
Exchange virtualized on 12 cores? Exchange Server The following website, http: / / technet.microsoft.com / en-us / library / ee832795.aspx Says, towards the bottom of the page "Root server processor cores (root servers with 12 x processor cores do not fit this model)". So can I use a server with dual 6 core 3 servers total)? The dual 6 core machine is the same price as a dual quad core machine. Thanks, Exchange Design Discussions Processors (1) Cores (1) Quad (1) Sorry, nevermind, the processors I was looking are quad core and not 6 core. Thanks, keywords: Exchange, virtualized, on, 12 cores? description: The following website, technet.microsoft.com / en-us / library / ee832795.aspx Says, towards the
all! I have a problem migrating mailboxes from a Exchange Server 2003 Standard SP2 into PSTs. . The error code is the one in the subject. What I have already done: - Downloaded have copied in the ExMerge folder the correct one. - I have tried to create some PSTs with mailmig.exe and it works!! I cannot figure out this issue!! I hope you have some good suggest for me :) . . I have read that to create PSTs ExMerge is a better choice than mailmig. . . Moreover mailmig creates password protected PSTs and I have not found the hotfix to create PSTs without passwords. . . Thank you in advance! Bye PS: sorry for my english but I am Exchange Admin Discussions CreateEMSPSTProfile (1) Exchange Server 2003 (1) Outlook (1) CopyMailBoxData (1) EDKRoutines (1) PSTs (1) MapiInit (1) ExMerge (1) Sorry the error is "CMapiSession::CreateEMSPSTProfile" not the one in 15:35:35] Copying data from mailbox 'Administrator' ('ADMINISTRATOR') on Server 'MAILSERVER' to file 'D: \ PSTS \ ADMINISTRATOR.PST'. [15:35:35] DN of object is ' / O = <NomeOrganizzazione> / OU = PRIMO GRUPPO AMMINISTRATIVO all! I have a problem migrating mailboxes from a Exchange Server 2003 Standard SP2 into PSTs. . The error code is the one in the subject. What I hav
Citrix and Outlook PSTs Exchange Server We are going to put alot of users on thin clients and connect to Citrix. What is the best way to handle their PSTs. Since MS does not recommend network share PSTs. . what have others done so we do not cause disruptions? Is the only solution to all of the data on the exchange servers? thx. steve Exchange Admin Discussions Outlook (1) PSTs (1) Mailboxes (1) CCNA (1) MCSE (1) Move their PST items back into their mailboxes files, period. Disable autoarchive in all desktop users' Outlook as well. keywords: Citrix, and, Outlook, PSTs description: We are going to put alot of users on thin clients and connect to Citrix. What is the best way to handle their PSTs. Since MS does not recommend network sh
I believe could be down to the paged / nonpaged pool issues that are mentioned whenever PSTs on file servers is discussed. Of course it very hard to be sure because nothing 1) Enforcement (1) Attorneys (1) Spindles (1) Registry (1) Pagepool (1) If mail in the PSTs are kept only for convenience, then why are you trying to find a way to files, you're just digging a deeper hole for yourself. If you give the users PSTs, they will keep using them, and demand more and more storage space for them. It situation. You are not doing yourself or your organization any good by continuing to use PSTs. There is no easy way to manage them. Increasing your Exchange capacity or getting an not the answer you wanted to see, but the reality is that continued use of PSTs doesn't help anyone. - - Regards, Mel K, MCSA: M if they are not keeping them