Exchange 2013 CU3 - Retention policy/ hold

Dear friends..
i have a requirement where client is asking that they dont want their end users to delete any mails. and if in case they delete any mails this should not be deleted from the server and can be retrieved at will.. i want to understand how we can achieve this
knowing that there is no time defined... secondly if a user from outlook deletes the mails .. as for the managers in that company, how they can see what mails are deleted and how they can recover it.. i understand there is this legal hold feature is there..
but i want to understand best practices and things i need to care for in this kind of requirement. 
Thanks
Happiness Always
Jatin

Hi,
I suggest setup a journaling mailbox.
Journaling
http://technet.microsoft.com/en-us/library/aa998649(v=exchg.150).aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

  • Exchange 2013 CU3 Retention Policy Not working for Calendar & Tasks

    We are currently on Exchange 2013 CU3 with Online Archiving Enabled for the user
    Default policy is set to move  all the items in mailbox which are  older than 30 days to online archive mailbox.
    Calendar and Tasks Items are also getting archived alongwith other Outlook items from Inbox,Deleted Items etc
    Followed Technet website and created RPT for Calendar and Tasks with retention disabled
    Still DPT takes precedence and move all the items under Calendar and Task to Online Archive Mailbox

    Hi Sam,
    I recommend you refer to the following article, despite this for Exchange 2010, however the same applies to exhcnage 2013:
    Prevent archiving of items in a default folder in Exchange 2010
    To prevent the <acronym title="Default Policy Tag">DPT</acronym> from being applied to a default folder, you can create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for that folder (or disable
    any existing RPT for that folder). The Managed Folder Assistant, a mailbox assistant that processes mailbox items and applies retention policies, does not apply the
    retention action of a disabled tag. Since the item/folder still has a tag, it's not considered untagged and the DPT isn't applied to it.
    Why are items in the Notes folder still archived?
    If you create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for the
    Notes folder, you'll see items in that folder are not deleted, but they do continue to be moved to the archive! Why does this happen? How do you prevent it?
    It's important to understand that:
    A retention policy can have a <acronym title="Default Policy Tag">DPT</acronym> to
    archive items (using the Move to Archive retention action) and a DPT to
    delete items (using the Delete and Allow Recovery or
    Permanently Delete retention actions). Both apply to untagged items.
    The move and delete actions are exclusive of each other. Mailbox folders and messages can have both types of tags applied - an archive tag and a delete tag. It's not an either/or proposition.
    If you create a disabled RPT for the Notes folder to not delete items, the archive DPT for the mailbox would still apply and move items.
    When it comes to archiving, there's only one archive policy that administrators can enforce – the <acronym title="Default Policy Tag">DPT</acronym> with 'Move to archive' action.
    You can't create a <acronym title="Retention Policy Tag">RPT</acronym> with the 'Move to archive' action. This rules out using the disabled RPT approach to prevent items from being moved.
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 CU3 Databases only activate on one mailbox server

    Hi, guys
    I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will  be activated on the mailbox
    server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
    From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
    Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
    This caused the database activated on another server.
    And I got the message from SCOM, like this:
    Alert: Health Set unhealthy
    Source: test-mbx - Outlook.Protocol
    Path: test-mbx.contoso.local;test-mbx.contoso.local
    Last modified by: System
    Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
    Latency: 00:00:00.0320000
    ActivityContext:
    Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
    Details:
    Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
    Log:     Mailbox logon verification
            EMSMDB.Connect()
            Task produced output:
            - TaskStarted = 11/12/2013
    5:15:25 AM
            - TaskFinished = 11/12/2013
    5:15:25 AM
            - ErrorDetails =
            - RespondingRpcClientAccessServerVersion
    = 15.0.712.4012
    Latency = 00:00:00.0303884
            - ActivityContext =
        EMSMDB.Connect() completed successfully.
            EMSMDB.DoRpc(Logon)
            Task produced output:
            - TaskStarted = 11/12/2013
    5:15:25 AM
            - TaskFinished = 11/12/2013
    5:15:25 AM
            - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
    Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
            - ErrorDetails =
            - Latency = 00:00:00.0018801
            - ActivityContext =
        EMSMDB.DoRpc(Logon) failed.
        Task produced output:
        - TaskStarted = 11/12/2013 5:15:25 AM
        - TaskFinished = 11/12/2013 5:15:25 AM
        - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
    Error
    States of all monitors within the health set:
    Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
    State               Name                                   
    TargetResource                     HealthSet                    
    AlertValue     ServerComponent    
    NotApplicable       OutlookMapiHttpDeepTestMonitor                                            
    Outlook.Protocol              Unhealthy      None               
    NotApplicable       OutlookRpcDeepTestMonitor                                                 
    Outlook.Protocol              Healthy        None               
    NotApplicable       OutlookRpcSelfTestMonitor                                                 
    Outlook.Protocol              Healthy        None               
    NotApplicable       OutlookMapiHttpSelfTestMonitor                                             Outlook.Protocol             
    Healthy        None               
    NotApplicable       PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy       
    None               
    NotApplicable       PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy       
    None               
    NotApplicable       ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy       
    None               
    NotApplicable       ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy       
    None               
    NotApplicable       ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy       
    None               
    NotApplicable       LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy       
    None               
    NotApplicable       LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy       
    None                
    This test is a cause that mailbox databases in DAG is doing  failover to another server
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          12.11.2013 4:49:46
    Event ID:      3169
    Task Category: Service
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      test-mbx-2
    Description:
    (Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchangeRepl" />
        <EventID Qualifiers="16388">3169</EventID>
        <Level>4</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
        <EventRecordID>1606248</EventRecordID>
        <Channel>Application</Channel>
        <Computer>test-mbx-2.contoso.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>DB-01</Data>
        <Data>test-mbx.contoso.local</Data>
        <Data>test-mbx-1.contoso.local</Data>
        <Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
      </EventData>
    </Event>
    I don't know why, anyone know what's the problem?
    Thank you.
    Nile Jiang- Please mark the post as answer if it answers your question.
    http://www.usefulshare.com

    Hi,
    After deleting all the health mailboxes and restart
    the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
    [PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
    rtvalue -AutoSize
    Server   state Name                                              AlertValue
    MAILBOX1       OutlookRpcDeepTestMonitor                            Healthy
    MAILBOX1       OutlookMapiHttpDeepTestMonitor                     Unhealthy
    MAILBOX1       OutlookRpcSelfTestMonitor                            Healthy
    MAILBOX1       OutlookMapiHttpSelfTestMonitor                       Healthy
    MAILBOX1       PrivateWorkingSetWarning....cclientaccess.service    Healthy
    MAILBOX1       PrivateWorkingSetError....rpcclientaccess.service    Healthy
    MAILBOX1       ProcessProcessorTimeWarning....ientaccess.service    Healthy
    MAILBOX1       ProcessProcessorTimeError....clientaccess.service    Healthy
    MAILBOX1       ExchangeCrashEventError....pcclientaccess.service    Healthy
    MAILBOX1       LongRunningWatsonWarning....cclientaccess.service    Healthy
    MAILBOX1       LongRunningWerMgrWarning....cclientaccess.service    Healthy
    Nile Jiang- Please mark the post as answer if it answers your question.
    http://www.usefulshare.com

  • 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

  • Exchange 2013 CU3 - Outlook Web App LogOff

    Hello All,
    I have Exchange 2013 CU3 installed and i'm using TMG server for authentication. I am able to login through OWA but when i try to logoff it shows me message of "Close All your Browser Windows.." but OWA does not sign out. 
    On TMG, only Basic and NTLM authentication is supported. And in IIS Authentication for the OWA Virtual Directory is set to basic.
    Can anyone please help me for TMG settings for exchange server 2013? Thankyou for the answers.

    Hi,
    Thank you for your patience and support.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Best Regards
    Quan Gu

  • Exchange 2013 CU3 - Problem with Retention Policies

    Hello, I configured a retention policy for mailbox and assigned it to the mailbox iwth the set-mailbox cmdled. I issued the Start-ManagedFolderAssitant [mailbox] to force the immediate processing for the mailbox but the maibox items are not moved.
    The ManagedFolderWorkCycle is set to 1 day so i waited 24 hours but no effect.
    I also noticed that connecting through OWA the tab Retention Policies does not appear.
    Am i missing something? Hope someione could help.
    Thnaks

    Hi, and thank you for your help. No I did not set the personal tag in the retention policy.
    Now I added a personal tag but still i can't see the tags available in the right-click menu. The starnge thing is i see the default MRM policy tags instead. I found Event ID 9017 and 9018 but no errors are reported.
    Best regards,
    Raffaele
    Hi,
    Did you have a personal tag in this retention policy and assign it to the mailbox?
    Only when you add a personal tag to retention policy and apply to user mailbox, you can see the Retention Policy option by right-clicking the message items in OWA.
    For this issue, I recommend you check whether there is the Event ID 9017 and 9018 in the application log, make sure the MRM works well.
    And please check if you can see the retention policy description in the Reading Pane when you click on the message items.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 CU3 Fails "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception."

    I can't get Exchange 2013 to install in our Server 2008 R2 infrastructure. Setup fails with the following error when preparing AD. This is running on Server 2008 R2 SP1 VM's.
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    FAILED
         The following error was generated when "$error.Clear();
            install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
    ainController $RoleDomainController
    " was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

    I have set the PowerShell Execution Policy to unrestricted. After running setup /PS I get the following output
    PS C:\Windows\system32> cd c:\temp\ex2013cu3
    PS C:\temp\ex2013cu3> ./setup /ps /iacceptexchangeserverlicenseterms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Extending Active Directory schema                                                                
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation completed successfully.
    PS C:\temp\ex2013cu3>
    The installation was started at 10:13am and hung for sometime at 94% of the prereq stage. Installation finally completed at 10:47am. The errors seem to indicate that setup will continue. However upon running setup /prepareAD the installation hangs for sometime
    at 21% of Organization Preparation before finally failing with the following output....
    PS C:\temp\ex2013cu3> ./setup /prepareAD /iacceptexchangeserverlicenseterms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    FAILED
         The following error was generated when "$error.Clear();
            install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
    ainController $RoleDomainController
    " was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS C:\temp\ex2013cu3>

  • Exchange 2013 CU3 and Firefox 26.0

    I upgraded Exchange 2013 to CU3 last night.  I tested the mail flow and everything worked fine sending and recieving.  The problem that I am having is with OWA in firefox 26.0 (currently newest version).  I get weird graphical glitches when
    OWA first loads.  Once you click around the display stabilizes but the biggest problem is that not all of the emails are displayed in a folder.  I have a folder with a bunch of system data emails that are collected throughout the day and in firefox
    I can see ~20 while in IE 9 I can see them all.  The inbox also has 5 emails in it but there is a scroll bar that is completely unnecessary in firefox but not IE 9.  Do you have any thoughts on this?  Thank you in advance.

    There's no way, as there's nothing wrong with the server.
    You will have to wait for the update from Firefox to get it fixed.
    It's purely Browser issue As I said before.
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    www.exchangeranger.com 
    Twitter:   
    LinkedIn:   
    Check out CodeTwo’s tools for Exchange admins   
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 CU3 Can't Access ECP from Office365 Enabled Account

    We recently upgraded our Exchange 2013 server to CU3 to fix the OWA redirection error. Unfortunately, we've now noticed that any admin mailboxes that have been 'moved' to Office365 can not access ECP and instead get a redirect warning to OWA.
    I had to create a new, onprem admin account to access in the meantime.  This is the message I see:
    Use the following link to open this mailbox with the best performance:
    http://outlook.com/owa/ACME.onmicrosoft.com
    X-FEServer: EXCHANGE
    Date: 12/3/2013 6:13:23 PM
    more detail...
    I assume this is due to the fix for OWA redirection?  How do I manage Exchange with my 'oncloud' mailbox accounts?

    Hi,
    I think it will be more suitable to ask this question on Exchange Online forum:
    http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • The Microsoft Exchange Administrator has made a change that requires you to Quit and restart outlook in Exchange 2013 CU3

    I have a Exchange 2013, That has been running for a few months now since we moved it over, but now I get the Microsoft Outlook Message "The Microsoft Exchange Administrator has made a change that requires you to quit and restart Outlook." It only
    shows up on certain users but not on others. What could be the problem? The only answers I have seen are for Exchange 2010.
    All Help is much appreciated

    This one? http://support.microsoft.com/kb/2934750

  • Installation Error Installing Exchange 2013 CU3 on Server 2012

    Hello,
    When Installing Exchange 2013 on server 2012 I get the following error during Step 1 of 8 of Transport Service. I have installed and unistalled Exchange a few times, restarted the machine manually and removed exchange from AD, etc. to no avail.
    Any suggestions will be very much appreciated.
    Thank You.
    VK
    Error:
    The following error was generated when "$error.Clear();
              install-MsiPackage `
              -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASDat.MSI") `
              -LogFile ($RoleSetupLoggingPath + "\InstallASDat.msilog") `
              -PropertyValues ("ALLUSERS=1") `
              -UpdatesDir $RoleUpdatesDir
            " was run: "Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. This action is only valid for products that are currently installed. Error
    code is 1605.".

    Martina,
    Thank you for your response. KB says that Machinepolicy and Userpolicy are to be set to Undefined and that is what I have.
    Windows PowerShell
    Copyright (C) 2013 Microsoft Corporation. All rights reserved.
    PS C:\Users\Administrator> get-executionpolicy –list
    Scope                                            
    ExecutionPolicy
    MachinePolicy                                                  
    Undefined
    UserPolicy                                                  
    Undefined
    Process                                                  
    Undefined
    CurrentUser                                                  
    Undefined
    LocalMachine                                               
    RemoteSigned
    VK

  • Exchange 2010 SP3 - retention policy fails to expire any messages that existed in Deleted Items prior to implementing retention policy

    I created retention policies that are working as expected for Inbox, Sent and Drafts folders. However, I created a similar policy for Deleted Items: (New-RetentionPolicyTag “test-DeletedItems-Retention” –Type DeletedItems –Comment “Items older than
    90 days are deleted” –RetentionEnabled $true –AgeLimitForRetention 90 –RetentionAction PermanentlyDelete). The messages that existed in the Deleted Items folder prior to implementing the policy do not appear to have any retention policy applied to them, so
    it appears that they will retain in Deleted Items indefinitely.
    Please advise.
    Sincerely
    Derek Bain

    Will,
    Please see the results below. The output is similar for the 3 other tags that I created for Inbox, Sent, and Drafts.
    Sincerely
    Derek
    [PS] C:\scripts>Get-RetentionPolicyTag "test-DeletedItems-Retention" | Fl
    RunspaceId                      : 3d1ea5eb-30e7-4dcf-8f65-8dcac9bbefe1
    MessageClassDisplayName         : All Mailbox Content
    MessageClass                    : *
    Description                     : Managed Content Settings
    RetentionEnabled                : True
    RetentionAction                 : PermanentlyDelete
    AgeLimitForRetention            : 90.00:00:00
    MoveToDestinationFolder         :
    TriggerForRetention             : WhenDelivered
    MessageFormatForJournaling      : UseTnef
    JournalingEnabled               : False
    AddressForJournaling            :
    LabelForJournaling              :
    Type                            : DeletedItems
    SystemTag                       : False
    LocalizedRetentionPolicyTagName : {}
    Comment                         : Items older than 90 days are deleted
    RetentionId                     : ead62b76-f54e-4981-b177-e3e24d0793a4
    LocalizedComment                : {}
    MustDisplayCommentEnabled       : False
    LegacyManagedFolder             :
    AdminDisplayName                :
    ExchangeVersion                 : 1.0 (0.0.0.0)
    Name                            : test-DeletedItems-Retention
    DistinguishedName               : CN=test-DeletedItems-Retention,CN=Retention Policy Tag Container,CN=XXXXXXXXXXXXXXXX
                                      DC=com
    Identity                        : test-DeletedItems-Retention
    Guid                            : ead62b76-f54e-4981-b177-e3e24d0793a4
    ObjectCategory                  : XXXXXXXXXXXXX/Configuration/Schema/ms-Exch-ELC-Folder
    ObjectClass                     : {top, msExchELCFolder}
    WhenChanged                     : 4/3/2014 8:49:44 AM
    WhenCreated                     : 4/3/2014 8:49:44 AM
    WhenChangedUTC                  : 4/3/2014 12:49:44 PM
    WhenCreatedUTC                  : 4/3/2014 12:49:44 PM
    OrganizationId                  :
    OriginatingServer               : XXXXXXXXXXXXX
    IsValid                         : True

  • Exchange 2013 cu3 setup fails with 'problem... validating the state of Active Directory... supplied credential... invalid'

    Windows Server 2013; Exchange Server 2013 with Cumulative Update 1
    Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with
    [xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.  See the Exchange setup log for more information on this error.
    [xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
    [xxx] [0] [ERROR] The supplied credential is invalid.
    (Crosses - XXX - replace original values.)
    I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely
    conincidental:
    The Security System could not establish a secured connection with the server
    ldap/xxx.xxx/[email protected] No authentication protocol was available.
    Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

    Hi vhr1,
    Based on my knowledge, the Event ID 40961 is a warning message.
    This behavior occurs when we restart the server that was promoted to a DC. The Windows Time service tries to authenticate before Directory Services has started.
    Found some resources for your reference even if the Exchange Version is mismatched:
    http://blogs.technet.com/b/jhoward/archive/2005/04/20/403946.aspx
    http://support.microsoft.com/kb/823712/en-us
    About the error message, "Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid."
    The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.
    Found a similar thread for your reference, hope it is helpful:
    http://social.technet.microsoft.com/Forums/en-US/98e26ad6-8e43-4ef5-8ff9-e9fee6e76bda/bind-operation-is-invalid?forum=exchangesvrdeploylegacy
    Feel free to contact me if there is any problem.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 CU3 Can't view permissions on mailbox in EAC

    Recently upgraded to CU3.  I'm not sure if my EAC problems are due to that or something else.  I could have swore this worked before, but I am not 100% positive.
    If I go to "Recipients > Mailboxes > Properties on a mailbox > Mailbox Delegation" it says "Please wait...".  It stays like that for about 15-20 seconds, then finally comes back with:  "error.  Your request
    couldn't be completed.  Please try again in a few minutes".  I hit OK and the boxes for Send As, Send on Behalf, and Full Access are all empty.
    I can view permissions on that same mailbox with PowerShell.
    Also, if I do the same process for a Distribution Group, then that works okay in EAC!

    Hi
    Almost the same problem here...
    Editing a Resorce Room...
    Request for URL 'https://InternalServerName:444/ecp/UsersGroups/EditRoomMailbox.aspx?pwmcid=8&ReturnObjectType=1&id=21b9ba56-12cf-4138-ba3d-9de2342f28b2(https://LoadBalancedExternalName/UsersGroups/EditRoomMailbox.aspx?pwmcid=8&ReturnObjectType=1&id=21b9ba56-12cf-4138-ba3d-9de2342f28b2)'
    failed with the following error:
    System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException:
    Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Data.Directory.Recipient.NonUniqueRecipientException: Multiple objects with Sid S-1-5-32-548 were found.
    Did you fix it?
    Regards
    Robban

  • Exchange 2010 users cant change password in OWA when Cas server is Exchange 2013 cu3

    Running Exchange 2010 and 2013 in mixed mode.  users who is still on Exchange 2010 cant change password in OWA. It worked when it was clean Exchange 2010 installation. Password change is working for users migrated to 2013
    LS

    Hi
    Please follow the below blog which will help you in solving this issue
    http://technet.microsoft.com/en-us/library/bb684904.aspx
    Note: Be careful while modifying the registry 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.
    Regards,
    Sathish

Maybe you are looking for