I'm in process of deploying a brand new Exchange 2007 deployment though we have an existing Exchange 2007.This is what we haveSingle Server Exchange 2007 SP1 on a Windows Server 2003 64-bit Server hosting 125 mailboxed including DG. The Server RAM is 6 GB. We are facing problem and and it is not configured the way we want it. It host only one domain.New DeploymentExchange 2007 SP1 with other latest updates on Windows Server 2008 R2. Existing AD is Windows Server 2003 SP2300 MailboxesMultiple Domains to be hostedMailobx size limite to general users is 1 GB and max is 2 GBMailobx to the Management is 20 GB-40 GBWe have intensive use of distribution groupWe have intensive use of Public foldersThis Server must be up and running 24x7 99.99% uptime is must.We want a single server solution with HA.We don't want an Edge Server as we will use 3rd part anti-spamChallengesIntegration in the existing environment. AD has to be upgraded to 2008 R2?In order to setup a new server how to move the mailboxes from the existing server. Or shall we add this server to the existing environment. Make sure that we will upgrade our all windows server to 2008 R2 in the near future.thanks.

There shouldn't be any need to upgrade your domain.Single server combined with a 24/7 99.99 uptime SLA doesn't seem realistic. Virtually any failure of a hardware component that isn't fault tolerant and hot-swappable is going to cause you to not meet that SLA. That's less than an hour a year of downtime. Maintenance reboots for service pack and security patch installations come exceed that in a year.

Hi, Exchange 2007 is not yet supported on Windows 2008 R2 - most probably it will be starting with the release of Exchange 2007 SP3 I would add the new server to the existing domain and move the mailboxes on the new server. There is no problem in having multiple domains hosted on the same Exchange organization. HA is not possible with a single Exchange 2007 server, but why don't you think about transitioning to Exchange 2010? Reusing the old Exchange server will create the possibility to implement a DAG solution that will increase uptime. Your hardware resources will also be better used and you'll benefit from a lot of improvements Exchange 2010 is coming with. Think about that. br, Sorin

I'm in process of deploying a brand new Exchange 2007 deployment though we have an existing Exchange 2007.300 MailboxesMailobx size limite to general users is 1 GB and max is 2 GBMailobx to the Management is 20 GB-40 GBWe have intensive use of Public foldersThis Server must be up and running 24x7 99.99% uptime is must.We want a single server solution with HA. A year has 525,600 minutes, to meet a 99.99% uptime, the system could only be down 52 minutes (leaps add some more minutes).You cannot achieve this with a single server. Perhaps you could with CCR and to Hub/CAS servers with redundant switches, routers etc. Good pro-active monitoring. Highly skilled Exchange administrators. Data center staffed with people 24/7 ... In this scenario we guarantee only 99.5%, and that's unplanned downtime. We have scheduled downtimes.If I got it right, Microsoft say they have months with 99.99 (webcast about Exchange 2007 storage and Universal Storage Building Blocks), and here they count in everything, such as failover times.Since you have Exchange 2007 and want to move, why not to Exchange 2010? Take a look at this design, which requires only two servers, in addition a load-balancer. Exchange 2010 does also solve a lot of issues with Exchange 2007 CCR.Two-Member DAG in Single Data center/Active Directory SiteA two-member DAG is the smallest possible DAG that can provide high availability. Two-member DAGs are best suited for organizations that require some form of high availability for mailbox services and data, but that don't require site resilience. This configuration works especially well in small office and branch office deployments because it enables redundancy for the Client Access, Mailbox, and Hub Transport server roles using only two Exchange servers. The following figure illustrates this configuration.http://technet.microsoft.com/en-us/library/dd979781.aspx MCTS: Messaging | MCSE: S+M | Small Business Specialist

thanks for the advices.A two member DAG sounds good.I can't for Exchange 2010 now becuase we have Cisco Unity and it doesn't support Exchange 2010. And we will have to wait 2011 which we can't.In a two member DAG what load balance would you suggest? I'd would go for a non-microsoft hardware load balancer. any suggesstion?I'll have both the servers with dual power supply and RAID 1 for the OS and RAID5 for the storage either on the same server or the SAN.I'll keep the transactional logs on a sepate RAID1 volume too.I'd also have separate SG for each department such as Marketing, Sales, Management etc.

Two Member DAG is supported in Exchange 2007?

Neither cluster continuous replication (CCR) nor single copy cluster (SCC) supports hosting the Hub Transport or Client Access server roles in a failover cluster. http://technet.microsoft.com/en-us/library/bb738124(EXCHG.80).aspxso i only have the option to cluster the mailobx on the 2nd server?

Two Member DAG is supported in Exchange 2007? DAG is supported only on Exchange 2010 as CCR/SCR only on Exchange 2007

Resource for NLB Network Load Balancing Technical Reference Unicast vs. Multicast Multiple network adapters Network Load Balancing - Concept and Notes If you connect NLB Nodes with a switch, the switch must be layer 2 instead of layer 3 or higher Configuring NLB on Windows 2003 for Exchange CAS Servers The resources for the Network Load Balancing on windows server 2008: NLB Deployment Guide in the Windows Server 2008 Configuring NLB on Windows 2008 for Exchange CAS Servers Known issue: Unable to connect to Windows Server 2008 NLB Virtual IP Address from hosts in different subnets when NLB is in Multicast Mode James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com