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."

Similar Messages

Outlook 2013 with Office365 exchange Scheduling assistant not retrieving free/busy information

Hi, we are using Outlook 2013 with Office365 Exchange and when using the Scheduling assistant in Outlook users are seeing "No Information. No free/busy information could be retrieved". The scheduling assistant works fine in OWA.
I have spent time trying to find an answer on the web but most answers involve different exchange variations.
Mark

Hi,
Since the problem only exists on Outlook Client, we can try running Outlook with the switch "/cleanfreebusy", this will clear and regenerate free/busy information:
outlook.exe /cleanfreebusyin the blank box, then press Enter.
You can also switch between Online and Cached Mode to check if there's a difference.
Regards,
Melon Chen
TechNet Community Support

Exchange 2013 autodiscover not working from Externally

Hi
i have exchange 2010 sp3(2Mb, 2hub/cas). I installed exchange 2013 servers(2MB, 2CAS). For coexistence i generated new certifcate with new cas from third party. I installed that certificate in that cas and assigned all services. i changed all my virtual
directories service url. I didnt import the new certificate to exchange 2010 cas server and i didnt change url to legacy link.But still iam able to check exchange 2010 user mailbox owa, activesync and autodiscover without any certificate error.
If i try to browse owa, its going to 2013 server, if user is exchange 2010 user and its redirecting to exchange 2010 owa with same link.
But i dont know how above things is working without importing to new certificate...
Main problem is i am not able to configure exchange 2013 users outlookanywhere, Autodiscover from externally...
So in tmg i pointed the outlook anywhere ip address new cas server, now both exchange 2010 and exchange 2013 users while OA from external, its keep on asking password... Not accepting it...
Please help me to fix this issue..

Hi ,
On TMG please have the outlook anywhere rule like below and check the status.
Step
1 :
On the TMG rule - >authentication delegation ---> select the option "no delegation users can authenticate directly"
Step
2 :
on the users tab in the TMG rule - just add "all users" group on that rule.
By having the above settings we have avoided the issues in your environment.
Note : Based on the above setting's , Each and everyone in exchange will have a access to the outlook anywhere from external world , because there would not be having any restriction on the TMG rules.
Please have a look in to the below link , it will give you some ideas which is related to TMG
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
Thanks & Regards S.Nithyanandham

Exchange 2013 mailboxes not accessible in outlook

Hi,
In the middle of migration from one exchange 2010 server to 2013 server and thought things were going well. However migrated mailboxes to exchange 2013 are not accessible through outlook although they are through OWA most of the time.
I ran test connectivity comandlet on 2013 server on mailboxes and they tested okay.
However when you connect to mailbox it says exchange unavailable.
I have a new ucc certificate on the exchange 2013 server that includes mail.contoso.com and autodiscover.contoso.com. These are both setup to point to 2013 server with split brain dns. The 2010 server has a certificate for mail.contoso.com.
The SC for autodiscovery right now for both the exchange 2010 and 2013 servers are https://mail.contoso.com/autodiscover/autodiscover.xml
When I run outlook connectivity test I get the following failure:
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exg:6004.
The attempt to ping the endpoint failed
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 24085 ms
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exg:6004.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl07_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 24085 ms

Hi
Did you migrate your DNS to point to the new Exchange 2013 Server?
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 - can not upload apps

Log in to ECP -> Organiztion -> APPS
Below error reported after selecting APPS
Error: The request failed. unable to connect to the remote server.
Note: Same error reported on other exchange 2013 servers.

I had issue with one of the arbitration mailbox, deleted ad account, ran adprep and re-created mailbox.
Error:
[PS] D:\RU5>Get-App -OrganizationApp | fl manifestxml
The request failed. The operation has timed out
+ CategoryInfo : InvalidOperation: (:) [Get-App], OwaExtensionOperationException
+ FullyQualifiedErrorId : [Server=EX1CVTEST2013,RequestId=4a69f46d-5cc1-4299-a5ae-a7416207181a,TimeStamp=6/12/2014
10:45:06 PM] [FailureCategory=Cmdlet-OwaExtensionOperationException] B6E4AE10,Microsoft.Exchange.Management.Exten
sion.GetApp
+ PSComputerName : WWWWWW.XXXX.YYYYY.com
Note: Verified all the arbitration mailboxes are acessable
Arbitration mailboxes:
FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042
SystemMailbox{1f05a927-168e-4658-b14f-5353451a82b0}
SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}
SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}
Migration.8f3e7716-2011-43e4-96b1-aba62d229136

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

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

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!

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

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

Sharing free busy and GAL between exchange organization.

HI, we are looking to share free busy and GAL between 2 exchange organizations. Thus far using the Microsoft federation gateway appears to be the better option for us to achieve this. Although due to both exchange organizations using the same SMTP email
domain we may run into issues trying when both organizations attempt to create the federation trust using the same autodiscover.abcdomain.com
What is the recommended approach to work around this issue?

Change the e-mail domain in one of the organizations.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

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

Using PowerShell to set Custom Access Rights on a Calendar Does not set Free/Busy Permissions

We recently discovered an issue where, if you use Exchange Management Shell to configure custom access rights, the Free/Busy permissions do not get set at all (they remain as "None"):
$temp = [Microsoft.Exchange.Management.StoreTasks.MailboxFolderAccessRight[]]("ReadItems","EditOwnedItems","DeleteOwnedItems","EditAllItems","DeleteAllItems","FolderVisible")
Add-MailboxFolderPermission -Identity "conf-company-test:\calendar" -User "Company Calendar Management" -AccessRights $temp
Add-MailboxFolderPermission -Identity "conf-company-test:\calendar" -User "mpinkston" -AccessRights Editor
If you use a pre-defined "role" such as Editor given to mpinkston6 in the above example it sets the Free/Busy permission to Full Details. It would appear that using Add-MailboxFolderPermission or Set-MailboxFolderPermission is generic for folder
objects, and doesn't explicitly set the Free/Busy permissions. In the case of the pre-defined roles either the command is doing something special/different, or the permission checks later accept pre-defined roles for determining Free/Busy permissions. No idea
which is going on. If Free/Busy permissions can be fixed through PowerShell by some other mechanism/command, that would be great. If not, how do we go about requesting a fix/feature change in Exchange?
http://technet.microsoft.com/en-us/library/dd298062%28v=exchg.150%29.aspx
(Please expand Parameters and read AccessRights to get a better understanding for what I'm describing.)

Did you try adding AvailabilityOnly or LimitedDetails in your $temp variable for Calendar folder? These would set it to "Free/Busy time, subject, location" or "Free/Busy time" respectively....
Add-MailboxFolderPermission - http://technet.microsoft.com/en-us/library/dd298062(v=exchg.150).aspx
The following roles apply specifically to calendar folders:
AvailabilityOnly View only availability data
LimitedDetails View availability data with subject and location
Amit Tank | Exchange - MVP | Blog:
exchangeshare.wordpress.com

Exchange 2013 ActiveSync not working

Hello everyone,
We seem to be having problems with our ActiveSync not working anymore. Users with mobile devices can not access their mailboxes. We have checked just about every setting and the IIS logs and can't find an answer to this issue. Microsoft's Remote Connectivity
Analyzer shows the following error which we can not find an answer for anywhere.
An ActiveSync session is being attempted with the server.
    Errors were encountered while testing the Exchange ActiveSync session.
   Test Steps
   Attempting to send the OPTIONS command to the server.
    Testing of the OPTIONS command failed. For more information, see Additional Details.
   Additional Details
    A Web exception occurred because an HTTP 400 - BadRequest response was received from IIS7.
Thanks!

Hi,
Did you ever find a solution to your problem? I have exactly the same problem with a fresh install of exchange 2013. Can access mailboxes via outlook 2010 and owa but can't connect any mobile device. I'm stumped...
a 400 IIS Bad Request error indicates token bloat. Are you proxying to 2010 mailboxes?
The usual fix is to set the following reg keys on the CAS receiving the requests following the first step described in this article that is similar:
http://support.microsoft.com/kb/2491354
Create the following registry keys on all CAS servers (both Exchange Server 2007 CAS servers and Exchange Server 2010 SP1 CAS servers) in the Active Directory site:
Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Name: MaxFieldLength
Type: DWORD
Value data: 65534
Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Name: MaxRequestBytes
Type: DWORD
Value date: 16777216
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2003, Outlook 2007 and Free/Busy options

We are using Exchange 2003 and Outlook 2007 our Free/Busy options are not showing up, is the a copatibility issue between the two?

Hi,
It is by design that there is no Free/busy option for Exchange 2003 mailbox. Here is a similar thread for your issue:
http://social.technet.microsoft.com/Forums/en-US/00859a5b-ada8-4824-9406-dff8d763b5b8/freebusy-options-in-outlook-2007-exchange-2003?forum=exchangesvrclientslegacy
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 servers not sharing Free / Busy

Similar Messages

Maybe you are looking for