Exchange 2013 category view always in "expand all" mode

Hi all,
having issues with mailboxes that have been migrated to Exchange 2013.If in category view and choose collapse all,then expand just a few,go to another folder/inbox then back all categories are expanded.Seems like Outlook (2010 and 2013) doesnt remember it.
Checked in view settings - group by - expand/collapse default is set to As last viewed.
This happens to all mailboxes exept those mailboxes that are on Exchange 2010.
Exchange 2010 sp3 cu6 had an update that fixes categoryview not updated,but cant find any for Exchange 2013.
Since the update is on server,i guess this can be changed on serverside settings in Exchange 2013?
Our workaround atm is to ask users to open additional mailbox in new window,but this doesnt work well for users with 1 screen.
Are there any fix for this?
Thanks.
Please 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. Thank you! Off2work

Hi,
There is no related category view settings in Exchange server side. I also have tested in my Outlook 2010 and Outlook 2013 with two test accounts: one for Exchange 2010 SP3 account and one for Exchange 2013 CU1 account.
Both these two accouns are working fine in . I set my Inbox folder in category view and collapse all colors except one expanded. I go to other folders(Deleted Items folder and Drafts) then go back to Inbox folder, the view is the same as last viewed without
expanding all colors. However, if I restart Outlook, the colors would be all expanded in Inbox folder.
Please make sure your Outlook is the latest version and start Outlook by running Outlook /cleanviews to restore default Outlook view to have a try.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

  • Outlook 2013 Category view not updating after Exchange 2010 SP3 RU3

    After updating to Exchange 2010 SP3 RU3 last night, users who use categories view in Outlook 2013 are complaining that the view does not update. The alert is received in the notification area and the unread message count next to Inbox updates appropriately.
    The view can be force updated by switching between All and Unread, by using Reset View, or closing and opening Outlook.  It seems anything that forces a 'redraw' of the view will update it - except for the actual reception of email.  I easily replicated
    this issue.  For reference:
    Exchange 2010 SP3 RU3
    Windows 7 x64 Ent
    Outlook 2013 (15.0.4551.1004) 32-bit
    I do see that SP3 RU4 has been released, however the only change listed is a security patch.
    Thank you for any ideas.

    Hi, Everyone –
    This has been a known issue for a very long time – we have people at our workplace that are very disappointed since a feature as great as categorizing email (not using tasks) has become broken and has not even been considered to be fixed for
    over half a year.  It was not fixed in the updates for Patch Tuesday this week.
    I would like to confirm that this is an issue with Outlook 2010 and 2013 when running the latest Exchange 2010 and there is NO FIX
    – I have scoured the internet for a solution – all proposed "textbook" solutions do not work and I am positive that the issue can be recreated; however, everyone from Microsoft does not mention trying to recreate the issue at all. 
    The workaround of creating a rule to send new emails to a category could break other pre-existing rules and cause more frustration and wasted time for users/IT before and after the issue is fixed.
    Please fix this issue sooner than later, as the Categories view is completely broken and unusable at this point in time.
    Regards,
    IT Helper

  • Exchange 2013 Give domain Admin access to all users inbox

    In the old 2007 exchange server we had domain admin access to everyones mailbox so we could open anyones email box using outlook client.
    But in 2013 exchange the mailbox delegation does not give us the option to add a "group" to the full access area, old allows to add a "user" who has a mailbox setup in exchange. I see there is Exchange Server group listed under Full Access
    , but it does not work added our domain Admin user to that group rebooted exchange and the test machine but did not work.
    Only option that works to allow mounting of xyz users mailbox via abc admin user is to actually add that abc admin user to the xyz mailbox under mailbox delegation > Full Access.
    Is  there a work around this, so we can simply have a group ABCD with user ABC or DEF etc. etc. so they can access everyones mailbox instead of going in and changing all users mailbox delegation one by one for the new user etc. ?

    Have you tried using the Exchange Management Shell?
    Get-Mailbox | Add-MailboxPermission -User Name_of_Group -AccessRights FullAccess -InheritanceType All
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    I did i tried get-mailboxpermission and other than NT Authority and the end user the Deny was set to True for all inheritance rights. I tried your command, added user to the group i wanted under Enterprise OU in AD and restarted transport on exchange and
    logged in on the test machine again.
    Still no go, the user I am trying to add when using get-mailboxpermission shows up as Denied for fullaccess so is that overriding the group permissions ?
    RunspaceId      : 2xxxxxxx0
    AccessRights    : {FullAccess}
    Deny            : True
    InheritanceType : All
    User            : domain\abc
    Identity        : domain/Users/xyzuser
    IsInherited     : False
    IsValid         : True
    ObjectState     : Unchanged
    And for the group i just added with the above abc user inside it:
    RunspaceId      : 2xxxxxxxxx0
    AccessRights    : {FullAccess}
    Deny            : False
    InheritanceType : All
    User            : domain\newgroupadded
    Identity        : domain/Users/xyzuser
    IsInherited     : False
    IsValid         : True
    ObjectState     : Unchanged
    So is the users deny is causing this ? Not really sure why ABC domain admin/enterprise admin is the only one listed as no deny, there are other mailbox users that do not show up, I am assuming I have to create a new user a domain local user and that might
    work ? I wanted the Domain/Enterprise Manager/admin to have access so we would not have to keep toggling between users just to access someones inbox.
    Also further down the list of mailboxpermission i see the user abc (the user i want to add to the group to have access) is listed with Full access and Deny flag is set to False instead of True.
    So have two entries for user abc one with deny flag set to true and one with deny flag to false.
    AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
    Deny            : False
    InheritanceType : All

  • CoreTable always in "Show All" mode

    Hi,
    I have a ADF table with selection set to "tableSelectMany", it is also boud to a CoreTable Component in the backing bean. In the setMyCoreTable method in the backing bean I manually pre-select certain rows. It all works fine, but, first time the page loads, the table displays all records(Show All), I want it to display only its range size(which is set to 10 in the page def). The drop down to select (Show All, 1-10 of 30, 11-20 of 30...) is hidden. The range and the drop down are displayed when I add a row to the table programmatically.
    Can someone help?
    Thanks

    Hi,
    you should be able to use EL to reference a keyset in a managed bean. If this has initialization logic in it then you can make this happen.
    Frank

  • Exchange 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation

    Hi,
    We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
    onto them. This all went fine and the servers are running stable.
    We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
    OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
    order.
    After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
    server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
    I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
    Exchange Health service has killed WININIT which causes the crash.
    Thanks!!!
    The crash dump text is below:
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa80192ebb30, Terminating object
    Arg3: fffffa80192ebe10, Process image file name
    Arg4: fffff80001dc37b0, Explanatory message (ascii)
    Debugging Details:
    PROCESS_OBJECT: fffffa80192ebb30
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME:  MSExchangeHMWo
    BUGCHECK_STR:  0xF4_MSExchangeHMWo
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80001e4cab2 to fffff80001abebc0
    STACK_TEXT:  
    fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
    fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
    fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
    fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
    fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  wininit.exe
    FAILURE_BUCKET_ID:  X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
    BUCKET_ID:  X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
    Followup: MachineOwner

    Hi Darrkon,
    I suggest checking the status of the HealthMailbox on each of servers.
    Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
    Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted.  Once that service is restarted, it will recreate any mailboxes that it needs. 
    More details in the following similar thread, just for your reference:
    BSOD after creating DAG
    http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • BSOD after upgrading to exchange 2013 SP1

    Hi,
    I Have 4 servers, x2 Mailbox and x2 CAS, all with 2008 r2 OS, Mailboxes with DAG. Problem started after I upgraded all servers from Exchange 2013 CU3 to Ex13 SP1. All Servers are in Vmware, same hardware.
    All servers getting BSOD, error is same as some other posts in Internet about:
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8007ab4890, Terminating object
    Arg3: fffffa8007ab4b70, Process image file name
    Arg4: fffff800019de7b0, Explanatory message (ascii)
    Debugging Details:
    PROCESS_OBJECT: fffffa8007ab4890
    IMAGE_NAME:  wininit.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    MODULE_NAME: wininit
    FAULTING_MODULE: 0000000000000000
    PROCESS_NAME:  MSExchangeHMWo
    BUGCHECK_STR:  0xF4_MSExchangeHMWo
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    LAST_CONTROL_TRANSFER:  from fffff80001a67ab2 to fffff800016d9bc0
    LOGS:
    RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityServerReboot: Throttling rejected the operation
    RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityConfigDCServerReboot: Throttling
    rejected the operation
    Recovery Action Failed. (ActionId=RestartService, ResourceName=ServerName.contoso.com, Requester=ActiveDirectoryConnectivityRestart,
    InstanceId=140408.062707.65292.001, ActualStartTime=2014-04-08T15:27:07.6529270Z, ActualEndTime=2014-04-08T15:27:07.7777262Z, ErrorMessage=Service ServerName.contoso.com was not found on computer '.'.)
    when Server restarts, logs show 
    Bugcheck action reported by server 'ServerName' initiated by responder 'ActiveDirectoryConnectivityServerReboot'
    Recovery Action Started. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ExpectedToFinishAt=2014-04-08T15:38:07.9326175Z
    Recovery Action Succeeded. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ActualStartTime=2014-04-08T15:33:07.9326175Z, ActualEndTime=2014-04-08T15:35:07.0828500Z)
    I found that it could restart like many times in a day, but
    Throttling does not let it, just one restart per day.
    I already spent four days trying to find problem but no luck.
    Try'ed to add override
    Add-GlobalMonitoringOverride
    -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
    but
    after 
    (Get-WinEvent
    -LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot"} | ft name,enabled
    still shows propertyValue 1, and servers are restarting no matter what, I just dont want to disable HealtManager
    Service.
    Try'ed to recreate all performance counters, did'nt worked
    Try'ed to create prefered domain controller, did'nt worked
    Try'ed to play with healthSet 'AD', but there is almost no information about it in TechNet, so I just looked which services are unhealthy, sometimes it shows ActiveDirectoryConnectivityServer
    or ActiveDirectoryConnectivityConfigDCServer as unhealthy, but after few minutes it goes to
    healthy, problem that Exchange could already restart the server
    mainly reason I think is: 
    The AD Health Set has detected a problem with Server.contoso.com at 2014.04.09 06:33:11. The Health Manager is reporting that ActiveDirectoryConnectivityProbe/Server.contoso.com
    Failed with Error message:  Search took 1518 ms. Threshold 800 ms. Attempts to auto-recover from this condition have failed and requires Administrator attention. Exception Details: System.Exception:  Search took 1518 ms. Threshold 800 ms
    I really need some new ideas...
    EDIT: Exchange 2013 sp1 works perfectly in test lab, there are  cloned machines from production, the only difference is DomainController, there is just one (server), no replications, and no subdomains (production domain have subdomain). 
    Running DCDiag shows no errors

    Hello Everyone,
    We have 2 CAS and 4 Mailbox server that were installed from SP1 and seeing the same issue.  This is a clean install still with no mailboxes migrated over as of yet.  Opened a case with MS.  also ran:
    Add-GlobalMonitoringOverride
    -Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot  -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
    Waiting
    for MS to get back and to see how this workaround does.  Seems like the original issue was not resolved completely?
    Will
    post back when we get an update.  Changing the DirectoryActiveMonitoringContext.xml and the above workaround do not seem suitable for us.  We would like to see a complete resolution for this.
    Good
    luck!

  • Exchange 2010 - Exchange 2013 permanent coexsistence to avoid migration of Public Folders

    Hi Guys,
    I was hoping to get some opinions/ advices regarding the case explained below.
    The company I work for has a medium-sized Exchange 2010 infrastructure that consists of several geographically dispersed 2-node DAGs and corresponding CASArrays. It hosts about 1000 mailboxes in total and large public folder database that is replicated on
    every mailbox server in the environment. All users are using Outlook 2010/2013.
    There is a business drive to perform migration to Exchange 2013. However, migration of the Public Folders is not feasible because of the lack of multimaster replication, the complicated migration process and several other limitations in Ex2013 PFs.
    To work around this issue while still performing the migration I am considering the following scenario:
    Deploy Exchange 2013 servers in the organization
    Migrate all mailboxes to Exchange 2013 servers
    Don't ever start migration of Public Folders (leave one Exchange 2010 mailbox server in every location for hosting the Public Folder database)
    Keep the coexistence permanently (with mailboxes on 2013 and public folders on 2010)
    What do you think of this setup? Do you see any issues with such long-term coexistence?
    Thanks.

    Hi,
    You can leave the public folders on Exchange 2010 if you can’t migrate them to Exchange 2013. Exchange 2013 users can access public folders on Exchange 2010, but Exchange 2010 users can’t access public folders on Exchange 2013.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Expand All Mail Conversations by Default

    There are quite a few threads out there on this topic but none with any suitable response.  Has anyone figured out a terminal command that might force this, sort of like we do for forcing font size?  Its frustrating to have to keep going to view and selecting "Expand All Conversations" manually evertime you switch views. 
    Looking forward to a response. 

    That checkbox is checked, I have to go to View/Expand All Conversations about 20-30 times a day to expand all messages because it continues to collapse whenever I "switch views" meaning, going from one folder, to a keyword search, to a smart folder, etc.  It would be great to have some command line "defaults...xxxxx" that sets the "Expand All Conversations" default to on rather than persistent off - even if selected from the menu. 
    It would appear that I'm not the only one frustrated by this, many others seem to have the same thoughts so I'm hoping that someone in this community have figured out that simply setting a command line in Terminal sets the default to on with a bit flip. 
    leroydouglas wrote:
    Mail>preferences>Viewing
    This doesn't work for you?
    JimN wrote:
    evertime you switch views. 
    What does this mean?

  • Exchange 2013 CU6 = LastLoggedOnUserAccount is empty

    Hello,
    i'm looking to find the "LastLoggedOnUserAccount" for some mailboxes. On Exchange 2010 we could check this like that:
    Get-MailboxStatistics MAILBOX |select LastLoggedOnUserAccount
    => On Exchange 2013 the Value is empty for all mailboxes...
    any ideas?
    Best,
    Martin

    below forum will answer your question.
    https://social.technet.microsoft.com/Forums/exchange/en-US/0b3ca6f6-abe9-473f-b354-e86c01fd596c/lastloggedonuseraccount-in-exchange-onlineexchange-2013?forum=exchangesvradmin
    Regards
    John

  • OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

    Hi,
    I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
    We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
    All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
    url) also redirects me to https://legacy.domain.com/owa just fine.
    HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
    Anyone any tips where to search?
    Many thanks in advance.
    Best regards and many thanks in advance, Eric Vegter

    This seems to be an outstanding issue.
    We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
    migration of our mailboxes from the 2007 DB to the 2013 DB.
    In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
    Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
    "Use the following link to open this mailbox with optimal performance:
    http://mail.domainname.com/"
    After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
    -Lorne

  • Remove Exchange 2007 from an Exchange 2013 coexistence.

    Hey everyone,
    I've just installed Exchange 2013 on a new server and all is working great.  It is currently in coexistence with our old Exchange 2007 server.  I've since shut the server down and Exchange 2013 has been working without issue.  However, I haven't
    been able to find any articles on this matter so I figured I would ask the question here.
    How do you remove Exchange 2007 from the coexistence.  Do I just uninstall Exchange 2007 from the old server and it will remove itself from the server and the domain?  Any help/link on this matter would be greatly appreciated.
    Thank you,
    Chris

    Hi Simon,
    I am about to do the same exercise as Chris,  I just would like some clarity.  
    1) When you say mailbox Database, do you mean make sure there are no more mailboxes that you want to move over, or are you actually meaning delete the physical DB on the exchange 2007 server.
    2) If there is no use of public folders does anything need to happen?
    Thanks,
    Terry

  • Exchange 2013 & Exchange 2007 Coexsistance

    We are in the process of migration from Exchange 2007 & Exchange 2013. Question is after decommision all last Exchange 2007 servers, if i want to restore mailbox data from 2007 database will i be able to install new Exchange 2007 server and perform restore.
    Question: Is it possible to install Exchange 2003 or 2007 in a pure Exchange 2010 organization?
    Answer: If this is an Exchange 2010 greenfield environment (an Exchange organization that consists only of Exchange 2010 servers and never had previous versions of Exchange deployed), the answer is no.If
    you have transitioned from Exchange 2007 to Exchange 2010 and the last Exchange 2007 server has already been decommissioned, the answer is again no. You will not be able to install Exchange 2007 at a later time in this organization because
    it’s now considered a pure Exchange 2010 organization.
    Please suggest, what all possible conditions I CANNOT INSTALL NEW EXCHANGE 2007 in my organization later.

    Hello,
    You're right. I'm afraid that there is no way to install pervious exchange version in exchange 2010/2013 organization.
    You can try Ed's suggestion.
    I don't know why you want to restore mailbox data from 2007 database.
    Cara Chen
    TechNet Community Support

  • Exchange 2013 SP 1 + Lync 2013 CAS servers 100% CPU Load.

    Hello. Can somebody explain about one issue?
    We have Exchange 2013 CU6 + Lync 2013 (5.0.8308.556) integration.  After install Exchange SP1 all Client Access Servers begun to consume all CPU time.  In process
    explorer there are w3wp.exe (MSExchangeServicesAppPool) and lsass.exe (netlogon context). In IIS logs a lot of events about
    GET /EWS/Exchange.asmx/s/GetUserPhoto email=[email protected]&size=HR648x648&CorrelationID=<empty>;&cafeReqId=07966a0b-99a4-4f0a-8a38-a8a83264e46c; 443 - 10.10.10.10 OC/15.0.4659.1001+(Microsoft+Lync) - 401 1 2148074254 46
    GET /EWS/Exchange.asmx/s/GetUserPhoto email=[email protected]&size=HR648x648&CorrelationID=<empty>;&cafeReqId=c7fb9499-1dc7-48d9-add6-64156a910de6; 443 Contoso\username 10.10.10.10 OC/15.0.4659.1001+(Microsoft+Lync) - 200 0 0 437
    IIS logs are grow up very quickly, about 1GB per day. Before to installing SP1 was not problems.  Thanks in advance.

    Hi,
    From your description, you said that you have Exchange 2013 CU6 + Lync 2013 (5.0.8308.556) integration, then you install Exchange 2013 SP1 on all CAS servers.
    Do you mean your Exchange 2013 Mailbox server is CU6, and all CAS servers are SP1?
    We had better have the same version on Exchange servers in our environment, if that is the case, please upgrate all to CU6, Exchange 2013 latest version, to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013, clients prompting for password

    Exchange 2013 SP1 on Server 2012 R2 both fully patched. Exchange 2013 is a single server will all roles installed. There is also an Exchange 2007 (fully pathed) as we are in the process of migrating the users.
    Setup legay.company.com points to Exchange 2007 and mail.company.com point to Exchange 2013
    Security on Exchange 2013 set to NTLM for External and Internal. 
    Mobile access works for user on Exchange 2013 and Exchange 2007
    Client with Mailbox's on Exchange 2013 using Outlook 2010 - 2013 internally and externally getting prompted for username and password.
    Clients with Mailbox's on Exchange 2007 ok.
    Checked IIS, autodiscover, EWS and Kernal mode is set. 
    Nothing showing in the Event Logs.

    Hi Skynite,
    I have met this issue before, I recommend you try the following method and check the result:
    In this situation, you must set LmCompatibilityLevel on the client to a value of 2. To do this, follow these steps.
    Click Start, click Run, type
    regedit in the Open box, and then press ENTER.<u5:p></u5:p>
    Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\
    In the pane on the right side, double-click lmcompatibilitylevel.<u5:p></u5:p>
    In the Value data box, type a value of 2 and then click
    OK.<u5:p></u5:p>
    Exit Registry Editor.<u5:p></u5:p>
    Restart your computer.<u5:p></u5:p>
    More details about this Key, please refer to the following link:
    http://technet.microsoft.com/en-us/library/cc960646.aspx 
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Windows XP Machines Always Prompt for Credentials (Exchange 2013, Outlook 2010)

    I am running Exchange 2013 on Server 2012 Datacenter (VM).  Windows 7 clients with Outlook 2010 work fine.  Windows XP clients with Outlook 2010 prompt for credentials (user name and password) each time Outlook is started, and checking the "Remember
    my password" box does not prevent this from happening the next time.  The "Always prompt for logon credentials" checkbox on the "Security" tab of the "More Settings" section of the Exchange account is not checked.  I have found a myriad of posts
    with similar issues, but they all seem to have to do with SBS/Exchange 2007, and I haven't come across something that works as a solution for me.  One suggested certificate issues, and I was having certificate security warnings, but I got that resolved. 
    I am hopefuly that the fact that this only happens on Windows XP will be telling.

    Proxy settings:
    auth_param ntlm program /usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
    auth_param ntlm children 50
    auth_param ntlm keep_alive on
    auth_param basic program /usr/lib/squid3/squid_ldap_auth -R \
    -b "DC=domain,DC=local" \
    -D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" \
    -W passldap \
    -f "sAMAccountName=%s" \
    -h domain.local
    auth_param basic children 20
    auth_param basic realm Domain Internet Proxy
    auth_param basic credentialsttl 8 hours
    external_acl_type ADS children=50 ipv4 ttl=60 %LOGIN /usr/lib/squid3/squid_ldap_group -S -K -b "DC=domain,DC=local" -f "(&(objectclass=person)(sAMAccountName=%v)(memberof =CN=%a,OU=Domain,DC=domain,DC=local))" -D "CN=Squid Proxy,OU=TI,OU=Domain,DC=domain,DC=local" -s sub -W ldappass domain.local
    tks.

Maybe you are looking for