2 Exchange 2013 Servers in 2 sites

Hi. I have 2 Exchange Servers total, one in main site and the other one in a branch ofice. Both of them belongs to the same forest, and also both of them have MBX
and CAS roles installed. The goals is to have them in a Database Copy configuration so both of them have the same DBs in case of an issue with any of them (if this is the proper design configuration).
After 2nd server installation I'm not able to connect to it through PowerShell (even though I'm logged on locally in it) as it redirects the connection to the 1st server. Within ECP (of the primary one) I can't see the 2nd server in the Servers tab, nor
the default DB it hosts.
I'm very confused about what the design must be in order to have them replicated with the same functionality. Would you please advice?
Thanks!
Infrastructure Management Sr. Analyst | MCSA Windows Server 2012

As for the design, I would probably add another node in the primary site so you have some local HA. What happened after you forced replication? Did it show up in the EAC? What happens if you go into the shell in the main site and run get-exchangeserver?
Can you also make sure that the Exchange Trusted Subsystem security group is a local administrator on both Exchange Servers? Also, make sure you have a global catalog in each site .
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

Similar Messages

RPC error when configuring Exchange 2013 servers in 2nd site

Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you!

Hello. I'm running into an error when trying to configure any of my Exchange 2013 servers in my 2nd AD site. To get into the loop of what my server structure looks like, please check below:
Site 1 servers:
DC1 - Domain Controller
DC2 - Domain Controller
CAS1 - CAS server
CAS2 - CAS server
MBX1 - Mailbox server
MBX2 - Mailbox server
MATHAFTMG - TMG server
Site 2 servers:
CCCDC1 - Domain Controller
CCCDC2 - Domain Controller
CCCCAS1 - CAS server
CCCCAS2 - CAS server
CCCMBX1 - MBX server
CCCMBX2 - MBX server
CCCTMG - TMG server
Currently I have a site-to-site vpn connection between site 1 and site 2 TMG servers via Internet connection; I can access the servers of the other site perfectly (whether I am in Site 1 or Site 2).
All user mailboxes are currently in Site 1 MBX servers; when users are in Site 2, they connect to the CAS servers in Site 1 to access their mailboxes.
Many users will stay permanently in Site 2, so it makes sense to have Exchange servers in Site 2 to provide faster access to mailboxes. I created the Site 2 domain controllers, and made sure AD replication is working; and it is. I then added the MBX servers
and CAS servers in Site 2 in this order: CCCMBX1, then CCCCAS1, then CCCMBX2, then CCCCAS2.
All Exchange servers in Site 2 installed beautifully. But then I tried to access the servers via ECP to proceed with the configuration. In ECP, I click on the server link, and all Exchange servers in both sites appear. If I try to configure the virtual directories
of Site 1 CAS servers, no problem. But when I try to configure virtual directories of Site 2 CAS servers, I get this error message:
The task wasn't able to connect to IIS on the server 'CCCCAS1.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
The virtual directories issue is just an example. Same thing happens if I try to configure Outlook Anywhere for Site 2 CAS servers.
Users connect to Site 1 CAS servers via mail.domain.com. I have the A record mail.domain.com pointing to the IP address of CAS1 server, and another A record mail.domain.com pointing to the IP address of CAS2 server. Not the best load balancing going on here,
but it works great with Exchange 2013.
From mail.domain.com I can access OWA and ECP internally and externally; no problems there. From ECP I can access and configure any Site 1 Exchange 2013 servers.
The only problem is when I access ECP to configure the Site 2 Exchange 2013 servers, I get the same error message:
The task wasn't able to connect to IIS on the server '<server name>.domain.com'. Make sure that the server exists and can be reached from this computer: The RPC server is unavailable.
Even if I try to access a Site 2 Exchange 2013 server via https://localhost/ecp to configure it, it get the same error message.
I updated all Exchange 2013 servers in both sites to CU2 v2 and rebooted the servers in the proper order; problem still there.
Any clue what might the problem be?
Thank you!

Error 1006 - Changing Ad Site for subnet where exchange 2013 servers was setup

We wanted to change Ad site for subnet where exchange 2013 servers was setup.
When we do that error id 1006 appear on 2 MBX Servers :
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: Database02
Error: An attempt to logon cross-site for Mdb 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' was prevented to Server 'yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy' in Site 'DomainAAA/Configuration/Sites/SiteB'. Local site is 'DomainAAA/Configuration/Sites/SiteA'.
DomainAAA - Our Domain
SiteA - AD site which temporarily cover subnet A and Subnet B
In subnet A are installed 2 DCs (Global Catalog) and other aplication servers.
In subnet B are installed all EX2013 servers (2 MBX and 2x CAS) ,1 DC (Global Catalog) and other app servers.
SiteB - new created AD site intended for subnet B
These subnets are on diferent physical location.
When we change Ad site for subnetB from the AD siteA to AD SiteB, above error appear.
There is a object ExchEdgeSyncService under the AD site : SiteA , where the installation EX2013 was done.
So do We need to create the new edgesyncservice under the siteB ?
What steps do we have to make ?
Our intention is to eventually remove all servers from the siteA and move to to SiteB.
So that siteA will no longer exist.
Thanks in advance , and sorry for bad english.
Best regards

Hi,
Why don't you just extend the VLAN so you don't have to create another site and do changes so much
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.
Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter:
@ikrisna

Migration Exchange 2010 to Exchange 2013 in a different site

Hi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server Administrator

Hi all, I have
an Exchange 2010 with these characteristics
Site A
- 2 Servers DAG for mailboxes
- 2 Servers Client Access and
Hub Transport in Microsoft
NLB
- 2 Domain Controllers Windows
Server 2008 R2
I want to upgrade to Exchange 2013 but in another
Site, Site B. When the migration is complete,
the mail system will only be in Site
B.
The connection between Site A and Site
B is a reliable connection.
Is there any problem to upgrade Exchange 2013
to another Site, other than Site
A?
regards
Microsoft Certified IT Professional Server Administrator
It is like any other Migration (Same Forest) You just need to make sure that AD is been replicated from Site A (Exchange 2010) to Site B (Exchange 2013).
No Network or replication issue between the sites. Having more than 1 DC on Site B would be good idea.
Once you have all these set, rest of the things are same.
Extend the AD Schema.
Deploy the Exchange Server 2013 CU6
Create the Cert request for 2013.
Install Cert on Exchange 2013.
Configure the Virtual Directories for Exchange 2013.
Test the Coexistence between 2010 and 2013.
Perform the Cutover from 2010 to 2013.
Test the Cutover and start the Test migration phase.
Once the test phase is fine, start the full fledge migration.
Move Mailbox and Public Folder Database.
Cheers,
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.

Moving 2nd Exchange 2013 server to another site

Hi there, looking for some insight into a task that has been assigned to me. We have two Exchange 2013 servers setup in a DAG environment. I've been asked to move the secondary to another site. If anyone has gone through this process, do you have any suggestions
or tips
Off the top of my head
Maintenance mode enabled on secondary exchange server
Shutdown VM
Copy to External drive
Ship external drive to secondary site
Create VM and assign new IP
Ensure DNS name for secondary is pointing to the new IP
Boot and turn off Maintenance mode on secondary server
Ensure DAG is replicating over
Questions
Do I have do change anything to ensure exchange realizes it's now off site? The new IP that will be assigned is bound to our secondary site in AD. Example 10.333.333.* = DR-SITE.
Anything I've missed in the steps brainstormed above?
Thank you to all who reply. I am somewhat green when it comes to Exchange but am trying my best to research.
-TSGzz

I would probably take a different approach if possible:
Build new Exchange Server in New Site (making sure storage passes).
Configure Vdirs and add to dag
Add Database Copies
Once database copies are seeded remove old server from the dag and retire it.
I like this method better, b\c you still keep some high availability while you are getting the second site together. PLuS you don't end up not being able to prune you log files since replication would be so far behind once you stand up the server in
the new site.
If you can't do that your steps look like they cover everything.

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.

Mailbox migration between two Exchange 2013 servers is horribly slow

Hi,
when migrating mailbox between 2 exchange 2013 servers,it s horribly slow. I have found some articles which describing problems about content indexing and missing AD group. This is not my problem, I have tried solutions but it didn't work. Both exchange
are next to each one, same VLAN, same switch. Just migrating between databases.
When I start batch jobs it is migrating only 1 mailbox at once and speed is really slow (2000 - 3000 mail items per 5 minutes). So mailboxes which have 10GB it's migrating 3 hours. My server is on 1gbps LAN.
I have also checked MsExchangeMailboxReplication.exe.config on both servers:
    MaxActiveMovesPerSourceMDB="20"
    MaxActiveMovesPerTargetMDB="20"
    MaxActiveMovesPerSourceServer="100"
    MaxActiveMovesPerTargetServer="100"
    MaxTotalRequestsPerMRS="100"
Do you have any idea where to look why only 1 mailbox is migrating at once?
Thanks

Hello,
For the reason why only 1 mailbox is migrating at once when you start batch jobs, there is no official articles or blog to explain it.
I recommend you check if the speed is slower when you move a smaller mailbox. If the issue doesn't occur, I recommend you set
the AllowLargeItems parameter.
Here are some articles for your reference.
New-MigrationBatch
http://technet.microsoft.com/en-us/library/jj219166(v=exchg.150).aspx
Exchange 2013 Local Mailbox Moves
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Configure legacy public folders where user mailboxes are on Exchange 2013 servers

Hello all,
I have mailboxes on an exchange 2013 server than need access to public folders on a 2010 server before I migrate them over. I followed the commands in the TechNet article with the subject "Configure legacy public folders where user mailboxes
are on Exchange 2013 servers" (sorry, I wasn't allowed to insert a link because I wasn't verified?). The problem is when I run the last command of "Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes ProxyMailbox1,ProxyMailbox2,ProxyMailbox3"
on the 2013 server, using the mailbox name I had created, it says it cannot be found. Of course I checked and the mailbox exists, is configured properly, and so is the new database. The 2013 EAC also sees the mailbox with no issues.
Can someone tell me why I am getting this error?
Thanks,
Shaibal

Hi Mavis,
Thank you for your response. I am the full domain admin, and check and was part of both groups mentioned above. Also, I have only one 2010 server with public folder, and so the command I am running on the 2013 looks like this: Set-OrganizationConfig
-PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox1. I even just created a second user and mailbox using the console instead of the shell, and still no luck.
Below is the error I get:
[PS] C:\Windows\system32>Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PFMailbox2
Couldn't find object "PFMailbox2". Please make sure that it was spelled correctly or specify a different object.
    + CategoryInfo          : NotSpecified: (:) [Set-OrganizationConfig], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : [Server=ZOR-EXCHANGE01,RequestId=cc567b2f-34d8-41ba-9261-143223566e06,TimeStamp=3/5/2015
    4:36:10 PM] [FailureCategory=Cmdlet-ManagementObjectNotFoundException] 2EF24201,Microsoft.Exchange.Management.Sys
temConfigurationTasks.SetOrganizationConfig
    + PSComputerName        : zor-exchange01.zubatkin.lan

Probling with Throttling of Emails by Exchange 2013 servers

We are experiecing delay of emails for users because of the Throttlig on Exchange 2013 servers.
This is causing company wide Delay and users are complaining as it takes a lot of time for the queue to get cleared.
We called in Microsoft and they suggested some values changes to msexchangedelivery.exe.config file
We added the following values, but still we face issues when there is Email flood.
Any one faced this or any suggestions that you have.
mdimthyas

Hi mdimthyas,
Thank you for your question.
Could you tell more details which throttling was configured on Exchange 2013 in organization?
Could you tell me how long was emails in the queue?
Are there any other issue which could help us troubleshoot.
We could remove the customized throttling and re-configure it 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 DAG with single site and 2 multi-role servers with error "MapiExceptionIllegalCrossServerConnection"

Hi,
I've got a lab with a domain controller and an Hyper-v with on it two multi-role exchange 2013 CU7 servers on W2K12 R2 OS, configured in DAG semplified (but the problem is the same also if I use the classical DAG configuration), a witness server, and a L7
load balancer for the exchange servers.
When I made the test to disable the OWA application pool where I've got the active mailbox database of the user, the balancer in correct manner redirect the session to the other exchange multi-role server, but the client in his OWA session is no more
able to send new mail with the error "Error your request can't be completed rigt now. Please try again later."
The only strange log that I see on the server in the MAPI client access directory where there is the following error message:
2015-01-21T08:00:45.132Z,956,1,/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt,,Microsoft.Exchange.RpcClientAccess.Monitoring.dll,15.0.0.0,Cached,,,,MapiHttp,Client=Microsoft.Exchange.RpcClientAccess.Monitoring,R:4ab7b6c8-54ee-4be3-aa9d-f8c856c4c47c:2,C:MAPIAAAAAOC4+7OCoZOjkqeKuoumlKSEtYO5ibyGs4bc/879z/vD9sX1zP28AwAAAAAAAA==|S:0-mGmHRQ==,OwnerLogon,0x6BB
(rpc::Exception),00:00:00.0310000,"Logon: Owner, /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt in database last mounted on Exch2.lab.net",RpcEndPoint: [ServerTooBusyException]
Client is being backed off -> [ClientBackoffException] Mailbox was moved to a different mailbox server. A client needs to retry. -> [IllegalCrossServerConnectionException] Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=1247f28558d24d4db872ab127b3e5810-Healt.
-> [MapiExceptionIllegalCrossServerConnection] Monitoring mailbox [] with application ID [Client=MSExchangeRPC] is not allowed to make cross-server calls from [Exch1.lab.net] to [Exch2.lab.net] [diag::AAAOAAAA/wAAAAAAAAAAAgAAAAA=],,,[email protected],
The CAS try to access the mailbox on the other server, but without success.
Someone have idea how to solve?
Thanks

Hi Hinte, sorry for the answer delay.
I've run the command you suggest to check the HealthMailbox status, but seems that all are fine:
[PS] C:\Windows\system32>get-Mailbox -Monitoring | ft name, servername
Name ServerName
HealthMailbox7021deb6ae104dadbf52feedfa7fa68b exch1
HealthMailboxb83c9040b32e4d1197f7f54f6709bb7f exch1
HealthMailboxb1c32037890b43fbb2af2efe7c36ba00 exch1
HealthMailbox8d174269b494458daf9ade5099e22845 exch1
HealthMailboxaa7d10f02d2d4cc588243b291ead3e3a exch1
HealthMailboxeb32c30a019f42968a7cbc49a6ac3e65 exch1
HealthMailboxc6ff1d36ba154c5db5411b44718edcbd exch1
HealthMailbox75dc7caa7e8c4a3b812a01b607536d48 exch1
HealthMailbox16c86e512f454e7890b80c180ce19c00 exch1
HealthMailboxc6e447f7dba24d9b913f1dfcabe9f927 exch1
HealthMailbox40fa5a3f2abc4accae6286cd98abc90a exch1
HealthMailbox2712b9544bad4e7b8b671be2cda8cfde exch2
HealthMailboxe2559124da20499386bf8103dcb21e9b exch2
HealthMailbox3264c6078dad45d4a78c56a3afe81df1 exch1
HealthMailboxacacc51eb8bc4717b295ddf0adccf77e exch2
HealthMailbox64c4dd8cddac4c4e8bb7314010e797b1 exch1
HealthMailbox4a92bfa14fdd47fbb27c19513f6d2beb exch2
HealthMailbox465d2a69de93430e84b4d699a88cb0c3 exch1
HealthMailbox97b578e57cd44204820fffa416b25633 exch2
HealthMailboxb411059771db4647bb775c665ec29440 exch1
HealthMailboxf981dde6f4134f839bf41eb0000434e4 exch2
HealthMailboxc33801c7c3b1474f8aa6065249bb4fca exch1
HealthMailbox2282128ed8d14937998212edd15adf20 exch2
HealthMailboxe3d12b756cf545239b38be4607904ae1 exch2
[PS] C:\Windows\system32>
Regarding the test sugested to diable instead the OWA App Pool only the OWA virtual directory, I've not found on IIS the possibility to stop the access to this virtual directory.
Also on exchnage Administration page there is no the possibility to switch off this virtual directory only (or I don't found where is this setting).
Regards

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.

Public Folders on multiple Exchange 2013 servers

Two companies (lets call them WestCoast Company and EastCoast Company) have merged. Each one has Ex2010 with PFs of local scope (the companies don't need access to each other's PFs). I want to move them to a single Exchange Organization with one Exchange
server in each office and possibly a 3rd Exchange in a data center. I am looking for the best/simplest solution for those legacy PFs. Questions:
- With Exchange 2010 I can only have one PF database so I will have to merge the PF structures. If the "master" PF DB sits in the data center I can choose which folders to replicate to each regional Exchange server (ie I can have only WestCoast
folders on the WestCoast Exchange and similar for East Coast). Are these statements correct?
With Exchange 2013:
- Can I have more than one PF trees (one per PF mailbox) or am I limited to a single PF hierarchy?
- If only one PF hierarchy, am I forced to have one location that holds all the content or can the content remain distributed in different locations?
- Can I have content (or PF mboxes) that only show up on some of the Exchange servers? (ie WestCost PFs will show up only on WestCoast Exchange)
- Do the PF limits (10,000 folders, 1 million items, etc) apply per PF mbox or for the whole thing?
Thanks

There is just one public folder hierarchy. You can assign sub-trees under the root to different mailbox databases, though, and through permissions you could restrict who can see each of them.
You can have public folder mailboxes mounted in different mailbox databases, with different databases mounted in different locations. So you could have the Europe folders in a mailbox in a mailbox database mounted on a European server, and the Americas
folders in a mailbox in a mailbox database mounted on an Americas server.
You can do that but only by grouping public folder mailboxes in mailbox databases that are mounted where you want them to be mounted. As stated before, you might be able to hide folders through permissions, not by where they are mounted.
Yes, the 10,000-folder limit applies to the organization. If you have more than that, wait until the limit is increased.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013, multiple IIS OWA sites with different authentication

Hi
I have an exchange 2013 server with Client Access and Mailbox server installed. The server has an second ip address which I have bound an additional IIS site to. The additional IIS site is named ExchangeExternalFBA.
The default web site is configured for basic and windows authentication with:
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
Then a new ECP and OWA are configured with:
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA"
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA"
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
Then I perform an iisreset.
My problem is that then when I try to access the ECP or OWA on the default website, it loads forms authentication! The ECP or OWA on the ExchangeExternalFBA web site works correctly and also loads forms authentication.
If I run...
get-owavirtualdirectory "owa (ExchangeExternalFBA)"
then it returns:
InternalAuthenticationMethods : {Basic, Ntlm,
WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
If I then run
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
and perform another iisreset then when I try to access the ECP or OWA on the default website it loads correctly. But then the forms based authentication on the ExchangeExternalFBA website can no longer log in, it does not accept the user name and password.
If I then disable and enable FBA on the ExchangeExternalFBA website then it works but forms based authentication takes over the default web site again!
Whether I perform the above from the gui or from powershell it does not make a difference, the same behaviour is observed. Changing the logontype on the FBA does not make a difference.
This has been tested on exchange 2013 cu1 and cu2.
Similar(if not identical until they get sidetracked) issue reported in http://social.technet.microsoft.com/Forums/exchange/en-US/9fcd360f-6658-4940-add7-2f13265cf86b/multiple-owa-sites-on-a-single-server-2012-with-exchange-2013-mailbox-cas.
This worked fine in outlook 2007 and 2010, why now do my virtual directories break each other?
I can reproduce the issue on a test exchange 2013 I built in dev.
Is this a bug or are you no longer meant to host different forms of authentication on a single cas?
I'm mostly interested to see if this works for other people and why it no longer seems to work in 2013, so please no questions; 'why do you want 2 different forms of authentication'.
Much appreciated, Thanks!

Based off of your feedback I have run the following:
Remove-OwaVirtualDirectory "owa (ExchangeExternalFBA)"
Remove-EcpVirtualDirectory "ecp (ExchangeExternalFBA)"
iisreset
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
iisreset
After this there has been no change in behaviour. After the iisreset, forms have again hijacked the default web site and re-setting the authentication on the default web site removes the forms but breaks the ability to sign in to the forms based page on the
ExchangeExternalFBA web site again.
Note. '-Role Frontend' did not work. It showed the error:
Cannot process argument transformation on parameter 'Role'. Cannot convertvalue "frontend" to type
"Microsoft.Exchange.Management.SystemConfigurationTasks.VirtualDirectoryRole".
Error: "Unable to match the identifier name frontend to a valid enumerator name. Specify one of the following enumerator names and try again:
ClientAccess, Mailbox"
+ CategoryInfo : InvalidData: (:) [New-OwaVirtualDirectory], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,New-OwaVirtualDirectory
Running get-help New-OwaVirtualDirectory -detailed shows the correct usage would be '-Role ClientAccess'?
-Role <ClientAccess | Mailbox>
The Role parameter specifies the configuration that should be used
when the virtual directory is created. The following are the values
that can be used with this parameter:
* FrontEnd Configures the virtual directory for use on a Client Access
server.
* BackEnd Configures the virtual directory for use on a Mailbox server.

Method to use Set-EventLogLevel against all the Exchange 2013 servers.

Recently Ran into an issue where we needed to troubleshoot an issue that required us to turn up the logging level across multiple exchange servers using the Set-EventLogLevel command.
I was trying to figure out a way to run this command without having to go to each of the exchange servers.
PSSession doesn't work because then your not running the exchange commandlets on that remote system.
Invoke-Command doesn't work either.
Unfortunately because of some security settings using Connect-ExchangeServer doesn't proxy in the command either.
So any ideas on how we can execute an exchange cmdlet against multiple exchange servers from powershell.
Jeff C

I can set it via this method on Exchange 2010, I don't have Exchange 2013 in front of me but it should be same I believe.
This will set MSExchangeIS\9000 Private\Logons level from Lowest to Low of all the Exchange server in my environment
$test = Get-ExchangeServer
$test | %{Set-eventloglevel "$_\MSExchangeIS\9000 Private\Logons" -Level Low}
To see if those are set or not run this...
$test | %{get-eventloglevel "$_\MSExchangeIS\9000 Private\Logons"}
Blog
|
Get your Exchange Powershell Tip of the Day from here

Exchange 2013 servers not sharing Free / Busy

Some of the users on EXMB01 are not able to see users calendar Free / Busy information on EXMB02.
In our exchange 2013 (CU5) environment the following server: mailbox EXMB01 and EXMB02, CAS EXCAS01, EXCAS02 and EXCAS03. Server are Windows server 2012, mail domain is mail.domain.com and does not match our internal network of local.domain.xyz
(Non standard was setup before me). All setting point to mail.domain.com for mail configuration. External cert from a CA was added to all three CAS servers.
USER1 on EXMB01
USER2 on EXMB02
USER3 on EXMB02
Was able to get USER1 to see a USER3 can see all Free/Busy, subject, location now (only set the Free/Busy time) . Added USER02 see Free / Busy, subject, location (also only set Free/Busy time). Added my own calendar to the USERS01 to the
USERS01 outlook and can see my Free/Busy, subject, location. I only have by default Free/Busy time set no one else added.
What settings to I check first? Is their a PowerShell command to reset a users calendar permissions? Is something not set correctly on the servers?

http://public.wsu.edu/~brians/errors/their.html
Get-MailboxFolderPermission
https://technet.microsoft.com/en-us/library/dd335061
Set-MailboxFolderPermission
https://technet.microsoft.com/en-us/library/ff522363
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

2 Exchange 2013 Servers in 2 sites

Similar Messages

Maybe you are looking for