Exchange 2013 - Unable to Delete Mailbox

When I try to delete a mailbox I get this error:
Active Directory operation failed on dc01.domain.local. This error is not retriable. Additional information: Access is denied. Active directory response: 00000005: SecErr: DSID-031520B2, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
I've ensured that "Inheritable Permissions" are checked for this user.
I noticed "Deny" permissions when I run this powershell command on the Exchange server:
[PS] C:\Windows\system32>Get-MailboxPermission -Identity jane.doe | fl
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, ReadPermission}
Deny            : False
InheritanceType : All
User            : NT AUTHORITY\SELF
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : False
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess}
Deny            : True
InheritanceType : All
User            : DOMAIN\administrator
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess}
Deny            : True
InheritanceType : All
User            : DOMAIN\Domain Admins
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess}
Deny            : True
InheritanceType : All
User            : DOMAIN\Enterprise Admins
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess}
Deny            : True
InheritanceType : All
User            : DOMAIN\Exchange Organization Administrators
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess}
Deny            : True
InheritanceType : All
User            : DOMAIN\Organization Management
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess}
Deny            : False
InheritanceType : All
User            : NT AUTHORITY\SYSTEM
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {ReadPermission}
Deny            : False
InheritanceType : All
User            : NT AUTHORITY\NETWORK SERVICE
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
Deny            : False
InheritanceType : All
User            : DOMAIN\administrator
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
Deny            : False
InheritanceType : All
User            : DOMAIN\Domain Admins
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
Deny            : False
InheritanceType : All
User            : DOMAIN\Enterprise Admins
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, ReadPermission}
Deny            : False
InheritanceType : All
User            : DOMAIN\Exchange Servers
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
Deny            : False
InheritanceType : All
User            : DOMAIN\Exchange Organization Administrators
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {ReadPermission}
Deny            : False
InheritanceType : All
User            : DOMAIN\Exchange View-Only Administrators
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {ReadPermission}
Deny            : False
InheritanceType : All
User            : DOMAIN\Exchange Public Folder Administrators
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
Deny            : False
InheritanceType : All
User            : DOMAIN\Exchange Trusted Subsystem
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {FullAccess, DeleteItem, ReadPermission, ChangePermission, ChangeOwner}
Deny            : False
InheritanceType : All
User            : DOMAIN\Organization Management
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {ReadPermission}
Deny            : False
InheritanceType : All
User            : DOMAIN\Public Folder Management
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {ReadPermission}
Deny            : False
InheritanceType : All
User            : DOMAIN\Delegated Setup
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
RunspaceId      : 2bd98ff2-251e-4b74-ade0-6cb0d81215a4
AccessRights    : {ReadPermission}
Deny            : False
InheritanceType : All
User            : DOMAIN\Managed Availability Servers
Identity        : DOMAIN.local/Accounting/Jane Doe
IsInherited     : True
IsValid         : True
ObjectState     : Unchanged
These permissions remain the same whether "Inheritable Permissions" is checked or not.
I think I'm running into a permissions issue, but I'm not sure where. A few weeks ago I messed with the permissions in AD for Exchange Servers, Exchange Trusted Subsystem, etc. This was in relation to another issue we were running into. The problem turned
out to be something else, but the permissions were left the way they were (not reverted back to the original). I feel that if I could get back to the default Exchange permissions that I'd be set. Is there a way to do that in a production environment without
breaking everything? Can I run /adprep?
Is there an easier way to get rid of those DENY's listed above? Are those even causing my problem?
Thanks in adavance.

Hi,
Thanks for your sharing.
It's great to hear the good news.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2013 OWA server accessing mailboxes on Exchange 2007

    Hi All-
    I just completed the installation of Exchange 2013, co-existing with Exchange 2007.  I have 2013 CU1 and 2007 SP3 RU10.  The issue I have is that I cannot access mailboxes existing in the 2007 mailbox servers through my 2013 OWA server.  Is
    there some advanced configuration that I need to do, on either 2007 or 2013? The documentation I have read seems to indicated that I should be able to use OWA 2013 to access 2007 mailbox.
    TIA,
    Chris

    Just the HTTP 500 error through the website.  I found this in the HTTPProxy logs:
    2013-04-30T16:17:12.093Z,100f0d73-0d2c-4bee-aa7d-54ada2c4e050,15,0,620,16,,Owa,/owa,,FBA,True,Domain\username,,Sid~xxxxxx,Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0),10.1.200.21,servername,500,,ServerNotFound,GET,,,,,WindowsIdentity,,,,0,,,,2,0,,0,,0,,0,0,0,0,,-1,0,0,3,,,,2,,,OnBeginRequest=1;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
    Unable to find proper HTTP service. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: Unable to find proper HTTP service.    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetBestBackEndServiceForVersion[ServiceType](TopologyWithSites
    topology  ClientAccessType clientAccessType  Predicate`1 versionNumberCondition)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)   
    at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox  BackEndServer
    mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1 operationToTrack  Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon
    beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass2b.<OnCalculateTargetBackEndCompleted>b__2a()    --- End of inner exception stack trace ---;

  • Exchange 2013 migrations logs deleted!

    Hi,
    I migrated mailboxes from 2010 to 2013 one domain straight forward process that went successfully. The migration reports were deleted from the 2013 ECP. Any idea how to get logs or information on "when" mailboxes were moved to the 2013 servers?
    Thank you
    Ibby667

    Hi,
    I migrated mailboxes from 2010 to 2013 one domain straight forward process that went successfully. The migration reports were deleted from the 2013 ECP. Any idea how to get logs or information on "when" mailboxes were moved to the 2013 servers?
    Thank you
    Ibby667
    You can get that information using Get-Mailboxstatistics.
    Example:
    Get-Mailbox | Get-MailboxStatistics -IncludeMoveReport | FL Displayname,MoveHistory
    UPDATE: Exchange 2013 stores by default information about the latest
    5 moves in the mailbox, so that is why you can get the information even if the migrationbatch or moverequest has been deleted (MaxMoveHistoryLength="5" in  *\bin\MsExchangeMailboxReplication.exe.config)
    Martina Miskovic
    all suggestions in here will work, however i like & believe it is best to pull the moverequeststatistics vs the mailbox statistics. 
    as listed in my reply, this will help to user determine numerous things about the move that the mailboxstatistics will not show
    I agree, but if the moverequests has been deleted (default setting: 30 days) and you want to know when a mailbox was moved, then you can with Get-Mailboxstatistics.
    Martina Miskovic

  • Users moved from Exchange 2007 to Exchange 2013 unable to access mails on the mobile devices

    New mailbox if created on Exchange 2013 works fine. But moved users from Ex2k7 to EX2k13 do not works. Here are the errors on the exchange server 2013 IIS logs:
    For android --  DevOS:Android_S110_Error:System.ArgumentOutOfRangeException_ADWR
    For iphone --   DevOS:iOS+8.1.1+12B436_S110_Error:System.ArgumentOutOfRangeException_As
    Exhange 2013 is on Cumulative update CU6
    Any clue.

    Hi,
    have you tried to recreate activesync profile?For IOS devices you could try to reset Network setting by doing the following:
    Settings
    General
    Reset
    Reset network settings
    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

  • We have a Exchange 2013 server and the Mailbox Database folder is filling up with .log files.

    We are migrating from Exchange 2010 to Exchange 2013.  We have installed the Exchange 2013 but it only has a couple of mailboxes on this server, all the mailboxes are still on the Exchange 2010 server.
    I have run a Windows Backup of the Exchange 2013 but I am still seeing a ton a log files in the mailbox folder.
    Also the database file is only about 1.1 GB but the backup is now 40 GB.  
    Is there something that can be done to truncate these logs and make the backup smaller?

    Hi ,
    1.Does the full backup completed successfully ?
    2.what about the status for the below mentioned command ? Does the mailbox database headers updated with the latest time and date ?
    Get-MailboxDatabase -Status | ft name,*full* -au
    3.Just check the application event logs for the event id
     2046  and that should state that the log truncation for the mailbox databases has been initiated or not.
    4.Before initiating the backup just make the exchange writer is not on error.
    vssadmin list writers
    In case if it on error state ,please restart the Microsoft exchange replication service and check the exchange writers status again by using the above mentioned command.
    Thanks & Regards S.Nithyanandham

  • Unity Connection 9.1.2 - MS Exchange 2013 support for Single Mailbox?

    Hello,
    we are currently running a unity connection system in version 9.1.2TT1.11900 together with single mailbox enabled with our Exchange server in version 2007.
    We are now planning to upgrade the exchange server to version 2013. From my understanding Exchange 2013 is supported with CUCN 9.1.2 (see http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/design/guide/9xcucdgx/9xcucdg020.html).
    When i go to the configuration screens I cannot choose Exchange 2013 ... Is there a special way to configure this or is 2013 not supported with Unity connection 9.1.2 ?
    any hints ?
    Michael

    Exchange 2013 is supported.
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcucumgx/9xcucumg020.html#17832
    If you choose to allow Unity Connection to search for Exchange servers, then you need to select from the following two options:
    – Exchange 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2007, Exchange 2010, and Exchange 2013.
    – Exchange 2003, 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2003, Exchange 2007, and Exchange 2010. When the Exchange organization includes Exchange 2003 servers, Unity Connection always communicates directly with the Exchange back-end servers, it never communicates with Exchange front-end servers.
    The drop down does not state 2013 but it will work fine for 2013..

  • Unable to delete mailboxes

    Hi 
    I am facing lot of issues post moving on to the new nokia belle. Unable to delete gmail  mail box...it just shows deleting but it never ends. would appreciate if any one has a solution for the same...

    Hi bhaviksparmar,
    Welcome to the Nokia forum.
    Try a hard reset and then reinstall the update after that. This should fix the issue.
    Make sure you make a back up with Nokia Suite first by going to Tools > Back up. Don't tick the Settings box as this will backup the bug that's causing this. Once you've made the backup, enter *#7370# into your phone and default security code 12345, unless you've changed this code yourself. 
    Once the phone has rebooted, reconnect it to Nokia Suite and reinstall the current software to make sure you really get rid of all possible bugs. You can do this by clicking on the green arrow in Nokia Suite. 
    After you've done the above, place the backup back onto your phoneb by going to Tools > Restore in Nokia Suite and then it should work.
    Let me know how you get on so that I can troubleshoot further, if necessary.
    Iris9290
    If my post has helped you in any way, please accept it as a solution or click on the white star, so that other users will be able to benefit from it too.

  • Exchange 2013 - Unable to recreate ECP Virtual Directory using New-EcpVirtualDirectory

    Hello,
    I had a problem accessing ECP so I decided to recreate its virtual directory on the client access server. I used Remove-EcpVirtualDirectory. The cmd completed successfully. Then I tried running New-EcpVirtualDirectory and am getting the following error:
    Argument: -Role ClientAccess
        + CategoryInfo          : InvalidArgument: (:) [New-EcpVirtualDirectory], ArgumentException
        + FullyQualifiedErrorId : 3C22AE5F,Microsoft.Exchange.Management.SystemConfigurationTasks.NewEcpVirtualDirectory
    Running the command using the -role clientaccess parameter doesn't change the outcome. I have tried running the Exchange setup using the recoverserver switch but the installator is unable to detect any problems with the installation and refuses to continue
    with the recover. Any thoughts?

    Hi,
    Unfortunately, this didn't help either, but it has resulted in a different error message which has eventually led me to an answer, so thank you very much for your help!
    The problem turned out to be quite strange (or not, I'm not very proficient with Exchange). It turned out that all the commands that I was executing, were actually applied to the mailbox server not to the CAS (hance the -role clientaccess error - it couldn't
    have been installed on a server that didn't have the role). Once, I used the -server parameter you proposed, the command failed again. The problem now was that while it was finally pointing to the right server it was still using the installation path on the
    mailbox server (SIC!). Exchange on the mailbox server has been installed at a non-default location and somehow the New-EcpVirtualDirectory command ran on CAS was trying to get to that path. So the trick that finally worked and something that Microsoft again
    doesn't include in their site was using the parameter -path as part of the command:
    new-ecpvirtualdirectory -internalurl https://xx.xx.xx/ecp -role clientaccess -server servername -websitename "Default Web Site" -Path "C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp"
    Hope it helps some poor soul some day. Thank you all for your help.

  • Exchange 2013 "Could not open mailbox Microsoft System Attendant" room mailbox

    I'm hoping someone else can help me here. I've searched google and technet and have found other people who experience this issue, but noone has seemed to have a fix.I'm doing a migration from Exchange 2007 to 2013. Everything is working great and the 2007 has now been uninstalled. I'm noticing though when creating a new room mailbox I get an error about "the mailbox was created but some properties could not be saved | cannot open mailbox /cn=Microsoft System Attendant"As the message says the mailbox is created OK, and it seems to work OK, but I still get this message every time I create a new resource. I've tried creating the resource via the EMS and that does NOT throw the error.I only have one 2013 server with one database so it is not an issue of the mailbox store hosting arbitration mailboxes being dismounted like I've seen a few...
    This topic first appeared in the Spiceworks Community

    Rock07,
    I find a related link for your reference:
    Event ID 12014 – Microsoft Exchange could not find a certificate
    http://msexchangeguru.com/2011/06/22/event12014/
    Disclaimer:
    Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
    that you completely understand the risk before retrieving any suggestions from the above link.
    More details:
    1. Run this cmdlet in Exchange management shell and copy the THUMBPRINT to a notepad:
    Get-ExchangeCertificate |FL
    2. Get-ExchangeCertificate -Thumbprint “A4530629717651BE6C4443FAC376F23412184CF3″ | New-ExchangeCertificate
    Click Yes when prompted
    3. Run Get-ExchangeCertificate |FL to get both new and old certificate Thumbprint.
    4. Enable-ExchangeCertificate -Thumbprint 3A25CDB554EF6DDF81D32C2D54873DSF7FE54F71 -Services SMTP
    Remember that this THUMBPRINT is the one for the new Certificate which we just created
    and we are enabling it for SMTP
    5. To remove old certificate, run Remove-ExchangeCertificate -Thumbprint A4530629717651BE6C4443FAC376F23412184CF3
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 (Office 365) shared mailbox not staying up to date.

    We have created a new shared folder for multiple users to access in Office 365 and were having some issues. There are a few users where this mailbox works great, but others users aren't able to see any changes that are made in the shared mailbox.
    Opening the mailbox in O365 shows all folders, emails, etc... but for some reason syncing stops working randomly after a bit of time. Removing and re-adding permissions to the mailbox does fix this issue, but that's not a feasable fix for us.
    Users can add folders to the shared mailbox, and those added folders do show up in the mailbox when opened in O365, but the changes do not push down to multiple other clients. 
    Anyone else seen this or have any info? Thanks!

    Hi,
    Are the users using Cached Exchange Mode or Online Mode? When the issue comes next time, have the user switch to the other mode and test if this helps.
    We can disable Cached Mode for Shared folders, check if this helps resolve the sync issue:
    Go to FILE -> Account Settings -> Account Settings -> Double click on the Exchange account -> More Settings -> Advanced tab -> Uncheck "Use Cached Exchange Mode", and click Apply then OK.
    In Cached Mode, it doesn't connect to Exchange Server all the time but keeps a cache of the mailbox locally to sync the local cache and mailbox according to a period, this may cause some items not sync immediately. By switching to Online Mode, it should
    be immediate.
    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.

  • How many system mailboxes should be in exchange 2013 after moving from exchange 2010?

    Hi, I am moving mailboxes from exchange 2010 to exchange 2013, I noticed that in exchange 2013, besides discovery search mailbox, there are other 5 system mailboxes.(especially, there are 2 x Microsoft Exchange system mailboxes) Please see the pic attached.
    Does this look right? thanks

    Looks perfectly fine - Why MS decided to name two of the five arbitration mailboxes the same (Microsoft Exchange) is unclear but it is what it is :)
    In EMS:
    Martina Miskovic

  • Outlook 2010 prompting for password each login to Exchange 2013

    We have a new member server w/ Windows Server 2012 and Exchange 2013.  User's mailboxes were migrated from an old Windows Server 2003 server w/ Exchange 2003 by creating new empty mailboxes in Exchange 2013 then we exported/imported
    .pst files instead of migrating exchange stores.  Every time any users opens Outlook, they are being prompted to log in with domain credentials.  Obviously I'm clicking on "Remember my password", too. The workstations are all
    using Outlook 2010 and on a mix of Windows XP SP3, Windows 7 SP1 and Windows Server 2008 R2 (terminal server with Outlook 2010 installed for remote users). Some users were using Outlook 2010 prior to the migration to Exchange 2013 and some were on Outlook
    2007 but upgraded to Outlook 2010. I'm almost to the point of telling the users it's a new "feature" of Exchange 2013.  I'm confident that it's not stored passwords or credentials on the workstations, I've removed, deleted, created and
    recreated those credentials.  I've changed domain passwords and that didn't help either.  Any hints, tips or suggestions would be greatly appreciated.

    Hi
       These settings can be found under your Outlook profile, "More Settings > Connection > Exchange Proxy Settings."
       If you have Outlook Anywhere enabled, then you should force all Outlook clients to use HTTP when connecting.  Ensure you have  "On fast networks, connect using HTTP..."  AND "On slow networks, connect using HTTP...".  If you
    don't, anytime you dock, undock, get a new IP address, refresh your IP address, go to sleep, idle, anything that causes your IP stack wants to renegotiate connective will cause a password prompt to appear, EVERYTIME.
    Terence Yu
    TechNet Community Support

  • Exchange 2013 CU7 OWA 400 Bad Request after successful login

    Scenario:
    Exchange 2007/2013 Migration
    One
    Exchange 2007 Server [removed]
    One
    Exchange 2013 Server Std, Windows 2012
    All mailboxes moved to 2013
    - November 27-30 2014
    All public folders moved to
    2013 - December 2, 2014
    Exchange
    2007 is still running and has not been removed from the domain, yet. [update]
    Exchange
    2007 removed from domain - 12-13-14
    SSL
    Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com
    Applied
    CU6 (Dec 3, 2014) to fix Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow).
    User
    logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs.
    [update]
    CU7 applied 12-11-2014
    All
    users can connect using Outlook 2013 or Mobile (iPhone & Android)
    Exchange
    Admin Center (ECP) still works!
    Browsers
    tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7
    Attempted:
    https://ex13.ExtDom.com/owa
    https://ex13.IntDom.com/owa
    https://ex13.ExtDom.com/owa?ExchClientVer=15
    https://ex13.IntDom.com/owa?ExchClientVer=15
    https://localhost/owa
    (on Ex 2013 server)
    https://localhost/owa?ExchClientVer=15
    (on Ex 2013 Server)
    Fixes
    attempted:
    remove
    | create Virtual Directories for OWA
    Change
    authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic
    reverted
    since change didn’t work.
    Run
    UpdateCas.ps1
    Run
    UpdateConfigFiles.ps1
    IISReset
    (iisReset /NoForce fails)
    OWA
    (Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. [update] Build 1044.25 (CU7)
    Links
    used for troubleshooting:
    http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp
    https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-request-when-logging-in-to-owa-exchange-2013?forum=exchangesvrclients
    http://tecfused.com/2013/09/23/exchange-2013-ecp-double-login-error-400/
    https://social.technet.microsoft.com/Forums/lync/en-US/c25ce81c-76ea-471a-93ae-eeaf9e5015ac/exchange-2013-owa-error-400-bad-request?forum=exchangesvradmin
    http://support.microsoft.com/kb/2871485/en-gb

    Hi,
    Does it work if you disable the FBA and only use the basic authentication?
    Please also let us know the authentication settings on the Default Web site.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

    We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them. 
    With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
    For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
    In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
    I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
    I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
    So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
    In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
    Questions are, Is this the right way to migrate all the users to Exchange 2013?
    Will it affect the operation of existing Exchange 2007 server?

    Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
    For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
    However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
    2013 for standardization.
    Refer article for configuring URLs -
    http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
    - Sarvesh Goel - Enterprise Messaging Administrator

  • Exchange 2013 / 2010 coexistence with different public domains

    Currently in my organization
    1x Exchange 2010 Standard w/SP3 - Client Access / Hub Transport
    1x Exchange 2010 Standard w/SP3 - Unified Messaging Server (we also have Lync 2013 in the environment)
    1x Exchange 2010 Standard w/SP3 - Mailbox
    In my organization, we have approximately 600 mailboxes - 100 office staff, and 500 field employees using a mixture of Outlook 2007/2010/2013 and various mobile devices. Most of our field employees are in remote locations, several hundred
    miles away. We have no IT staff in any of our field locations.
    We also have two public domains that we use, though we are trying to phase out the old one to unify everything.
    domain-old.com - Used when the company had a different name. All Exchange services are published with this one.
    domain-new.com - Used after the company changed names. The goal is to publish all Exchange services with this one.
    domain.local - Our internal Active Directory domain.
    We use Microsoft Exchange Online Protection for all inbound/outbound email. We publish OWA, ActiveSync, etc. through our Sophos firewall. Also, we have two KEMP LoadMaster appliances that for high availability that we currently use for Lync 2013; they are
    severely underutilized.
    Goals for the Exchange migration
    My primary goal is to introduce high availability into our environment by introducing redundancy on multiple levels. I would like to accomplish this by utilizing Exchange 2013 since we will need to purchase additional licensing anyway. My idea of the
    final topology is:
    2x KEMP LoadMaster appliances providing reverse proxy and load balancing to the CAS servers
    2x Physical servers running Hyper-V, separated physically but in the same AD site. Each one would run:
    1x VM with Exchange 2013 Standard w/SP1 - Client Access
    1x VM with Exchange 2013 Enterprise w/SP1 - Mailbox - Utilizing DAGs for high-availability
    I'd like all the new Exchange services to be published under the domain-new.com domain - such as mail.domain-new.com, mail.domain-new.com/owa, smtp.domain-new.com, etc.
    We have purchased two new physical servers that will be Hyper-V hosts running Server 2012R2. My timeframe to start this project is within the next two weeks, so I'll be running the new Exchange 2013 VMs under Server 2012, not R2 as it won't be supported
    until Exchange 2013 SP3 is released.
    Deployment Plan
    Install Exchange 2013 on new VMs.
    Create CAS Array object.
    Configure Exchange 2013 to publish under the new namespace.
    Perform mailbox moves to 2013 for a small group (1-5 users) at a time. Recreate Outlook profiles and mobile device profiles for that group. Test and move to the next group.
    Once all users are moved to the new namespace, decommission the Exchange 2010 servers.
    Unknowns
    My primary unknown is about the namespaces. All of the guides I have read strictly deal with keeping the existing namespace and having the Exchange 2013 CAS proxy requests to Exchange 2010 for mailboxes still on 2010. This should never be an issue for us
    since we'll be using the new domain for each mailbox we move.
    My question boils down to, is this a supported way to migrate to Exchange 2013? And if so, are there some materials or information to help me perform it this way?

    Hi,
    From the description, you want to install Exchange 2013 in another domain and then migrate from Exchange 2010 to Exchange 2013. 
    About DAG, all servers in a DAG must be running the same operating system. If there is only one mailbox server, there is no need to deploy DAG.
    About CAS array, we should know that the CAS Array no longer exists in Exchange 2013.
    About the namespace, based on my knowledge, we can introduce a new namespace. Just as what you said "This should never be an issue for us since we'll be using the new domain for each mailbox we move".
    Here are some articles about how to upgrade from Exchange 2010 to Exchange 2013 in the same organization.
    Checklist: Upgrade from Exchange 2010
    Install Exchange 2013 in an Existing Exchange 2010 Organization
    Upgrade from Exchange 2010 to Exchange 2013
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

Maybe you are looking for