Exchange 2013 Multi site

Hi
I have Active directory 2012 R2 with sites ( A ,B)
Site A
I have 2 cas servers
I have 2 MBX servers with DAG
ALL users in site B has issue from slow outlook profiles , we suggest to create a CAS server there in B site and memeber of DAG
SO in site B we will have cas server + MBX member DAG
Regarding users in B site how can i enforce the to connect the exchange throw the cas server located in B site ?
How can i confirm that all smtp trafic will go from B site throw cas server located there then to the cas server located in A site then to the firewall ?
is this scenario provide performance wise?
all users for site B will have a DB and will be mounted on MX in B site .
Please need suggestions .
I need to have high performance for outlook profiles located in B site
we have wan link between site A and site B but it is slow .
Do I need to create another DAG ?
when shall we have multiple DAG in our exchange organization ?
Thanks
MCP MCSA MCSE MCT MCTS CCNA

Hi,
Based on your description, CAS servers in site A are Internet-facing, CAS server in Site B are non-internet facing.
In this case, all outbound mail for site B users will go from CAS in site B to CAS in site A and then to firewall and Internet.
All inbound mails will go from CAS in site A to CAS in site B and then go to Mailbox server.
Here is an article which may help you for your reference.
http://technet.microsoft.com/en-gb/library/aa996349(v=exchg.150).aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support
Thanks for you reply Belinda ,
Is it need any configuration from my side ?
MCP MCSA MCSE MCT MCTS CCNA

Similar Messages

Exchange 2013 Multi Site Not SR/HA

This is the first time we have deployed a multi site Exchange organization. Here is the scenario and I am wondering if it is the correct one or if I should have done it a different way.
We have a VPN setup between our corporate location and a satellite campus. The satellite campus has it's own namespace and is a tree in our forest. We have Exchange 2013 SP1 setup at the corp location. We installed two Exchange 2013 SP1 servers
at the satellite location in that domain in the same Exchange organization. I was able to create a few linked users mailboxes (newly acquired and in process of user migration into our forest) and mail delivers between the two without issue. But
lately every new user will not receive email and they will be in the queue. Does not matter if the email is from a corp user or a local user on the same mailbox server.
We decided to do this because we want them to have all of their Exchange resources, email, CAS services and UM local to them, but they are still part of our system. I am having a hard time finding why this is happening. I also noticed that the emails
sent from one satellite user to another is actually going through the corp hub transport server and not their local. Sites and Services is setup with the correct subnets for each site. I have verified the send and receive connectors.
Is this scenario the best way to configure our organization or should we simply have created a second organization of their own and tried to share calendars, etc between the two? All of our other services are centrally located so it only made sense that
this should also work but before going live I wanted to see if this was the optimal way. This is not a high availability or site resiliency plan. No DAGs are used. We are just one company with two separate very remote disjoint locations and
even though we have a small VPN for services we would like to keep as much as possible local to that site.
I have not been able to find information on this scenario. Everything seems to point to SR/HA scenarios. Any advice would be greatly appreciated.

You can't create a second organization when the domain is in the same forest, so you shouldn't have done that.
You're saying that SMTP messages are stuck in the queue? That can be caused by any number of problems, but my experience is that it is most likely one of the following. Look at the SMTP queue and see if any error code is listed, and post that
here.
1. In the main site, the site to which the messages are being sent, someone has modified the Default receive connector(s) in a way that the Exchange server can't connect. The most likely issues would be modifying the PermissionGroups or RemoteIPRanges
properties. Best practice is to not modify the Default receive connector (except maybe to add AnonymousUsers to the PermissionGroups to allow inbound mail), and instead create a new connector for the special purpose with the connection limitations supplied.
2. You have a firewall or relay device between the servers that's "helping" your SMTP connections (Cisco PIX firewalls are notorious for this, disable "SMTP Fixup") or breaking authentication. The servers must be able to connect on port 25 without
any molestation of the transactions.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Implementing Exchange 2013 DR Site

Hi All ,
We have current Exchange 2013 with 2 Mailboxes & 2 CAS servers , we would like to implement Exchange 2013 DR Site , to make only passive copy on DR Site once we have a problem with primary site the mailbox users connecting
to DR Site .
How can achieve this requirements ?
Thank you .

Hi,
If your organization has a third location with a network infrastructure that is isolated from network failures that affect the two datacenters in which your DAG is deployed, then you can deploy the DAG’s witness server in that third location, thereby configuring
your DAG with the ability automatically failover databases to the other datacenter in response to a datacenter-level failure event.
If there isn't a third location for FSW server, you can failover to DR site manually. For more details, you can refer to the following article.
http://technet.microsoft.com/en-gb/library/dd351049(v=exchg.150).aspx
Hope this is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2013 cros site blank page OWA/ECP

Hello,
I have an issue with a fresh installation of Exchange 2013 SP1.
The are two AD site in different cities, connected by WAN link (site-to site VPN organized by Cisco ASA).
I installed two Exchange servers in Site A (MBX1 and MBX2, both with MBX+CAS roles), and one Exchange server MBX3 in Site B (also both with MBX+CAS roles).
Each Exchange hosts its own mailbox database (DB1, DB2, DB3 respectively), there are no DAG.
Users spread over all databases. For example, user1 has mailbox in DB1, user2 - in DB2, user3 in DB3.
When user1 opens OWA/ECP on CAS server MBX1 or MBX2, he successfully get into his mailbox.
But, if user1 opens OWA/ECP on CAS server MBX3, he get blank page (no error at all).
And vise versa:
When user3 opens OWA/ECP on CAS server MBX3, he successfully get into his mailbox.
But, if user3 opens OWA/ECP on CAS server MBX1 or MBX2, he get blank page (no error at all).
I know, that Exchange 2013 is able to proxy request cross site.
Where are no custom redirects set on IIS.
Also I check IIS (Back End Site) for right certificate.
There are no error in Windows Event log and IIS event Log.
All ports are allowed between sites.
Everything looks good.
What I did wrong? May be I need to enable cross-site OWA proxy in Exchange somewhere?
Or it is a CISCO ASA misconfiguration?
Any help would be appreciated!
Thank You!
Pavel

Hi,
Firstly, I’d like to confirm if all your Exchange server are internet facing servers.
We can try to clear the Forms based authentication on the non-internet facing server.
And here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/85983a21-3922-46f4-b64a-d53c0a2271a7/issues-with-crosssite-cas-redirect-of-owa-users?forum=exchange2010
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2013 Multi-tenant contact administration

Hi everybody!
Searched high and low, but couldn't find an answer.
I have deployed multi-tenancy Exchange as a service provider, and will look into self service portals later.
I'm currently developing all the powershell scripts needed to manage the multi tenant environment.
Question arrises:
How do you handle contacts in a multi-tenant environment?
Since a SMTP address can only be used once in an Exchange Organization, what if 2 tenants need the same contact?
- Use customattributes and filter on that? Than what if I want to use the multi-tenant AD for different purposes later?
- Use custom DACLs on the OU or contacts?
- Any other ideas?
Of course I started with
http://blogs.technet.com/b/exchange/archive/2013/02/20/hosting-and-multi-tenancy-guidance-for-exchange-server-2013-now-available.aspx but there's no mention of this issue.
Thank you for any input regarding this issue.
There's a new blog in town: http://msfreaks.wordpress.com

I would advise against "sharing" contacts, as each tenants requirements may be different. Meaning each may want to see different values for various attributes. You may want to stand up an ADLDS instance for each tenant which will hold their contacts independently
of your current Active Directory Forest that houses Exchange. This way, your Exchange Organization remains pristine, no never-ending queues/NDRs for ambiguous SMTP addresses, and each tenant can manage their own contacts without interfering with each
other. Also, I would look into Forefront Identity Manager (FIM).
Woody Colling, MCITP Exchange 2010 --The incentive for the experts to answer posts is to get their replies marked as helpful, or as the answer to our questions, help them help us, mark posts accordingly--

Exchange 2010 - Multi Site DAG with DAC - Node evicted

I have a 2 site DAG with 4 members, 2 at each site with DAC set.
Primary Site:
EXMB01
EXMB02
FSW
Failover Site:
EXMB03 - PAM
EXMB04
AFSW
After updating and rebooting one of the members in the primary active site (exmb02), it looks like the server was removed from the cluster as it was booting back up:
Event ID: 4621
Source: FailoverClustering
This node was successfully removed from the cluster.
Directly preceding that, in the Failover Cluster Manager events, I can see the following progression:
Event ID: 4620
Task Category: Cluster Evict/Destroy Cleanup
Unloading the cluster service registry hive during cluster node cleanup failed. The error code was '3221225569'. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the
'Clear-ClusterNode' PowerShell cmdlet on this machine.
and then: Cluster node cleanup encounted at least one error. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. Please review and resolve preceding cluster node cleanup events. For manual cleanup,
execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine.
And then from all three other nodes:
Node MGR: Cluster node USTRYCO01EXMB02 has been evicted from the failover cluster.
I intend to move the PAM role back to the primary sight, I had not noticed it was there.
Curiously, if I run Cluster.exe node, I can see that all 4 nodes are listed as UP.
What do I need to do to recover EXMB02? I've read that sometimes just a reboot will clean up the cluster configuration, but how would I add the node back into the cluster? Why is it still listed as a node if it was evected? Also,
what is the significance of having the PAM role in the primary data center as opposed to the failover data center?

Hi,
From the error message, you need to run the following cmdlet to force the cleanup on server EXMB02.
CLUSTER NODE /FORCECLEANUP
For more details about error 4620 and 4622, you can refer to these two articles: Event ID 4620 — Node Cleanup Success
and
Event ID 4622 — Node Cleanup Success.
About PAM, the PAM role is automatically held by the DAG member that owns the cluster’s core resource group. It doesn't matter what site the PAM is in, if the server that owns the cluster quorum resource fails, the PAM role automatically moves to a surviving
server that takes ownership of the cluster quorum resource.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

SMTP Authentication in Exchange 2013 multi tenant

I have configure a multi tenant environment. local domain is scurenet.local and i have host 3 different email domains like
abcd.com efg.com and xyz.com. now how its possible to create 3 mailboxes of same login in 3 different domains like [email protected] [email protected] [email protected] also
want to authenticate with there emailIDs and that is main issue. i can create 3 different logins like john1 john2 and john3 in AD and manually add smtp like [email protected] etc.
but issue is how i authenticate users with SMTP IDs so john1 can login using [email protected] and
password john2 use [email protected] as
login id and so on.

Hi,
I think you can try creating mailboxes for the three users and assign the full access permissions to each other.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Unable to send to external email recipients - Multi Tenant Exchange 2013 - MultiRole servers in DAG

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine (external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Send Connectors are the default ones created during install. Receive connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for many hours with no progress.
I have created new Send Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
I am at a loss as to why I can't send out with the default configuration. I would assume that email would flow out without any changes, but this does not happen.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Greetings all, I hope someone can help.
I have created a Exchange 2013 multi-tenant organization, with two servers, both multi-role - CAS and Mailbox roles.
Internal mail flow is fine.
Incoming mail from external senders is also fine. -
external email addresses can send to the domain).
External firewall port forwards ports 443 and 25 to the Internal DAG IP address.
There are two multi-role Exchange servers that are members of the DAG.
I am able to connect to OWA and ECP via https://externalIP/OWA and https://alias.domain.com/OWA
No SSL certificates have been purchased or installed yet.
Exchange URLs have not been changed since default configuration at install.
OWA and ECP works both internal and external.
External DNS works with SPF and PTR records correctly configured
Exchange RCA - Send test only fails with one Spam Listing (this Blacklist provider now flags all domains and you cannot ask to be removed)
Receive Connectors are the default ones created during install. Send connector is standard configuration with - * -
When sending email to an external address, I receive a failure notice
ServerName.test.corp.int gave this error:
Unable to relay
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.
More Info -
ServerName.test.corp.int
Remote Server returned '550 5.7.1 Unable to relay'
I have been troubleshooting this for several days with no progress.
I have created new Receive Connectors for the server that is advising that it is unable to relay, but they have all failed.
I have tried setting the Internal IP address for Exhange Server 1 (Exchange Server 2 reports failure), with most combinations of Security (Anonymous, Exchange Users, etc).
I have also tried with the IP range 192.168.11.0/24 to allow the whole the subnet, I still receive the unable to relay failure notice.
I have tried this guide - hxxps://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/ - with different combinations, still no resolution.
Even more info - Further troubleshooting -
I found my one of my Exchange servers had an extra NIC. I have since added a second NIC to the other server, so now both Exchange servers have dual NICs. I removed the DAG cleanly and recreated the DAG from scratch, using this link -
hxxp://careexchange.in/how-to-create-a-database-availability-group-in-exchange-2013/
The issue still exists, even with a newly created DAG. I also found that the Tenant Address Books were not 'applied'. I applied them but still no resolution
I think the issue is related to multi-tenant configuration even though the error says that it can't relay. The unable to relay message can appear when sending from a domain that the Organization does not support. Like trying to email as [email protected]
when you domain name is apple.com - But through extensive research I still can't resolve the issue.
Can someone please assist before I lose my sanity.
Thanks in advance,
Terry

Second Exchange 2013 server in remote site

Just finished migrating from 2007 to 2013 and decommissioned 2007. Exchange 2013 is running in site A with 350 mailboxes on it. However, almost half of those users reside in site B so the plan is to introduce a second Exchange 2013 server to
this site and migrating mailboxes to it. There already exists a DC & GC in both sites.
My question is, immediately after I introduce Exchange 2013 into site B with CAS & MBX role, client computers from that site will start to receive certificate errors. Will updating the SCP on the new exchange server to point to the SCP on the exchange
server in site A be enough to mitigate that problem? What other precautions will I need to take? Has anybody been down this road?

Hi
You can introduce the second exchange server in the remote site and also setup a DAG. If you are using the same name on your certificate like mail.domain.com then you can use the cert for your second server as well. You need to make sure you have autodiscover
records setup correctly.
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2013/2007 coexistence: The Name on the Security Certificate is Invalid or Does Not Match the Name of the Site.

In the midst of Exchange 2013/2007 coexistence configuration.
Currently:
Exchange 2007:
2 CAS\HUB
1 Mailbox server
Exchange 2013 (2 sites):
LA:
1 CAS
2 MBX servers
MKE:
1 CAS
2 MBX servers.
We purchased a certificate from Digicert and added every SAN name we could think of including "legacy.companyname.com", just to be sure. Added certificate to Exchange 2013 CAS servers and 2007 CAS\HUB boxes. Configured virtual directories on Exchange
2013 MKE-CAS01 but not on Exchange 2013 LA-CAS01. Configured virtual directories to on Exchange 2007 CAS\HUB to point to "legacy.companyname.com".
Mailboxes have not been moved yet. I just wanted to get the coexistence between Exchange 2013/2007 up first but some users (not all) receiving
"The name of the security certificate is invalid or does not match the name of the site" for
"LEGACY.COMPANYNAME.COM". I remember configuring the AUTODISCOVER virtual directory for Exchange 2007. Any ideas? Thank you.

Hi,
Please make sure that the certificate with "legacy.companyname.com" name is enabled for IIS service. We can check it by running the following command in Exchange server 2007:
Get-ExchangeCertificate | FL
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 2 Node Multi role Servers with DAG issues connecting OWA users

Hi
I am on a job at the moment whereby I have 2 exchange 2013 multi role servers. Both are CAS and Mailbox servers. I have 2 databases, 1 called MBXDB01 and the other MBXDB02. MBXDBX01 is on Server 1 and 02 on Server 2.
I have created a DAG and included both databases. Active copy of MBXDB01 is on Server 1 and MBXDB02 on Server 2
I have configured the external and internal URLS of all virtual directories on both servers to be the same publically accessible FQDN. I have assigned the trusted cert to IIS and all other services on both servers. I have modified internal split brain DNS
to point the FQDN used to both Server 1 and Server 2 IP addresses with a TTL of 30 seconds. And also for autodiscover.
All test exchange connectivity comes back green and good from external and from outlook Test-Autoconfiguration autodiscover information is displayed correctly.
The problem I am having is that when a user access the FQDN from a web browser i.e owa.domain.com/owa they get the login screen. This could be from either server 1 or 2 depending on DNS round robin. In this example lets say the user is accessing OWA on SERVER
1 and their mailbox lives on SERVER 2.
In this scenario when they login they get a page :( OOps Something Went Wrong and the exception is this
A problem occurred while you were trying to use your mailbox.
X-OWA-Error: Microsoft.Exchange.Data.Storage.UserHasNoMailboxException
X-OWA-Version: 15.0.847.32
X-FEServer: SERVER1
X-BEServer: SERVER2
The URL provides a little more info
/auth/errorfe.aspx?httpCode=500&msg=861904327&owaError=Microsoft.Exchange.Data.Storage.UserHasNoMailboxException&owaVer=15.0.847.32&be=SERVER2&ts=130398071193518373
However, if the user accesses OWA via the private FQDN of SERVER 2 i.e https://SERVER2/owa they are able to access their mailbox.
It is driving me nuts.
Has anyone got any suggestions? I am tearing my hair out here
Thanks
One very frustrated field engineer :)

Hi,
To narrow down the cause, I recommend the following troubleshooting:
1. Please double check the DNS entries about the host name used in the OWA URL.
2. Add A record that the host name used in the OWA URL points to server 2 IP address in a user local host file. Then try to login OWA again.
3. Check your event log and find if there is any error about OWA.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 migration between AD sites

Hello,
I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
Any advice on performing this migration without issues?
Thanks

Hello,
I am preparing a migration from one Exchange 2013 Cu6 server to another 2013 CU6 server in the same domain in a different AD site. Each server is HT and MB server, hosting its own DB. There is no DAG between the 2 servers.
I am planning to use coexistence between the servers during the migration when I move mailboxes from one server to the other. The move should be transparent to the users. Outlook should detect the move and find it automatically.
I configured one namespace for all URLs, identical on both servers like "mail.organization.nl" for AS, OA, OWA, ECP and autodiscover.
Would this work? I read here it will: The article is referrning to a DAG spanned over 2 sites, which I do not have.
http://blog.netwrix.com/2014/03/21/configuring-exchange-2013-for-site-resilience-2/
Any advice on performing this migration without issues?
Thanks
Mailbox Moves are pretty seamless, so not a concern.
As far as the CAS namespaces. How are you handling that ? Load balancing between the CAS? Round Robin DNS? Or are you going to cut everything over at once and change DNS to point to the new server? Are both CAS accessible from the internet?
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 edge

Hi!
Today we have a site with Exchange 2013 multi-role servers. On our DMZ we have 2 exchange 2010 edge servers. We are planning to install 2 new Exchange 2013 edge servers that will replace the once currently installed. When the new servers are installed and
we have created the edge subscription, will all edge servers (2010 and 2013) be used until we remove the old ones?
Regards,
UC

yes.

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

KeepAlive settings for Exchange 2013 environment

Hello All,
We have very weired problem in our environment. Our environment consists of 10 Exchange 2013 multi-role servers in Primary DC with Wind 2012 OS and 5 servers in Secondary DC with Wind 2012. We have F5 LB & Cisco f/w
Sometime back users reported the outlook disconnection issue and we've implemented following settings in the environment based on MS support team recommendation
1) Configure the Idle session time out on the Network devices to 2 hours.
2) Add the registry key “MinimumConnectionTimeout” with value as 120
seconds as per below article on all the Exchange 2013 Servers. Once this registry key is added, we need to restart the Server for the changes to take effect..
Path: HKLM\Software\Policies\Microsoft\Windows NT\RPC
Type: REG_DWORD
Name: MinimumConnectionTimeout
Value: 120 (Decimal)
3) Add the KeepAliveTime registry key on all the Exchange 2013 Servers
to reduce the Keep alive from default 2 hours to 5 minutes. Once this registry key is added, we need to restart the Server for the changes to take effect.
Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters
Value name: KeepAliveTime
Type: REG_DWORD
Value: 300000 (Decimal)
This value controls how frequently TCP tries to verify that an idle
connection is still intact by sending a keep-alive packet. If the remote computer is still reachable, it acknowledges the keep-alive packet. The recommended value setting is 300,000 (5 minutes).
After applying these settings we've started facing the ACTIVESYNC issue in the environment. We've changed the keep alive setting in exchange server to 29 mins and now activesync issue is solved but outlook disconnect issue started
IS THERE ANYONE who can recommend what is the correct KEEP ALIVE value should be kept in such environment
Our environment has 27K mailboxes totally spread across 50 DBs apprx
Appreciate experts help here !!!
Vinoth Kumar. M
Vinoth Kumar. M

Just to add one more point here
All our network devices including F5 LB has 30 mins as the idle time out value.
We've added below registry values also in all AD DC & Exchange servers
MaxConcurrentAPI
http://support.microsoft.com/kb/2688798
5 in DC
10 in Exchange servers
Vinoth Kumar. M

Exchange 2013 Multi site

Similar Messages

Maybe you are looking for