Exchange 2013 Deployment

Hi
Can any budy share me the best deployment guide of Exchange server 2013 with DAG implementation on Hyper 2012
Also the sizing of mailbox database..

Hi,
There are few documents about deployment guide of Exchange server 2013 with DAG implementation on Hyper 2012. I searched and only fond some related articles which may help you for your reference.
Exchange 2013 virtualization
http://technet.microsoft.com/en-gb/library/jj619301(v=exchg.150).aspx
Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments
http://technet.microsoft.com/en-us/library/cc794548(v=EXCHG.80).aspx
About mailbox database size, you can look at the following articles.
Ask the Perf Guy: Sizing Exchange 2013 Deployments
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
Exchange 2013 storage configuration options
http://technet.microsoft.com/en-gb/library/ee832792(v=exchg.150).aspx
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

Active Directory Sites and Exchange 2013 Deployment

I've recently took over responsibility of an Exchange 2013 Organization that is deployed as follows:
Active Directory consists of 4 Sites. AD Site A, B, C, D Exchange 2013 Enterprise resides in 2 of the 4 AD Sites as follows:
AD Site A - ExchangeServer 1 and ExchangeServer 2
AD Site B - Exchange Server 3
AD Site C - No Exchange Servers
AD Site D - No Exchange Servers
All 4 AD Sites are 4 different Physical locations/datacenters. All 3 Exchange 2013 servers are multi-role servers.
The Forest in which Exchange resides in consists of an empty Root domain, a Production (child) domain and a Test (child) domain. Exchange resides in the Production (child) domain.
Issue: AD Site A contains DC's from all 3 domains: Root Domain, Production child Domain (this is where Exchange lives) and Test child Domain. I notice that Exchange in AD Site A is using DC's from the Root Domain for it's "DefaultGlobalCatalog",
"DefaultConfigurationDomainController" and "DefaultPreferredDomainControllers" This to me does not seem to be very efficient as any Address Book queries will have to be referred to by the Root Domain DC's to the Production child domain
where Exchange lives. All of the AD User accounts and mailboxes are in the Production child domain.
In a situation such as this, would it be advisable to build 2 additional AD sites specifically for Exchange? Rather than re-IP Exchange or risk the impact of moving several other (non exchange) servers to another AD site, I would add the IP address
of the Exchange servers /32 to the new Exchange dedicated AD Sites and erect a DC in these new sites adding its IP address /32. Any thoughts on this idea? If the subnet that exchange resides on is (for example) 10.60.3.0 /16 in AD Site A, and
I build a new AD site for Exchange and add the IP address of the Exchange server such as 10.60.3.141/32 for this new Exchange AD Site boundary, I can still leave the 10.60.3.0 /16 unaffected in AD Site A, correct?
I'm looking for Microsoft's best practices in terms of laying out AD and domain controllers pertaining to Exchange server 2013.

Hi Anthouyray,
Thank you for your question.
We could use the following command to exclude domain controller which is root domain controller:
Set-ExchangeServer –Identity <exchange servername> -StaticExcludeDomainControllers <root domain controller>
Then we could restart the service of “Microsoft Exchange Active Directory Topology” to check if the issue persist.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2013 deployment design recommendations?

We are planning on upgrading from Exchange 2010 to 2013.
Currently, we have 2 Exchange servers. One server with mailbox and hub transport in our local office with users. The CAS is in a remote data center. So, whenever either server is down or being restarted, all mail stops.
We have received licenses for three Exchange 2013 servers. What is the best way to set these up so there is high availability whenever any one of the three servers is offline. Also, since we will still have the licenses for our existing two Exchange
2010 servers, will there be any benefit in keeping those in this scenario?
I have attached a diagram of our current layout and we want to revamp it.

Hi
The current setup of your environment is not Microsoft recommended solution as there is no HA set up for mailbox hub as well as CAS
My recommendation for exchange 2013
You can have CAS servers deployed one in each datacenter
Below thing can be thought for DAG Config
In order to increase the service level which is to have one site alive when the other site is down, its
better to Move the file share witness server to a server that does not belong to neither site but it needs to have reliable network communications between both sites.
So if any of two sites fails, the DAG will have a quorum and it can remain operational. The databases will
not be dismounted and service and data access will not be disrupted.
If in case if you don't have 3 sites you can follow below( again this is not best recommended HA )
Put the FSW in the primary Data Center and set the DAG to DAC mode so you can easily do a data center
switchover in case the primary fails.
http://technet.microsoft.com/en-us/library/dd351049(v=exchg.150).aspx
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Sizing a very small Exchange 2013 deployment

Hi,
I'm currently running Exchange 2007 SP3 on Windows 2003 so I'm starting the process of migrating to Exchange 2013. Our current Exchange 2007 configuration is very small with 31 users and an Exchange mailbox size of around 100 GB right now. Our current
Exchange 2007 box has a Xeon CPU with hyper-threading so I've got two CPUs and it has 6 GB of memory. I've got two Raided drives for the C and D with the Exchange 2007 software and mailbox on the D drive. The performance of this server is adequate though it's
beginning to get a little slow. We also have an SCR replica server that is virtualized.
So I'm trying to figure out what would be an appropriate new server size should be and I've looked at all the server sizing information and looked at the Microsoft provided sizing calculator workbook but even the smallest example is for a server with 1000
users which is clearly way more than what I have.
Given what I've read, I was going to go with the following hardware:
- New very fast Xeon CPU with at least 8 cores
- 16 GB of memory, possibly 24 GB
- Raided drives for the C, and D, and possibly an E drive to separate the database and log files. Probably 250 GB for the OS and 1 TB each for the data drives.
Any thoughts on this? Also if anyone has any links for sizing that are a little more specific to smaller deployments that would be very helpful.
Thanks
Nick

Nike,
CUP & Memory (24GB) should be good as you only have very few users to handle.
On the Disk, Make sure they are Fast & The recommended RAID configuration for mailbox drive is RAID-1/0
I would recommend you to take a look at the below links
Exchange 2013 system requirements
https://technet.microsoft.com/en-us/library/aa996719%28v=exchg.150%29.aspx
Exchange Server Deployment Assistant
https://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA~
Shekhar.K - Microsoft Exchange Admin.

Exchange 2013 Deployment - 150 Users

Hi!I have been asked to deploy Exchange for 150 users in a virtual environment. The organization does not want to deploy O365 for political reasons that are beyond my control.I am looking for verification that my planning is sound. I am looking to deploy in the VMWare environment. Mailbox sizes will range from 4gig to 20gig, depending on user group. I will only have 150 users. I will deploy in a failover cluster. One server will be on site, the other will be across town. We have a stable 1gb fiber connection between the two sites.My questions:Is direct access storage going to be enough? I don't see the need for the complexity of a SAN, but maybe I should use a JBOD for the mailbox databases? Seems like for such a small deployment DAS would work. I am looking at RAID10 over 4 disks with one hot spare. My network will not be getting an...
This topic first appeared in the Spiceworks Community

Hi,
As far as I know, the number of mailbox role depends on mailbox size and mailbox number. I recommend you use the Exchange 2013 Server Role Requirements Calculator to get the proper number:
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 / Outlook 2010+ Attachment size limit

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl
1. If you send a message larger than 10MB from an external client to your org, does it bounce back because its over the limit?
2. Do you see the same problem sending internally with OWA?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 to Exchange 2013 work order

Hi ,
Can anyone help me on below points.
I have installed exchange 2013 , and able to view all mail box form existing server 2010.
And move successfully some mail box from 2010 to 2013.
My question are :
Pls let me know the sequence for below reimaging task……
Move all mailbox from 2010 to 2013
Change connectors (received /Send)
NAT the IP in Router (private to Public)
Change the IP address in service provide site. ( OWA for external users)
Need to create or change MX record in internal DNS as well ?
How to change MX record for external DNS.
Note: 2010 is exchange 2010 & 2013 is exchange 2013.
Regards,
Dilip T

Hi,
Based on my experience, here are the steps of migration from Exchange 2010 to Exchange 2013:
Exchange 2013 Deployment
Digital Certificates Configurations
Configure Exchange-related virtual directories
Configure offline address book (OAB)
Move Internet mail flow from Exchange 2010 to Exchange 2013
Move Client Access from Exchange 2010 to Exchange 2013
Move mailboxes from Exchange 2010 to Exchange 2013
Move public folder data from Exchange 2010 to Exchange 2013
Decommissioning Exchange 2010
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 Site Resilience - Basic questions for setup in two seperate AD Sites, same domain

I am just getting ramped up with Exchange 2013 and have a friend that I am assisting with planning an exchange 2013 deployment for. I am not asking for step by step directions for setup, just asking for a basic overview so I can dig in to this and
assist.
Goal is to have an exchange server, one in NC and one in Switzerland in an active/passive mode for site resilience. Both servers will be multi role servers.
This is a small organization, less than 50 users and on a budget for equipment. HQ is in NC and the server will have all roles installed on a single server. Switzerland will have only one Exchange server for fail over. There is only
one domain total with two AD Sites.
My questions for clarity -
1. Can I create a Site resilient deployment with two Exchange Multi Role servers in these locations?
2. Currently, the organization does not have a Load Balancer. Will this be required?
3. They do not have a third location for a Witness Server, what issues could potentially happen if the witness sits in one of the two sites?
4. Any other basics for this design are much appreciated. I am reading a lot, however a little confused as I read through the requirements.
Thanks for your input and direction!
Wall

Hi
Please find below answers to your questions.
1. Can I create a Site resilient deployment with two Exchange Multi Role servers in these locations?
Yes
2. Currently, the organization does not have a Load Balancer. Will this be required?
No you don't need to have a load balancer. As you are setting up the infrastructure in Active / Passive mode you don't need a dedicated LB for this.
3. They do not have a third location for a Witness Server, what issues could potentially happen if the witness sits in one of the two sites?
The issue with the witness server in primary or DR site is if your witness server is not responding your DAG won't work properly (failover). If you don't have a 3rd site then you can setup a witness server in your primary site and Alternate witness server
to your DR site.
4. Any other basics for this design are much appreciated. I am reading a lot, however a little confused as I read through the requirements.
I would recommend to use Exchange sizing calculator and technet is the best resource for you :)
Kindly mark this as answer if it fulfill your requirements. :)
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Verifying correct setup for Exchange 2013 DAG

This should be a relatively simple question. I've just set up the DAG on my new Exchange 2013 deployment, it spans two servers, MB1 and MB2. Both are dual-horned, on both a replicator subnet and the LAN. I notice that the 2013 DAG is automatically
setup by default, so I want to make sure it's been setup optimally. I'm going by this article:
http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
My main concern is it looks like I should be seeing two DAG networks set up, as per this:
Enumerated DAG network settings for a multi-subnet DAG
Name
Subnets
Interfaces
MAPI access enabled
Replication enabled
MapiDagNetwork
192.168.0.0/24
192.168.1.0/24
EX1 (192.168.0.15)
EX2 (192.168.1.15)
True
True
ReplicationDagNetwork01
10.0.0.0/24
10.0.1.0/24
EX1 (10.0.0.15)
EX2 (10.0.1.15)
False
True
But I'm only seeing a MapiDagNetwork in my list of DAG Networks. Did it fail to install the ReplicationDagNetwork? If so, what's the best way to go about fixing it? Seems preferable to keep the automatic setup.
----------- Ron E Biggs Network Administrator Entertainment Studios

Hi,
I am just writing to check on the status of the problem.
Is there any update on this issue?
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2013 Split DNS, how to get WAN clients to use public Split DNS IP when inter-office link is DOWN?!

Hello,
I have an Exchange 2013 deployment and a LAN/WAN setup, we have many small remote WAN linked offices that can resolve to the Exchange Server's internal IP.
Outlook clients in remote WAN offices work fine as long as the link is UP since the Split Brain DNS for Exchange will resolve the internal clients to the internal IP of the Exchange server, Outlook connects up without issues.
However, in the event of loosing connection to our remote sites, they will no longer be able to resolve to the internal Exchange IP, but they still have a backup public internet that they can use. So should the inter-office connectivity fail we have it setup
so clients in remote offices can still browse the internet, etc.
However, their Outlook fails to connect because it has a cached DNS record for our Split Brain Exchange DNS setup and tries to resolve it to its internal IP, instead of refreshing the cache and grabbing the public IP of the Exchange server since now they
would be resolving it over the public internet.
Is there anything I can do with my existing configuration to allow the client to pick up the public IP of the Split DNS setup when our inter-office connection is down and the client is no longer able to use the internal IP they have cached for Exchange?
I guess I could lower the TTL on the DNS record to something like 1 minute so it does not cache the DNS record / IP for long? Is this the best approach?

http://public.wsu.edu/~brians/errors/lose.html
I would suggest that the best approach is to either improve the reliability of the WAN link or to configure DNS to always use the Internet path. You might want to work with your network guy, perhaps there's a way to have your gateways automatically
switch to an Internet VPN backup when the WAN link is down or something like that.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 UM on-prem-hybrid with Office365

design:
Exchange 2013 deployment on-prem including UM being used for UM for users. Domain and Exchange are set to companyA.net
companyA.com is set up in O365 for email\calendars etc.
ADFS and DirSync already configured to O365.
Available UPN's in AD are already companyA.com and companyA.net.
Plan:
Setup hybrid so some users can have mailboxes on-prem and others on O365.
Have companyA.com be the primary smtp address
Question:
1) The speech attendant part of UM on prem is a non-negotiable requirement. could the mailboxes be on O365 and still work correctly?
Other considerations:
1) Lync 2013 on-prem is deployed for all features including Enterprise voice. Presence, calendars, and voicemail from exchange required.
Need to have the MWI and calendaring\presence work.

1: It should, but first make sure you create the UM Dial Plans other UM properties in Office 365.
Do testing before the move.
I saw one of friend faced issue where as, Voice Mail notification wasn't getting delivered to user Mailbox.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 on-prem hybrid to O365

design:
Exchange 2013 deployment on-prem including UM being used for UM for users. Domain and Exchange are set to companyA.net
companyA.com is set up in O365 for email\calendars etc.
ADFS and DirSync already configured to O365.
Available UPN's in AD are already companyA.com and companyA.net.
Plan:
Setup hybrid so some users can have mailboxes on-prem and others on O365.
Have companyA.com be the primary smtp address
Questions:
1) which domain would be used as the autod when running
Set-HybridConfiguration –Domains "companyA.com, companyA.net", "autod:<>"
2) The speech attendant part of UM on prem is a non-negotiable requirement. could the mailboxes be on O365 and still work correctly?
Other considerations:
1) Lync 2013 on-prem is deployed for all features including Enterprise voice. Presence, calendars, and voicemail from exchange required.

Sorry if I am asking a lot of questions.
I am trying to setup test accounts and make sure this is working like we want it to. The production system is 30,000 accounts and I do NOT want to affect any of them until we are ready.
I have the on-prem domain of companyA.net and have setup test.companyA.net as a UPN suffix in AD domains and trusts. ADFS has been setup as well as DirSync (limited to one test OU). I have set up both the companyA.net and test.companyA.net
as additional domains and both show active in Office365 of companyA.com.
I started the hybrid wizard on-prem and got as far as the Domain and token page. Only companyA.net is listed, not test.companyA.net. Again, I ONLY want for now to have test.companyA.net working. Should I be able to proceed or how do I get test.companyA.net
on that list?
Sorry to be skittish, but any really detailed articles (step-by-step is nice) or help on how to get this setup for testing?
I am open to questions and providing what info I can if given how to find it.

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Exchange 2013 - CAS Server Multi Namespace & Site Deployment

Hello,
I am
currently designing the new Excahnge 2013 environment that I am looking to deploy by the end of the month. And I have come up with two designs on what could be deployed. The first being an active/passive design with a single namespace across two sites.
One site being the primary site and the other being the secondary DR site in a single DAG. Now this is a common design and similar setups are documented in detail online on many blogs and such.
Where my trouble is with the second design I have come up with which is an active/active model using a multi namespace across the same two sites utilizing two DAGs. The idea here being the first
site is the corporate head office which would only contain those users. While the second site would contain everyone else not based out of the head office. The goal being to cut out internal users from connecting all of the way into the primary site when they
are external to it.
Now the way in which the network is setup between the two sites. Accessing the internet from the primary site requires you to go through the secondary. So for the second design my idea would
be for external Outlook, OWA and ActiveSync connections would connect into the secondary site for it to then proxy over to the primary. Now I am used to how Excahnge 2010 did its proxying and if the ExternalUrl property was blank is knew to proxy to the other
site. Is that still the case with Excahnge 2013 or it does not care at all and I can just populate both the internal/external url properties for all of the CAS servers at the primary site?
Now assuming I do populate both the internal/external url property in Excahnge 2013 for the primary site. And for this example I am going to use mail01.domainname.com for the primary site and
mail02.domainname.com for the second. To get Outlook, OWA and ActiveSync to connect for users of the primary site externally would it be as simple as having that external internet DNS entry for mail01.domainname.com point to the same IP as mail02.domainname.com
would be? With mail02.domainname.com pointing to a externally accessible load balancer for the second site.
Now applying the above logic and assuming as long as you hit a CAS server. And it will find your mailbox for you does that mean I can could also use the same namespace in both locations for
say OWA and ActiveSync? So the idea being we want to keep using webmail.domainname.com for OWA access. So if I set that URL for both the primary and secondary site as long as I hit a CAS server in the secondary site. It will be able to connect over to the
mailbox in the primary site for OWA?
Nicholas

Hello Angela,
I need some clarification to your reply as it has left me a little more confused. Where you start by saying “all client requests will firstly access the internet-facing server”.
Are you talking about when the client is connecting in externally or when the client is internal? As this would make it seem like in my second design where only the secondary site would have internet facing CAS. That clients in the primary site internally
would connect over to the secondary site then be proxyed back to the primary.
Then for the separate namespace portion of your reply. I am assuming you mean the secondary site form my example which will have the internet-facing CAS server? If that is
the case my public DNS entry would be mail02.domain.com only but then how would the client from the primary site who use mail01.domain.com which is not on an internet facing CAS server. Then figure out they can connect in on mail02.domain.com externally from
the internet?
And when you talk about both sites using the same namespace. And using two public DNS entries pointing to the CAS servers in both datacenters. Is that not just going to do
DNS round robin? As described in this technet blog?
http://blogs.technet.com/b/exchange/archive/2014/02/28/namespace-planning-in-exchange-2013.aspx
Or is it because both datacenters will be hosting active mailboxes. Will the clients query each CAS server till it finds one in its site? I do also plan to deploy a load balancer with my CAS servers. So I would think that would cancel our using the two public
DNS option.
Nicholas

Migration From Exchange 2010 Hybrid to Exchange 2013 Hybrid Deployment

hi,
I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot.
I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?
Thanks

Hi Muhammad
Can you please give few more information about your environment so that people around here can help you out
I have existing Exchange Server 2010 Hybrid Deployment - Do you have Exchange 2010 and Office 365 in a
hybrid setup now ?
Are you trying to upgrade your on premise Exchange 2010 servers to Exchange 2013 ?
Or Are you trying to migrate your on premise Exchange 2010 to a different forest to Exchange 2013 ?
You can try the below suggestions-
I would better suggest you to follow Microsoft Exchange Server Deployment Assistant - http://technet.microsoft.com/en-us/office/dn756393.aspx
Also i would recommend you to check the prerequisites for hybrid deployment with office 365
http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
Cheers !!!
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Exchange 2013 Deployment

Similar Messages

Maybe you are looking for