Can't access site mailbox- Exchange 2013

Hi
Please I have been refered to the Exchange 2013 forum Support team by the SharePoint Team to resolve a complex issue that is unfortunately taking quite some time to resolve. I currently manage a Sharepoint 2013 environment. I have a requirement
to configure and enable the creation of site mailboxes. 
So, I have Sharepoint 2013 installed on A.contoso.com which has all the user accounts( Account Forest). As a means of using the Sharepoint 2013 site mailbox feature, another domain( resource domain) called B.contoso.com has been created. Exchange 2013 has
been setup on B.contoso.com. All the lengthy services on Sharepoint and Exchange 2013 have been configured. A two way trust has been established between both domains. I am able to access resources both ways. On the other hand, when ever I or a user tries to
access a site mailbox it prompts that a mailbox has been created and then takes you to the OWA page of which login credentials don't work. I'm having to now create a linked mailbox and specify the users account in the accounts domain in order to enable a user
login to the created site mailbox. Furthermore, When, I access Exchange management Center I don't see the site mailboxes listed. I only see the linked mailboxes for the account holders. I am only able to view the site mailboxes through powershell. 
Please, I would appreciate it if anyone can help.
Dominic

looks as if there are not many exhange 2013 experts around. Please could you someone look into my question.

Similar Messages

  • Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

    Hi,
    We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
    Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers.  Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
    When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
    problems or the Exchange server is down for maintenance".
    Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM.  Everything is setup as per the Tech-net recommendations.
    Checked both these articles but still it is not working:
    http://support.microsoft.com/kb/2839517
    http://support.microsoft.com/kb/2834139
    Please let me know if there are any other ideas.
    Raman

    Hi,
    I recommend you refer to the following articles to troubleshoot the issue:
    Troubleshooting Mailbox Auto-Mapping : Autodiscover
    Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
    correctly
    Troubleshooting Mailbox Auto-Mapping : Permissions
    When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
    are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
    Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Disaster Recovery site for Exchange 2013

    Hi, I have to build DR site with Exchange 2013 environment and unable to see document for Exchange 2013 perspective.
    In new environment will contain 10 CAS/MBS co-located servers in primary datacenter with two mailbox copies and disaster recovery site with 5 Exchange 2013 CAS/MBS co-located servers with one database copy in blocked activation mode. Any document related
    to this screnario would be helpful. The required solution is when all the servers in PDC goes down then DR site would be activated at DMZ level and Server level. Can I use same IP subnet/Site for the DR site?

    Hi,
    Yes, you can use the same subnet for DR site. If you use the same subnet, you need to use stretched VLAN.
    Here is a related thread for your reference. (This case is for Exchange 2010, but it also applies to Exchange 2013 DAG deployment)
    http://social.technet.microsoft.com/Forums/exchange/en-US/80ca452f-f950-4496-83e8-3067d571bb57/exchange-2010-dag-across-sites-different-subnets-vs-stretched-vlan?forum=exchangesvravailabilityandisasterrecovery
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Re-Create the "Exchange" virtual directory in the "Exchange Back End" Site on Exchange 2013

    Sorry for this stupid question.
    In IIS, I accidentaly deleted the "Exchange" virtual directory in the "Exchange Back End" Site on Exchange 2013 (Mailbox Role).
    What I need to know is the physical path to re-create it.
    Thanks

    Check http://blogs.technet.com/b/get-exchangehelp/archive/2013/02/07/managing-exchange-2013-iis-virtual-directories-amp-web-applications.aspx

  • Java enabled but can't access sites

    I have enabled Java (version 7/21) in Safari/Chrome and Firefox but still can't access sites - they report a "missing Plugin"
    I managed in the past.  What is happening?  any ideas?

    Java is probably not the plugin that is missing. Those sites probably require Flash, which is not installed by default. You can install Flash by downloading it from here:
    http://get.adobe.com/flashplayer/
    As for Java, note that  you really shouldn't have that enabled in your web browser these days. See:
    Java is vulnerable… Again?!

  • Is it possible to only allow given MAC addresses to access ActiveSync in Exchange 2013?

    We are designing a new Exchange 2013 environment for a client and one of their requests was to only allow known mobile devices to access ActiveSync.
    I can see that you can allow or block remote devices based on IP Address, model, etc. but we'd need to allow devices based on their MAC Addresses.
    Is it possible to use the built-in features of Exchange 2013 or IIS ARR to provide this feature?
    Cheers for now
    Russell

    We are designing a new Exchange 2013 environment for a client and one of their requests was to only allow known mobile devices to access ActiveSync.
    I can see that you can allow or block remote devices based on IP Address, model, etc. but we'd need to allow devices based on their MAC Addresses.
    Is it possible to use the built-in features of Exchange 2013 or IIS ARR to provide this feature?
    Cheers for now
    Russell
    No, but you can use DeviceId.
    The ActiveSyncAllowedDeviceIDs parameter specifies one or more Exchange ActiveSync device IDs that are allowed to synchronize with the mailbox. A device ID is a text string that uniquely identifies the device. Use the
    Get-MobileDevice cmdlet to see the devices that have Exchange ActiveSync partnerships with the mailbox.
    To enter multiple values and overwrite any existing entries, use the following syntax:
    <value1>,<value2>.... If the values contain spaces or otherwise require quotation marks, you need to use the following syntax:
    "<value1>","<value2>"....
    To add or remove one or more values without affecting any existing entries, use the following syntax:
    @{Add="<value1>","<value2>"...; Remove="<value1>","<value2>"...}.
    https://technet.microsoft.com/en-us/library/bb125264(v=exchg.150).aspx
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Active Directory Sites and Exchange 2013 Deployment

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

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

  • Introducing Active Directory sites AFTER exchange 2013 installation

    Hi
    We have multiple physical sites and only 1 active directory site.  Email environment is pure on-premises exchange 2013.  Each physical site has CAS/Mailbox servers.  There are not IP restrictions between these physical sites.  Everything
    is outlook anywhere obviously.
    I would like to introduce NEW AD sites for each of these physical locations.
    Do you see any major issues that I need to be aware of?  
    Can this be done in the middle of the day?
    Will there be pop ups in outlooks and disconnects?
    I appreciate your help.

    I haven't had to do this before, but I would probably schedule this at night as there are some changes that will need to be made on the Exchange side of things.
    Once you have the new AD Sites configured (Make sure you have at a minimum one Global Catalog, although I would recommend at least 2 in each AD site). You should cycle the AD Topology Service on each Exchange Server (this is going to cause all services
    to restart so do it one at a time).
    You should also use Set-ClientAccessServer and set the proper site scopes that you want Autodiscover to respond to. 
    I'm sure there's more, but that's what I can think of at the moment.
    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

  • Built-in domain Administrator account not given full access to new Exchange 2013 server

    I migrated from Exchange 2010 to 2013 over the weekend.  I cannot log into the EAC with my domain administrator account I use to log into all my other servers.  I also cannot run the clean-mailboxdatabase cmdlet logged in as this user.  I
    had no trouble moving mailboxes from the old server to the new server with this account though.
    This account is a member of: Domain Admins, Enterprise Admins, Exchange Full Admin, Exchange Organization Admin, Organization Management, Schema Admins, Server Management.
    I can log into the EAC with another admin account that has the same memberships as the Administrator account.
    I tried giving the account the role of "Databases" as suggested by others to fix the clean-mailboxdatabase issue but that did not work for me either.
    The Administrator mailbox has been moved to the new database on the Exchange 2013 server.  The Exchange 2010 has been decommissioned and is turned off.

    Hi,
    Based on my research, to retrieves the mailbox statistics for the disconnected mailboxes for all mailbox databases in the organization, we can try the following command:
    Get-MailboxDatabase | Get-MailboxStatistics -Filter 'DisconnectDate -ne $null'
    http://technet.microsoft.com/en-us/library/bb124612(v=exchg.150).aspx
    Additionally, The Identity parameter specifies the disconnected mailbox in the Exchange database and it can be display name instead of mailbox GUID.
    http://technet.microsoft.com/en-us/library/jj863439(v=exchg.150).aspx
    Hope it can help you.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Outlook 2013 client, not in domain, can't connect to the Exchange 2013 server.

    Hello everyone,
    A colleague and me are in the process of rebuilding our Hosted Exchange servers. Everything is working perfectly except for the local Outlook 2013 clients. They are not in the domain but in the same network (through VLANs) as our Exchange server, and still
    they can't connect to Exchange without the use of Outlook anywhere. If we use Outlook Anywhere, it connects perfectly. If I ping the Exchange servers (1 CAS, 2 MBX servers) I get response with the right IP addresses.
    We've tried to create a new profile, this goes without problems. We enter the FQDN (or IP address) of CAS server and the required usersname, and the FQDN gets resolved to the correct MBX server where the mailbox resides on. We complete the whole wizard and
    then start Outlook. We then get the error that Outlook can't logon to the Exchange server.
    Is this an authentication setting that is wrong or do we need to use Outlook Anywhere if the PC is not in the same domain as the Exchange server?
    Thanks in advance!

    Hi,
    Agree with Martina, all Outlook clients use RPC over HTTP to connect to Exchange 2013. if the server version is Exchange 2013 SP1, only Outlook 2013 SP1 use MAPI over HTTP to connect to server after we enable the protocol MAPI over HTTP.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Journaling mailbox - Exchange 2013 Migrations from 2010

    hi guys
    i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
    and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
    move old one at the end .
    my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ?? 
    thank you
    Indunil

    Hi,
    Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
    And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
    So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Android & WM6.5 devices can't use ActiveSync with Exchange 2013, ADFS and WAP.

    Bit of a long winded title but I was trying to sum up the issue.
    Newly installed Exchange 2013 environment; we've setup external access for OA and ActiveSync.  We've used ADFS with WAP to publish the necessary paths etc.  We've setup DNS and firewall rules etc.
    OA is perfect and can be accessed by anything with a browser.  ActiveSync is perfect for any new Windows Mobile device and any iOS device.  When we've tried to sync older WM6.5 or any Android device, it just doesn't seem to want to work.
    We've checked logs on both devices; the WM6.5 complains about a cert issue however we've took every step from installing the CA, RA and actual cert on the device to no avail.  Some android device complain about using the port 443 but no matter what
    we change this to it still won't sync.
    Unfortunately my suggestion of 'just give everyone a new phone' went down as well as...well lets just say not good :)
    I appreciate this might be an ADFS\WAP issue but thought I'd rule Exchange out first so any advice is much appreciated.

    We are having issues on connecting ActivySync on Microsoft Exchange 2013.
    OWA,OutlookAnywhere is working
    ActiveSync is not working.
    can you help us or share the configuration.
    We have Used MS UAG2010 SP4 to publish Exchange 2013 SP1 (On premises).
    Regards,
    Furqan

  • How can i publish owa on exchange 2013 without ssl?

    hi
    i need connect to owa on exchange 2013 without ssl.
    but when i change config from https to http. my iis return internal error.
    can anybody tell me switch from https to https step by step on exchange 2013?
       regards

    Check out http://technet.microsoft.com/en-us/library/dn635115(v=exchg.150).aspx#OWA
    Bharat Suneja
    Exchangepedia.com | bsuneja
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Please do not send email directly to this alias. This alias is for newsgroup purposes only.

  • Can we connect Outlook with Exchange 2013 with the default Self-signed certificate?

    Hi,
    the question is very simple, but after several days searching in this forums and in the web I have not been able to find a definitive answer YES or NOT. I know that Self-signed certificates are not for a production enviroment and only for labs and we must
    purchase a third party certificate or get one from a internal CA.
    Anyone can answer this question with no doubt?
    Thanks in advance!
    jspt

    Hi Abhi,
    I wrote this question because in a recent migration to 2013 from 2007 we've found with this problem: you can view it in the post http://social.technet.microsoft.com/Forums/exchange/en-US/1ddd1e81-1061-4461-95dd-13de653ef8fe/outlook-cant-connect-with-exchange-2013-after-migration-from-exchange-2007?forum=exchangesvrdeploy.
    Also I have installed a new exchange 2013 in a lab enviroment and I also have unabled to connect from a Outlook 2013. The problem is the same Outlook is unable to detect the exchange server. Many people in this forums told me that have to be a certificate
    problem and for that I posted this question. Honestly, I don't know how to do for Outlook can be connect with Exchange 2013. I don't know what I'm doing wrong.
    Anyway thanks for your answer.
    jspt

  • I deleted cookies from my computer and now I can't access sites that require usernames/passwords

    I recently deleted cookies from my computer and now I can't access any of the sites i used to use with usernames/passwords. even after requesting ne wpasswords etc. the pages just keep resetting

    If you are using Safari, empty the Safari cache.
    With Safari open, press Command + Option + E on your keyboard.
    Quit and relaunch Safari to test.
    ***   When you post for help, please state which OS X is installed.
    If you aren't sure, click About this Mac from your Apple menu 
    Troubleshooting advice can depend on that information.

Maybe you are looking for