Auto-mapping of shared mailboxes in a resource forest scenario

In a resource forest scenario you assign full access to a shared mailbox using:
Add-MailboxPermission -Identity SharedMailbox -User AccountForestDomain\UserID -AccessRights FullAccess
This provides the user in the account forest full access, but it will NOT auto-map the shared mailbox in Outlook.
If you use the command:
Add-MailboxPermission -Identity SharedMailbox -User UserID -AccessRights FullAccess
and UserID is the disabled account of the linked mailbox in the resource forest then the user in the account forest does not have the necessary permission to
open the mailbox, but the auto-mapping of the mailbox in Outlook works.
You have to use both commands to have the auto-mapping feature and have access to the shared mailbox.
This looks like another issue of the auto-mapping feature. The intention of the feature is good, but the way it was implemented can be improved.
How do you configure full access to shared mailboxes in a resource forest scenario?

Hi J-H,
Because i don’t have such a lab environment, so I am unable to do a test.
Now let’s separate the issue.
1. The first issue is
[email protected]
unable to auto configure outlook profile.
I suggest you
changing the user’s attributes in the account forest, does it work?
 2. The second issue is
[email protected] unable to open a shared mailbox in the resource
forest.
At first, I suggest you create a shared mailbox in resource forest with this command.
New-Mailbox -name
<name> -Database <Database name> -OrganizationalUnit Users –UserPrincipalName
<UPN value, example: [email protected]> -<ResourceType: Room, Equipment or Shared>
Managing
Resource Mailboxes in Exchange Server 2007 (Part 1)
Then test if you can log on the shared mailbox via outlook.
If yes, then grant full access right for
[email protected]
to [email protected]
Resource:
Shared mailbox
permission in resource forest with linked users
Manage Full Access Permissions
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

  • Exchange 2010 Auto-Mapping not removing mailbox from Outlook

    I am having an issue that others seem to have as well.  When I give Full Access to another mailbox, auto-mapping brings it in to the users Outlook 2010 client.  However, when I remove that users access to the shared mailbox it doesn't remove the
    mailbox from Outlook.
    I know that I can go the shared account in ADSIedit and edit the msExchDelegateListLink and remove the user that should no longer have access, but this is not a good solution.  I feel this is a bug that Microsoft should address and release a patch for.
    Does anyone know of a fix?  Not a workaround, an actual fix?

    Hi,
    Based on my experience, we can take the following actions to remove the additional mailbox :
    1. Turn off the auto-mapping feature for your account:
    Add-MailboxPermission usermailbox –user PersonBeingGrantedRights –AccessRights ‘FullAccess’ –AutoMapping:$false
    2. Remove the full access permission by using EMC or EMS.
    3. Clear the msExchDelegateListLink attribute for all mailboxes which are being displayed as an additional mailbox in Outlook. In your case, you need change 10 msExchDelegateListLink attributes.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

    We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
    add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
    Orange County District Attorney

    This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
    Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Exchange 2013 OWA: Cannot set auto reply in shared mailbox

    We use Exchange 2013 and Outlook 2010. We have 3 users tha connect to a shared mailbox. We would like to have an auto-reply on this mailbox but cannot set it with the OWA. We get the following error:
    Client Information
    User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; InfoPath.3)
    CPU Class: x86
    Platform: Win32
    System Language: nl-NL
    User Language: nl-NL
    CookieEnabled: true
    Exception Details
    Date: Fri Jul 11 11:31:40 UTC+0200 2014
    Message: Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
    Url:
    https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
    Line: 5
    Call Stack
    Dump Event
     errorMessage = Kan de eigenschap _events van een niet-gedefinieerde verwijzing of een verwijzing naar een lege waarde niet ophalen
     errorUrl =
    https://owa.'domainname'.nl/ecp/15.0.712.22/scripts/microsoftajax.js
     errorLine = 5
     errorCharacter = 57312
     errorCode = 0
     actionURL =
     altKey = false
     altLeft = false
     behaviorCookie = 0
     behaviorPart = 0
     bookmarks = null
     boundElements = [object HTMLCollection]
     button = 0
     buttonID = 0
     cancelBubble = false
     clientX = 1187
     clientY = 72
     contentOverflow = false
     ctrlKey = false
     ctrlLeft = false
     data =
     dataFld =
     dataTransfer = null
     fromElement = null
     keyCode = 0
     nextPage =
     offsetX = 0
     offsetY = 0
     origin =
     propertyName =
     qualifier =
     reason = 0
     recordset = null
     repeat = false
     returnValue = true
     screenX = 2373
     screenY = 343
     shiftKey = false
     shiftLeft = false
     source = null
     srcElement = null
     srcFilter = null
     srcUrn =
     toElement = null
     type = error
     url =
     wheelDelta = 0
     x = 0
     y = 0
     getAttribute =
    function getAttribute() {
        [native code]
     removeAttribute =
    function removeAttribute() {
        [native code]
     setAttribute =
    function setAttribute() {
        [native code]
    Detailed Call Stack

    Hi,
    Error information is quite important. In order to solve your issue effectively, please take your time to describe the error in English for my research.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Lync 2013 Hybrid deployment with resource forest scenario on-premise

    Hi there,
    Im starting to deploy this scenario of Lync on-premise in resource forest with Lync Online:
    I´am not finding any documentation about this specific scenario. I wish to know how the flow between forests will be to have users in lync online and users on premise.
    Thank you very much in advance for your help.
    Joaquin Gonzalez

    Hi Joaquin,
    You need to deploy Microsoft Forefront Identity Manager (FIM) 2010 to manage the life cycle of user accounts.
    In a resource forest topology, one forest is dedicated to running server applications, such as Microsoft Exchange Server and Lync Server. The resource forest hosts the server applications and a synchronized representation of the active user object, but it
    does not contain logon-enabled user accounts. The resource forest acts as a shared services environment for the other forests where user objects reside. The user forests have a forest-level trust relationship with the resource forest. When you deploy Lync
    Server in this type of topology, you create one disabled user object in the resource forest for every user account in the user forests. If Microsoft Exchange is already deployed in the resource forest, the disabled user accounts might already exist. A directory
    synchronization product, such as MIIS, Microsoft Forefront Identity Manager (FIM) 2010, or Microsoft Identity Lifecycle Manager (ILM) 2007 Feature Pack 1 (FP1), manages the life cycle of user accounts. When a new user account is created in one of the user
    forests or a user account is deleted from a forest, the directory synchronization product synchronizes the corresponding user representation in the resource forest.
    Click the links below for more information.
    Supported Active Directory topologies in Lync Server 2013
    http://technet.microsoft.com/en-us/library/gg398173.aspx
    Windows Azure Active Directory Connector for FIM 2010 R2 Quick Start Guide
    http://technet.microsoft.com/en-us/library/dn511002(v=ws.10).aspx
    Hope it can be helpful.
    Best regards,
    Eric

  • 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

  • AADSYNC in Account/Resource Forest

    Hello,
    we installed AADSYNC in an Account/Resource Forest Scenario. The logic in this scenario is that the object that will be synced to Office365 is put together with information from account and resource forest. It knows what to combine by taking into account
    that the objectsid from account forest and msexchangemasteraccountsid from resource forest are the same for the users that need to be synchronized.
    Now we have some filtering in place to only sync user objects from both forests when they have the attribute "pager" filled with "Office365".
    This works fine most of the time. The user object to sync is successfully buidl together with information from both forests and exists only once in the Metaverse.
    If we create new users we create them first in Account forest and then we do migrate them with admt to the resource forest. Then they get the mailbox (linked) and are disabled in resource forest. If we fill the filter attribute first in AD meaning the pager
    gets filled with "Office365" and a synchronization process occurs before filling the pager attribute in the other forest we end up with two different objects in the metaverse and only the account part is synchronized to Office365.
    Is this by design? Is there any workaround to combine the two different metaverse objects into one?

    It depend's on the Version, but if you are using Azure AD Sync, you can open the "Synchronization Rules Editor", and edit the "In from AD - User Join" Rule:
    And when you have two AD to sync, make sure, that the second (resource forest) ist selected to join, because this will prevent to create new user objects from the resource forest:
    www.sccmfaq.ch

  • Exchange 2013 resource forest deployment, auth error with imap/pop3 clients.

    Hello Everyone!
    We have an issue with pop/imap clients trying to authenticate.
    Users log on with credentials from Account Forest, security audit shows a succesful log on and impersonation from process Microsoft.Exchange.Pop3.exe, but fails to login to mailbox.
    The following warning appears in the event log:
    Log Name:      Application
    Source:        MSExchangePOP3
    Date:          22/01/2014 11:41:29
    Event ID:      2005
    Task Category: (1)
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      exchangeCAS
    Description:
    User [email protected] wasn't found in Active Directory.
    Protocol logs show the same warning.
    Seems that Microsoft.Exchange.Pop3.exe process is unable to determine the linked mailbox of the provided credentials.

    Thanks for your answer.
    We can access this mailbox with any protocol but pop/imap.
    Anyway, I think that I found something. 
    In an isolated enviroenment, with an Active directory trace (Performance Monitor tool) those are the LDAP querys with some tests:
    Trying to log on with an account in the same forest as the mailbox:
    User string: resource.forest\administrator\userA_linkedMB
    LDAP Query: ( (mailNickname=userA_linkedMB) ( !(msExchCU=*) )  ....
    Success, as expected.
    Trying to log on with an account in the account forest:
    User string: account.forest\userA\userA_linkedMB
    LDAP Query: (  (sAMAccountName=userA) ( !  (msExchCU=*) ) ....
    First, in this case the query seems incorrect, I expect it filtering by mailNickname and with the third part of the logon string. Of course it fails because there isnt any user with this SAM in the resource forests.
    Same test, with resource.forest\userA, sAMAccountName = userA
    User string: account.forest\userA
    LDAP Query: (  (sAMAccountName=userA) ( !  (msExchCU=*) ) ....
    This query returns 1 matching user, but seems that pop3 process checks if its from account.forest (it isn't of course, because query is sent to resource.forest DC) and fails.
    I'm not sure, but seems a bug in the POP3/IMAP login code.

  • Outlook 2010 - Automatic signatures for auto-mapped shared mailbox..

    Hi,
    I have recently received below 02 requests for a shared mailbox:
    Automatic signature or standard bottom lines  for shared mailbox, user have full mailbox and send as permission?
    Automatic response and auto delete of all incoming mails for shared mailbox?
    Is there a way to achieve this, Please help!

    Hi,
    If you want to set separately default signatures for each mailbox, primary mailbox and shared mailbox, I'm afraid there is no way to achive this goal from Exchange side, you may need some third party software.
    Here is a similar thread for your reference.
    https://social.technet.microsoft.com/Forums/en-US/5c62c553-7533-4547-b49d-dcbffeb447e1/outlook-2010-automatic-signatures-for-automapped-shared-accounts?forum=outlook
    To create automatic reply, you can use the Set-MailboxAutoReplyConfiguration command. And if you want to delete all messages for incoming to this share mailbox, you can run the New-InboxRule command to create an inbox rule for this shared mailbox to delete
    incoming messages.
    More information about these commands:
    https://technet.microsoft.com/en-us/library/dd638217(v=exchg.141).aspx
    https://technet.microsoft.com/en-us/library/dd335170(v=exchg.141).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Is there a way to create a rule that sends and Auto Response for a shared mailbox?

    I have a shared mailbox set up that receives emails that are sent to 3 different addresses:
    [email protected]
    [email protected]
    [email protected]
    I would like to create a rule that would send an auto response when someone emails one of these addresses.  However, I don't want an auto response sent to [email protected] so I can't just set up an "out of office" reply for the mailbox.
    Is there a way that I can create a rule to send an automated response to 2 of the 3 addresses?
    Nate

    Hi 
    we can enable the shared mailbox in ADUC and create Outlook rules for it in Outlook to achieve it. please follow these steps:
    1. In Active Directory Users and Computers, right-click the shared mailbox and click Enable Account.
    2. Configure the Outlook account for the shared mailbox in Outlook.
    3. Click Rules > Manage Rules & Alerts.
    4. Create a rule like the following format:
         Apply this rule after the message arrives
         Have server reply using a specific message
         Except if the subject contains specific words
         Select exception(s) (if necessary) of the Outlook Rule - (“except if from people or public group“)
    5. Apply the auto reply rules for this shared mailbox.
    Then users can receive auto reply of the shared mailbox except the exceptions we have set  when they send messages to this shared mailbox.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

  • Issue with Update Rollup 5 for Exchange 2010 SP3 - Mailboxes that were auto mapped not working

    Below is  my response in another thread but creating a new one in the hopes that someone has the same issue and a solution besides mine below.
    Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
    Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
    What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
    Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
    the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
    I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
    This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

    Not sure why it was suggested to use the auto mapping feature to grant permissions because that is the component that is causing the issue. Also, there is nothing wrong with the auto configuration because the user can access their own mailbox just fine and
    also select mailboxes in their Outlook that were NOT auto mapped.
    With that said, here is how I fixed them all.
    Remove the permissions using the Exchange Console. Don't forget Send As
    Wait about 15 minutes. The mailbox should disappear from the users Outlook
    Open an Exchange PowerShell window and run the following command:
    .\add-mailboxpermissionsnoautomap.ps1 -Identity mailbox -User user -AccessRights FullAccess
    Have the user add the mailbox to their Outlook using the manual process.
    All is well....
    If you don't have the PS script add-mailboxpermissionsnoautomap.ps1, you can download it. I stumbled across it a few years ago and use it all the time. If you can't find it, just use the Exchange built in command for adding mailbox folder permissions but
    specify automap $false.
    The idea here is to grant the user access without auto mapping.

  • Office 365 Shared Mailboxes - Auto Reply

    We've just migrated from an exchange 2003 to Office 365.
    We have several shared mailboxes where previously they had an out of office setup with a generic message on it.  Now that those mailboxes have been turned into'Office 365 Shared Mailboxes' without licenses attatched, i can't seem to work out how to
    setup a similar auto reply for each of the mailboxes. 
    The only thing i can see is to assign a license to each of the mailboxes that we want to have an auto reply and treat them as normal users, but this just seems a waste of money.
    Any Help?

    It appears you may have bumped into a limitation of Office 365.
    You might try this workaround.  License the mailbox, log in, set the out of office message, log out, and remove the license.  If the out of office message stays, then you have your workaround.  Please post here whether or not that works so
    others will benefit from your experience.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010 /hosting shared mailbox issue

    Hello everyone.
    I had an issue come up in our Exchange 2010 with /hosting switch deployment (currently at SP2).
    We have several organizations and shared mailboxes configured and working on some. We add Full access permissions via Powershell + Send as rights and it auto configures and works just fine.
    Last week though, one of several people that uses a specific shared mailbox started getting the error: "Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the
    Microsoft Exchange Server computer is down for maintenance." (Error ID: 300)
    The other users can still work just fine. Configuring the account in another PC shows the same problem (so it's not the local profile).
    Creating 2 users, giving nr1 full access to nr2 generates the same error.
    In another org though, i was able to give full access to another acount to an existing user and it worked (although the auto-mapping didn't, had to add it manually)
    I'm out of ideias. Any sugestions?
    EDIT: Did a couple more tests on another Org. On this one everything works with the shared folder access with old and new accounts but strangely the auto-mapping doesn't.
    It seems that this is an issue with the mapping.
     

    Hi,
    From your description, I recommend you manually update or create your Outlook profile with RPC encryption and check the result. Here is the steps on Outlook 2007 for your reference:
    1. Select your profile, and then click Properties, click E-mail Accounts.
    2. Select the Microsoft Exchange Server account, and then click Change.
    3. In the dialog box that contains your mailbox server and user name, click More Settings.
    4. In the Microsoft Exchange Server dialog box, click the Security tab.
    5. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK.
    6. Click Next, and then click Finish.
    For more information, here is a kb for your reference.
    Connection issues and error messages in Outlook for a mailbox on a server that is running Exchange Server 2010
    http://support.microsoft.com/kb/2735060
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Opening a shared mailbox in Outlook 2013 (office 365) returns "Cannot Expand Folder" error.

    Hi!
    We've just upgraded from our old Domino email server to Office 365 E1 and running an on-premise Exchange 2013 hybrid server.
    In Outlook 2013, when trying to expand a shared mailbox, It asks me to enter my outlook credentials. Trying so doesn't work and it continues to ask repeatedly. If I click cancel, I get the following error:
    "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."
    The error only occurs in Outlook 2013 and it happens to all staff who are using Outlook 2013. Shared mailboxes are accessible in Outlook 2010 and OWA with no issues.
    I have tried recreating profiles, removing and re-adding permissions, disabling auto-mapping. I've tested with creating shared mailbox in Exchange Online and on our hybrid server.

    Hi,
    Check if the kb below matches your scenario:
    https://support.microsoft.com/kb/2992644
    This problem occurs only when the following conditions are true:
    You are using Microsoft Outlook 2013 client version 15.0.4641.1001.
    The client is connected by using Outlook Anywhere (RPC over HTTP).
    To resolve this issue, apply the update that is described in the following article in the Microsoft Knowledge Base:
    2889859
    If you are using the Click-to-Run version of Office 2013, the Outlook application is kept up to date automatically. For more information about Office 2013 Click-to-Run updates, see
    Microsoft Office 2013 Click-to-Run virtualization
    I hope the information is helpful.
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Easier way to find shared mailbox permissions

    I'm wondering if there's a way to query for what I will call the reverse record for auto-mapping. Outlook dynamically adds shared mailboxes that the user has permission to. Is Outlook brute force searching though all objects looking for permission, or is
    there a PowerShell command that I can use to find them quickly.
    Something like:
    get-AutoMappedMailboxes -user [email protected]
    and it would return the list of mailboxes the user has permissions to:
    sales
    accounting
    etc
    This would be a cool feature, if not already there!

    Hi,
    In addition to Ed's suggestion, I would like to clarify the following thing:
    If you want to prevent auto-mapping, you need to add -AutoMapping:$false to the Add-MailboxPermission command. If access has already been granted you should first remove it. Then run Add-MailboxPermission again with auto-mapping disabled.
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

Maybe you are looking for

  • DATA LOADING PROBLEM

    Hi All,        I am loading data from data source to DSO and from dso to cube.       i am getting data in DSO , and when i run DTP for DSO and cube the data does not come in cube.       There is no status message for error while executing the DTP .  

  • Not reading camera at all

    I have an Olympus D-395 digital camera. I tried to download photos today. At first it appeared in the finder, but once in iphoto after selecting import; it just starts spinning, Nothing happened. After that one time, the computer no longer detects th

  • UnixODBC: Driver's SQLAllocHandle on SQL_HANDLE_HENV failed

    I have installed the instant client and am now getting the following error: unixODBC: Driver's SQLAllocHandle on SQL_HANDLE_HENV failed I googled a lot but could not find a solution. Could there be something wrong with my ENV variables? /etc/odbcinst

  • SCCM Office 2010 Deployment - "already compliant"?

    Hi, I am deploying Office 2010 successfully to a group of machines on our network. It looks like there are machines that state "already compliant" even though the install definetely has not gone through. I checked some of the logs no record. Also rei

  • HT201077 Shared Photo stream to iPhoto

    I have shared photo streams that I can see on my phone & iPad, but they aren't showing up in iPhoto. All of my settings appear to be correct, but I'm not seeing the individual streams, nor any photos that were shared with me.