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

Similar Messages

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.

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

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

Exchange 2013 SP1 displaying users that no longer exist

I'm currently in the process of migrating my Exchange 2010 SP3 environment over to 2013 SP1 and am hoping someone can give me a hand with an issue I'm having in Exchange 2013. After installation of 2013 with no errors returned, when I log in to the
admin console I'm seeing users that have been deleted from my AD for quite some time with a mailbox type of "Legacy". I've searched high and low to find these accounts and cannot find them anywhere. I've searched through ADSI Edit and
LDP and nothing. If I click on any of these users and choose to edit I get this error message:
The operation couldn't be performed because object 'GUID' couldn't be found on 'domain controller'.
The odd thing to me is that these "Legacy" users are nowhere to be found on my Exchange 2010 server.
Anyone have any other ideas of how and where I may be able to find these users?

Below powershell script can help you find out the lingering objects in your AD.
$myForest = [System.DirectoryServices.ActiveDirectory.Forest]::GetCurrentForest()
$dclist = $myforest.Sites | % { $_.Servers } |% { $_.Name }
$dcs_guid = get-qadobject -searchroot 'CN=Sites,CN=Configuration,DC=domain,DC=root' -Type nTDSDSA -IncludedProperties guid,dn -DontUseDefaultIncludedProperties | % {@{GUID=$_.guid;DN=$_.dn}}
foreach ($dcforestname in $dclist){
    foreach ($dc_src_guid in $dcs_guid){
        $hostname = ((($dc_src_guid.DN).split(',')[1]).split('=')[1]).tostring()
        $dcfqdn = $dclist -like "$hostname*" | Out-String -Stream
        $dclist_arr = ($dcfqdn).split(".")
        $dcname = $dclist_arr[0]
        $dcdomain = $dclist_arr[1 .. ($dclist_arr.count-1)]
        $domain_dn = ""
        for ($x = 0; $x -lt $dcdomain.Length ; $x++){
            if ($x -eq ($dcdomain.Length - 1)){$Separator = ""}else{$Separator =","}
            [string]$domain_dn += "DC=" + $dcdomain[$x] + $Separator
        write-Host "repadmin /removelingeringobjects $dcforestname" $dc_src_guid.GUID $domain_dn "/advisory_mode >> lingering_debug.log"
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Exchange 2013 Sp1 some users cant access owa

After I install new exchange 2013 with sp1 on windows 2012 R2 server one for mail boxes and the second Client Access, i move all mail boxes to it, then i uninstall the old server (exchange 213 with cu3).
All may exchange server’s virtual machines on hyper-v 2012R2
I install certificate and configure virtual directories
I notice some users can’t open there mail boxes from OWA they get a blank page after the enter username and password (from internal and external) (the same users can open outlook anywhere) at the same times many users can access owa.
After many restarts they can access OWA.
After some days some other users can’t access owa.
I remove ECP and OWA virtual directories, Then Recreate and configure it.
But the same problem some users cant access owa
I install a new client access server, configure it
But the same problem

HI
YOu can check below things to resolve the problem
Disable SSL from Default Web Site if you have enabled them
Check if you have set any redirection in the Default Website if so remove redirection and see the results
Ensure that you have a valid certificate for owa VD
check correctly the authentication type - windows authentication is enabled or if you have form based authentication enabled
Below is an example for enabling WA
set-Owavirtualdirectory -identity "servername\owa (Exchange Back End)" -WindowsAuthentication $True -Basicauthentication $false -Formsauthentication $false
Set-EcpVirtualDirectory -Identity "servername\ecp (Exchange Back End)" -WindowsAuthentication $true -FormsAuthentication $false
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

Exchange 2013 free/busy not seen by users in different mailbox database suddenly

Hi folks,
suddenly I have this problem that users in Maildb1 can't see free/busy information at users in Maildb2 and vice versa in my Exchange 2013 environment. Users in the same MailDB can see eatch other free/busy info, but not via databases.
Anyone familyar with that one?
My setup is:
cas0 15.00.0775.041 (15.00.0775.041 15.0.775.41 2880833 Security issue that is described in Security Bulletin MS13-105 is resolved by an Exchange Server update
December 10, 2013)
cas02 15.00.0775.041 (15.00.0775.041 15.0.775.41 2880833 Security issue that is described in Security Bulletin MS13-105 is resolved by an Exchange Server update
December 10, 2013)
Regarding to: http://exchangeserverversions.blogspot.com/2013/01/exchange-server-2013.html (http://support.microsoft.com/kb/2880833/en-us)
mbx01 15.00.0712.024 ( Exchange Server 2013 Cumulative Update 2 (CU2)
15.0.712.24 07/29/2013)
mbx02 15.00.0712.024 ( Exchange Server 2013 Cumulative Update 2 (CU2)
15.0.712.24 07/29/2013)
Regarding to: http://exchangeserverversions.blogspot.com/2013/01/exchange-server-2013.html (http://support.microsoft.com/kb/2859928/en-us)
Thanks in advanced,
Bjarni

Hi,
Please make sure that Exchange Autodiscover is set up correctly for all organizations that use an organization relationship. If Autodiscover isn't working correctly, there's no supported way for you to use organization relationships.
Make sure that Autodiscover URLS can be resolved internally and externally for the organization with which you want to share free/busy information.
Make sure that the organization with which you are sharing free/busy information has its external EWS endpoint set up.
Refer to this link for more information.
https://support.microsoft.com/kb/2838688?wa=wsignin1.0
In addition, if the users are in different organizations, please configure Organization relationships for them to share Free/Busy information.
http://technet.microsoft.com/en-us/library/jj657445(v=exchg.150).aspx
By the way, if the database are on different forest, please try to
configure the Availability service for cross-forest topologies.
http://technet.microsoft.com/en-us/library/bb125182(v=exchg.150).aspx
Best Regards.

No users are being migrated to the Unified Contact Store (UCS) for Lync 2013 - Exchange 2013

I'm having difficulty getting the unified contact store to work on a migrated Lync/Exchange environment. Both servers have been upgraded to 2013 CU2, and almost everything appears to be working properly...except UCS.
By default the global CsUserServicesPolicy has UcsAllowed set to True. In that mode, none of the Lync users were being migrated to UCS, so I set the global policy to False and created a new Policy called "AllowUCS" and set UcsAllowed to True. I then
assigned that policy to myself and a couple other test accounts. Still, my contacts are not being migrated to the UCS after logging in with Lync 2013.
Other Lync/Exchange integration features are working properly. I have set up OAuth, and it tests successfully, and Lync integration with OWA is working successfully, so I know at least some communication is happening properly between the servers.
Here is what I'm getting when I run some diagnostics from the Lync server:
PS C:\Users\administrator> get-csuser jdoe |FL Name,UserServicesPolicy
Name : Jon Doe
UserServicesPolicy: AllowUCS
PS C:\Users\administrator> Get-CsUserServicesPolicy |FL
Identity : Global
UcsAllowed : False
Identity : Tag:AllowUCS
UcsAllowed : True
PS C:\Users\administrator> Debug-CsUnifiedContactStore -Identity [email protected] |FL
UcsMigrationAttemptCount : 0
LastUcsMigrationAttempt :
SipUri : [email protected]
UcsMode : Disabled
PS C:\Users\administrator> Debug-CsUnifiedContactStore -PoolFqdn lync.domain.org
FrontEnd : lbclync.domain.org
UcsDisabledCount : 141
UcsAllowedCount : 0
UcsMigratingCount : 0
UcsMigratedCount : 0
FailedUserData :
PS C:\Users\administrator> Test-CsUnifiedContactStore -UserSipAddr
ess [email protected] -TargetFqdn lync.domain.org
Target Fqdn :lync.domain.org
Result : Failure
Latency : 00:00:00.0654970
Error Message : User has not been migrated. Verify that the user has a mailbox
in Exchange and that the user has been migrated.
Diagnosis :
Anyone know what I am missing?

Hi,
Please make sure the user has been provisioned with an Exchange 2013 mailbox and has signed into the mailbox at least once.
If the user logs in with a Lync 2010 or earlier client, or if the user is not connected to an Exchange 2013 server, the user services policy is ignored and the user's contacts remain in Lync Server.
Please also check the registry key on the client computer:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync\<SIP URL>\UCS
If the user's contacts are stored in Exchange 2013, this key contains a value of InUCSMode with a value of 2165.
Kent Huang
TechNet Community Support

Creating a New Email address policy for users in another Domain with Exchange 2013 powershell?

Hi
Everyone
Is it possible to create a new-emailaddress policy with Exchange
2013 Powershell, for users within OU´s located on another different
domain/forest than where Exchange 2013 is installed?
There
is a Transitive, two way trust between the domain/forest where the users are
located - and the Exchange 2013, multi tenant domain.
Further
more, and if possible, I need to create linked mailboxes to all these users as
well.
Í have been struckling with this issue for weeks, so please anyone -
advice - and comment.
Best
Regards
Peter
A-ONE Solutions

Hi Siddharth
I want to create a new e-mailaaddress policy - and after that create linked mailboxes/users in my account domain with powershell.
Can you help me achieve that ?
I have a powershell CMDlet, but i doesn´t work. (Cannot fint user OU in my account domain)
CMDlet is as follows:
New-EmailAddressPolicy -Name $CustomerName -RecipientContainer "OU=$CustomerName, OU=kunder, DC=Domain, DC=local" -IncludedRecipients 'AllRecipients' -ConditionalCustomAttribute1 $CustomerName -Priority '1' -EnabledEmailAddressTemplates SMTP:%2g%1s@$AcceptedEmailDomain
Where $Customername = test.dk
and Account domain is = OU=kunder, DC=Domain, DC=local
But the command fails with:
New-EmailAddressPolicy : Couldn't find organizational unit "OU=Test.dk, OU=kunder, DC=Domain, DC=local". Make sure you have typed the name correctly.
At line:52 char:1
+ New-EmailAddressPolicy -Name $CustomerName -RecipientContainer "OU=$CustomerNa
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [New-EmailAddressPolicy], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : [Server=HE-MBX03,RequestId=2cbe1b51-4af2-4c04-9f7e-e440000975e6,TimeStamp=24-03-2014 12:58:19] 2D00FD2A,Mi
crosoft.Exchange.Management.SystemConfigurationTasks.NewEmailAddressPolicy
So, I cannot find the OU on the Account forest/Domain, even though the OU do exists in the Account domain.
Verifying with this:
Get-ADOrganizationalUnit -Identity "OU=$CustomerName,OU=kunder,DC=Domain,DC=local" –Server ‘DC01.domain.local’| FL
This works fine, Can you please help/assist?
Peter

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

Exchange 2013 Hybrid Configuration Wizard OAuth error

Hi,
We are facing following error when we run OAuth configuration after complete the Hybrid Configuration Wizard.
Error:
ScenarioFailureException
Message:
Exchange OAuth authentication couldn‎'t find any accepted domains in your on-premises organization.
Verify you‎'ve configured at least one on-premises accepted domain.
Location:
   at Microsoft.Online.CSE.HRC.Activities.OAuthActivities.GetCertificateActivity.Run‎()‎
   at Microsoft.Online.CSE.HRC.Workflow.Activity.WorkflowBaseActivity.Launch‎()‎
   at Microsoft.Online.CSE.HRC.Workflow.Runtime.WorkflowActivityHelper.Execute‎(ActivityContext context, Boolean launch)‎
   at System.Activities.NativeActivity.InternalExecute‎(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)‎
   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody‎(ActivityExecutor executor, BookmarkManager bookmarkManager,
Location resultLocation)‎
Environment:
2x Exchange 2013 CU6 (DAG+one ClientAccess)
Directory Sync Server
No ADFS server since we don't need single sign on
Office 365 E3 Tenant
We have tried manually setup the OAuth configuration according to the below TechNet article but failed when running the ExportAuthCert.ps1
script file. It couldn't match the certificate thumbprint with the location "Cert:\LocalMachine\My"
http://technet.microsoft.com/en-us/library/dn594521%28v=exchg.150%29.aspx
Please help!
Thanks in Advance
Roshan

We have the exact same Issue, tried the exact same setup and NO JOY!! - any resolution yet?
Also found this article:
http://consulting.risualblogs.com/blog/2014/09/10/exchange-2013-cu6-hybrid-users-with-o365-unable-to-query-freebusy-for-on-premises-users/comment-page-1/#comment-5192
..... but did not fix the free/busy
Best Regards,
Francois

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 Deployment - 150 Users

Similar Messages

Maybe you are looking for