Single item recovery in Exchange 2013

I am looking for some help in identifying the simplest process to recover a single item in Exchange 2013 in a scenario where the item is no longer available in the dumpster (i.e. a retained deleted item).
In Exchange 2010 the process was:
Restore the mailbox database from backup to the Recovery database
Restore the item using the Restore-Mailbox cmdlet with the -AllContentKeywords parameter to identify and restore the individual item (or items) to a target folder in the user's mailbox.
The Restore-Mailbox cmdlet is no longer available in Exchange 2013. 
I guess one possible option is the following:
Restore the mailbox database from backup to the Recovery database
Restore the mailbox to a dummy mailbox (or Discovery Mailbox) using New-MailboxRestoreRequest.
Use the Search-Mailbox cmdlet to find the item in the dummy mailbox and restore it to a target folder in the user's mailbox.
It just seems like a very long-winded method to restore a single item. Any way to do this better?
Alexei

Hi ,
In exchange 2013 single item recovery work as follows .
Scenario 1 : Items from the deleted items folder and also the hard deleted items (shift + delete) will move it to the dumpster (i.e deletions folder) which is an sub-folder in recoverable deleted items folder.On that deletions folder items will be retained
based upon retention period .
Scenario 2 : In case if we move the items from the deletions folder it will get move in to the purges folder (if single item recovery is enabled) .purges folder is also one more sub folder for recoverable deleted items folder .
In purges folder items will be again started to get retain for the whole retention period (I mean to say retention period count will not get calculated from the day when it moves from the deletions folder to purges) instead again that particular email item
start to get retained till the whole retention period get's over .
You can use  mfcmapi tool and e-discovery search in exchange 2013 to recover the items which is moved from deletions folder to purges folder.
Reference blog : http://www.msexchange.org/articles-tutorials/exchange-server-2010/high-availability-recovery/single-item-recovery-part1.html
For an additional information litigation and In place hold is one of the feature in exchange which will retain emails for the years that you want .
http://blogs.technet.com/b/exchange/archive/2013/12/11/litigation-hold-and-in-place-hold-in-exchange-2013-and-exchange-online.aspx
Note : from 2010 on wards single item recovery feature is available.
http://blogs.technet.com/b/exchange/archive/2009/09/25/3408389.aspx
Regards
S.Nithyanandham

Similar Messages

  • Exchange 2013 - Public Folder Mailbox and Single Item Recovery

    Hello,
    I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
    "Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
    is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
    looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

    So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder. 
    Check out this article
    http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
    I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB  but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward.  That said this will also increase the
    DB size so consider all the options before implementing
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Exchange Online Archive and Single Item recovery

    We are currently looking to implement online archiving in Exchange 2010.
    From my perspective,  we are doing it to relocate the older messages to some cheaper storage,  while making primary mailbox sizes are little more manageable.
    Management however,  want to ensure that once an item is moved to the online archive that it cannot be permanently deleted until after a 7 year retention period (for discovery purposes).
    Journaling isn't an option at this point..
    We have an Archive RPT which moves the items to the users archive after 90 days.
    We have another RPT which will Delete items from the Archive after 7 years (Delete no Recovery).
    We then have "Keep deleted Items for", set to 30 Days on the Primary Mailbox Database.
    and then have "Keep deleted Items for", set to 7 years (2555 Days) on the Archive Database(this is so that items are not immediately deleted if the user manually deletes from the archive).
    Obviously with this setup,  users will be able to purge items from the "Deletions" sub folder (Recover Deleted Items) if they want to remove it from the archive.
    My understanding is that if I enable Single Item Recovery for everyone,  then the items that the user might remove from the "Deletions" sub folder will be transparently moved to the "Purges" sub folder, and are therefore discoverable
    if required,  up until the retention period of each database (30 days for Primary mailbox, 7 years for archive).
    This sounds like exactly what we are after.
    Thus my questions;
    Apart from the obvious storage implications of doing this (7 years is alot of email),  are there any other issues\risks associated with going down this method for email retention?
    Is there a better way of achieving what we are after?  I dont suppose we could completely restrict deletion access to the users archive completely for example?
    If a user was to drag an item back into their primary mailbox.. and then delete it before the Managed Folder Assistant moved it back to the archive..  Would that be a potential hole in the retention requirement?
    Thanking you all in advance for your insight..

    You may want to use Litigation Hold to have users unable to delete the item permanently.
    http://blogs.technet.com/b/exchange/archive/2011/08/16/retention-hold-and-litigation-hold-in-exchange-2010.aspx
    I know it works on Active mailbox but not sure if the same attributes available for Archive Database. Just run the cmdlet and see if it can be done.
    Where Technology Meets Talent

  • Enable single item recovery with two retention settings at the database level.

    Hello All,
    We have an Exchange 2010 SP3 RU4 environment and planning on moving from third party archives solution to Native Exchange archives for cost reduction purposes, upgrading to Exchange 2013 to benefit from added in place features is not within scope at
    this stage.
    We are looking at implementing the following steps and want to know if it will work:
    1-Create archive DB(s) as per our usage and growth projections
    2-Enable archives for all our users and migrate current archive content to it.
    3-Create Retention Tag/Policy to move all records from live to archive "Age limit for retention" 90 days (no retention tags on the policy)
    4-Enable Single Item recovery for all of our users (script the same to run twice daily to enable SIR for newly created accounts)
    5-Set the "Keep Deleted Items" on the Live DB(s) to 90 days and the Archive DB(s) to 7 Years
    6-We are NOT using Legal Hold or plan to use it except on per as need basis
    Are we accomplishing the following:
    1-Items are automatically archived after 90 days
    2-Items archived now have a 7year retention based on the "keep deleted items" set for the archive DB(s)
    3-Items copied back to the live mailbox by a user will be returned to the archive database the next time the folder assistant runs against this user account (based on load or if run manually)
    4-Hard deleted items by a user is recoverable as long as the email record is within the retention period set at the database where it resides.
    5-Hard deleted items are recoverable using MFCMapi or by a restore.
    6-Items are permanently purged on the archive DB(s) after 7 years.
    Any input, ideas, recommendations, clarifications would be greatly valued and appreciated.  
    Ash

    Thanks CodexCZ,
    So, SIR will "kind of" do the same as the retention tag except I can use different durations based on the limits on each DB? am I correct?
    thanks again.
    Ash

  • Litigation Hold, Single Item Recovery, & Mailbox Database Deleted Items Retention

    Hello
    I'm looking for a simple explanation of how the three features mentioned in the subject line interact and affect one another.
    Specifically, I'm after the answer to the following question:
    If a users mailbox has litigation hold enabled, and the mailbox database it lives on has a deleted items retention value of 365 days, does that users "Recoverable Items" get deleted after 365 days, or does litigation hold, as I supspect bypass the retention
    value?
    If Single Item Recovery is enabled for said user as well, and added to the scenario above - how does this affect the retention of the deleted items?
    I cannot find a definitive article that describes mailbox database deleted items retention, litigation hold and single item recovery and their behaviours when used together.
    Regards
    Matt
    Matt

    Hello again,
    Just wanted to open this thread up again, and gain some further clarification, specifically on the behaviour of items in "Recoverable Items\ Deletions" folder.
    In the following scenario how will items be processed:
    -SingleItemRecoveryEnabled -True
    -LitigationHoldEnabled - True
    -UseDatabaseRetentionDefaults -True
    -Items in the Deletions folder have passed the retention value date as specified on the database.
    Given the parameters above, when the I run the Managed Folder Assistant against a mailbox, I'm expecting to see the items in the Deletions folder move, and be placed in Purges folder.
    This is not happening however, items are only removed from the Deletions folder when LitigationHold is disabled. Then, items bypass the Purges folder altogether and are removed from the mailbox/database altogether.
    I referred to the article below for clarification:
    http://blogs.technet.com/b/exchange/archive/2009/09/25/3408389.aspx#_Short-Term_Preservation_of
    "...the message was not purged from the mailbox store. Instead the message was moved from the Recoverable
    Items\Deletions folder to the Recoverable Items\Purges folder. All store hard-deleted items end up in this folder when single item recovery is enabled. The Recoverable Items\Purges folder is not visible to the end user, meaning that they do not see data retained
    in this folder in the Recover Deleted Items tool.
    When the message deletion timestamp has exceeded the deleted item retention window, Records Management will purge the item."
    Can anyone assist in explaining the behaviour I'm observing?
    I'm in a transition period where by our organisation has been journalling all
    email to an Online service since 2008 and this service will continue to be used solely as our archiving and compliance mechanism.
    Since Exchange 2010 was adopted by the company around 18 months ago, the previous mail administrator had litigation hold enabled on all mailboxes
    from the outset, so I'm in the position now where by I have two retention methods running side by side.
    Long story short, the online archiving will be used moving forward and litigation hold will be disabled within Exchange. 
    What I want to do is transition from long term data
    preservation inside Exchange, to short term preservation - hence the reason for now enabling SIR.
    Currently I have mailboxes with 10's of GB's of mail sat in the "Recoverable Items\Deletions" folder, and very little, if anything in some
    cases, in the respective "Purges" folder.....
    Can anyone advise on a "correct" procedure for making this transition?
    Regards
    Matt
    Matt

  • Enabling Single Item Recovery per databse

    Hello,
    I am trying to find a command that will set "Single Item Recovery" to be true for all mailboxes in a database. I know how to set it for a single mailbox but I can't seem to find the correct syntax to make it work for each mailbox in a particuliar database.
    This is what I have come up with so far but it tries to set it on all mailboxes in all databases:
    [PS] C:\Get-Mailbox | Where{$_.Database -eq servername\databasename} | Set-Mailbox -SingleItemRecoveryEnabled $true
    Also, is there a way to set it as the default for all new mailboxes created in a database?
    TIA.
    Mark

    Addition to what Jonas said :)
    For a scheduled script you can use the same command as you already did: Get-Mailbox -Server
    servername| Set-Mailbox -SingleItemRecoveryEnabled $true. If you run that command once every night you would have to wait no more then one day before the new users have the correct settings.
    And if you want to make it a bit more complex you can add a where function and the command will only configure the mailboxes that has been created in the last 24h: Get-Mailbox -Server
    servername | Where { $_.WhenCreated -gt (get-date).adddays(-1) } | Set-Mailbox -SingleItemRecoveryEnabled $true
    Martin Sundström | Microsoft Certified Trainer | MCITP: Enterprise Messaging Administrator 2007/2010 |
    http://msundis.wordpress.com

  • Single Item Recovery:versions

    In Exchange 2013, after running Set-Mailbox Lousy -SingleItemRecoveryEnabled $true, I edit a message in OUTLOOK 2013. The versions subfolder under RecoveableItems folder is still empty. 
    In Exchange 2010, after running Set-Mailbox Lousy -SingleItemRecoveryEnabled $true, I edit a message in OUTLOOK 2013. The versions subfolder under RecoveableItems folder will have one item.
    In Exchange 2013, after placing a mailbox in-hold, I edit a message in OUTLOOK 2013. The DiscoveryHolds folder will have one more item but not versions subfolder.
    Thanks,
    Kaiming

    Thank you Allen and Shweta for your response.
    Sorry for not being clearer earlier. Below are the current settings for the user.
    I have already enabled SingleItemRecovery for the user and checking the 'versions' folder using Get-MailboxFolderStatistics cmdlet and MFCMAPI tool.
    What I want is to get the versions folder count\size to increase, how can I get that tested.
    Please  guide me through the steps to make edits on the email items to make this happen. 
    User details below:
    [PS] C:\>get-mailbox testuser1 | fl *Sing*,*retain*
    SingleItemRecoveryEnabled : True
    RetainDeletedItemsUntilBackup : False
    RetainDeletedItemsFor : 14.00:00:00
    [PS] C:\>Get-MailboxFolderStatistics -Identity testuser1 -FolderScope RecoverableItems | ft Name,FolderPath,FolderandSubfolderSize,ItemsInfolderAndSubfolders -auto
    Name FolderPath FolderAndSubfolderSize ItemsInFolderAndSubfolders
    Recoverable Items /Recoverable Items 598.9 KB (613,312 bytes) 46
    Calendar Logging /Calendar Logging 0 B (0 bytes) 0
    Deletions /Deletions 389.1 KB (398,446 bytes) 28
    Purges /Purges 209.8 KB (214,866 bytes) 18
    Versions /Versions 0 B (0 bytes) 0
    The Versions folder stays empty irrespective of edits(saves) I make on emails located in Inbox, Deleted Items or elsewhere.
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • How to make disable/enable single item recovery effectively Immediately?

    for the following command , "it may take up to one hour to disable single item recovery",my question is how to make the disable/enable  single item recovery
    effectively Immediately by some command?
    SingleItemRecoveryEnabled $false/true
    http://technet.microsoft.com/en-us/library/ff678798(v=exchg.141).aspx
    Please click the Mark as Answer button if a post solves your problem!

    other options:
    Move the mailbox to another DB or if in a DAG, activate the DB on another server. ( the activating seems to work as far as I have seen at least).
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

    Hi,
    I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
    I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
    I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
    Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
    Thank you!

    Hi,
    It is possible to open a shared mailboxes on a legacy server.
    Your problem could be caused by:
    Not having one of the later CU installed (read CU4 or CU5)
    Incorrect authentication methods configured (see link below)
    Outlook is not at the latest patch level
    Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
    http://support.microsoft.com/kb/2834139
    Martina Miskovic

  • What happened to the sent items configuration in Exchange 2013?

    Why is Set-MailboxSentItemsConfiguration
    removed from Exchange 2013? It was a really useful feature... Does anyone know if it will reappear? I know I can make a gpo and roll out the DelegateSentitemsStyle but I prefer using the setting in Exchange.

    Hi,
    The feature is removed from Exchange 2013, currently, there is no official document about when this feature will be re-introduced again.
    As a workaround, we can edit it via registry.
    1) Click Start, click Run, type regedit, and then click OK.
    2) Locate and then click the following registry subkey:
    HKEY_CURRENT_USER\Software\Microsoft\Office\Version\Outlook\Preferences
    Note: the version depend on which version of Outlook we are using. Outlook 2010 is version 14, Outlook 2013 is version 15.
    3) On the Edit menu, point to New, and then click DWORD Value.
    4) Type DelegateSentItemsStyle, and then press ENTER.
    5) Right-click DelegateSentItemsStyle, and then click Modify.
    6) In the Value data box, type 1, and then click OK.
    7) Exit Registry Editor.
    We should note that only the cached mode will work fine with this workaround. The DelegateSentItemsStyle registry value will not work consistently on an Exchange account that is configured in Online mode.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Multiple owa sites on a single server 2012 with exchange 2013 (mailbox, cas)

    hi,
    I'm trying to
    set up an exchange server 2013 on windows 2012 with all roles installed for 2 owa virtual directory, one for integrated windows authentication and the other for forms-based authentication.
    I followed a tutorial for exchange 2010.
    http://technicaljeditrials.info/2011/02/28/exchange-2010-multiple-owaecp-directories-part-1/
    Step 1: IP Address
    Obtain a second IP address and add it to the NIC of your server.
    Step 2: DNS
    Add a DNS entry for That secondary IP address for the name we will want to use in the new FBA OWA Web site.
    I have chosen "testwebmail."
    Be sure there is a valid SSL certificate (recommended to have UC or SAN
    SSL certs) on the server Which has the new name "testwebmail" that will be used in the certificate.
    Step 3: New Web Site
    Create a new web site in IIS on the Client Access Server and bind it to the new IP address used in step 1.
    Step 4: Adding Exchange Virtual Directories
    The web site has been created and bound to the secondary IP address of our server.
    Also the DNS record That will be used to access the OWA FBA new page was added to DNS.
    The next step is to go into EMS and begin adding our virtual directories for OWA and ECP.
    Login to the Exchange server and open the Exchange Management Shell.
    Then run Get-Get-OWAVirtualDirectory and ECPVirtualDirectory to see the default OWA and ECP directories.
    New-OWAVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/owa
    New-ECPVirtualDirectory -WebSiteName FBA -InternalUrl https://testwebmail.mylab.ad/ecp
    Step 5: Configure the Virtual Directories
    To configure the virtual directories we will disable FBA on the Default Web Site OWA and ECP virtual directories
    Set-OWAVirtualDirectory -Identity "OWA (Default Web Site)" -WindowsAuthentication
    $true -BasicAuthentication $false  -FormsBasedAuthentication $false
    Set-ECPVirtualDirectory -Identity "ECP (Default Web Site)"
    -WindowsAuthentication $true -BasicAuthentication $false  -FormsBasedAuthentication
    $false
    Step 6: iisreset
    now if I access the default site I log in with
    windows integrated authentication, but when I try to access the second site with forms authentication tells me username or password incorrect
    Tell me you know where I'm wrong?
    thanks
    Greetings
    Daniele

    Hello,
    Something like this:
    New-OWAVirtualDirectory -WebSiteName "FBA"
    Enable the Basic authentication via running the following command:
    Set-OWAVirtualDirectory -Identity "yourservername\owa (FBA)" -BasicAuthentication $true
    Restart the IIS admin service in services.msc
    Thanks,
    Simon Wu
    TechNet Community Support

  • Exchange 2013 Recoverable Items\Versions folder stays empty

    Hi All,
    I need some clarifications on Recoverable Items Folder.
    Versions: If either litigation hold or single item recovery is enabled and If a user modifies an item, a copy of the original item is placed in the Recoverable Items\Versions folder, by a process called copy-on-write page protection. This
    folder isn’t visible to end users. (Visible via MFCMAPI though)
    I don’t seem to be practically achieve this with Single Item Recovery Enabled.
    The Versions folder stays empty irrespective of edits(saves) I make on emails located in Inbox, Deleted Items or elsewhere.
    I would really appreciate some light here on how to get this going.
    NOTE:- Deletions and Purges folder are working just fine.
    Regards,
    Satyajit
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

    Thank you Allen and Shweta for your response.
    Sorry for not being clearer earlier. Below are the current settings for the user.
    I have already enabled SingleItemRecovery for the user and checking the 'versions' folder using Get-MailboxFolderStatistics cmdlet and MFCMAPI tool.
    What I want is to get the versions folder count\size to increase, how can I get that tested.
    Please  guide me through the steps to make edits on the email items to make this happen. 
    User details below:
    [PS] C:\>get-mailbox testuser1 | fl *Sing*,*retain*
    SingleItemRecoveryEnabled : True
    RetainDeletedItemsUntilBackup : False
    RetainDeletedItemsFor : 14.00:00:00
    [PS] C:\>Get-MailboxFolderStatistics -Identity testuser1 -FolderScope RecoverableItems | ft Name,FolderPath,FolderandSubfolderSize,ItemsInfolderAndSubfolders -auto
    Name FolderPath FolderAndSubfolderSize ItemsInFolderAndSubfolders
    Recoverable Items /Recoverable Items 598.9 KB (613,312 bytes) 46
    Calendar Logging /Calendar Logging 0 B (0 bytes) 0
    Deletions /Deletions 389.1 KB (398,446 bytes) 28
    Purges /Purges 209.8 KB (214,866 bytes) 18
    Versions /Versions 0 B (0 bytes) 0
    The Versions folder stays empty irrespective of edits(saves) I make on emails located in Inbox, Deleted Items or elsewhere.
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • What is the best backup plan for Archive Databases in Exchange 2013?

    Hi,
    We have Exchange 2013 with Hybrid setup with O365.
    We have On premise exchange 2013 servers with 3 copies of primary Database & Single Copy of Archival DBs.
    Now we have to frame backup policy with Symantec Backup Exec which has to backup our primary & Archival DBs
    In 2007 exchange, before migration to 2013, we had policy of DBs - Weekly Full backup & Monthly Full Backup
    Please suggest what would be the best possible backup strategy we can follow with 2013 DBs.
    That too, especially for Archiving DBs
    Our Archiving Policy are - 3 category - Any emails older than 6 month OR 1 Year OR 2 Year should go to Archive mailbox.
    Keeping this in mind how to design the backup policy ? 
    Manju Gowda

    Hi Manju,
    you do not find best practice different from the common backup guidelines, as there is no archive db specific behaviour. Your users may move items to their archive at any time as well as your retention policies may move items that machted the retention policies
    at any time. The result is frequently changing content to both, mailbox and archive mailbox databases, so you need to backup both the same way. You also may handle archives together with mailboxes together in the mailbox db 
    Please keep in mind that backup usually means data availability in case of system failure. So you may consider to do a less frequent backup with your archive db with dependency to the "keep deleted items" (/mailboxes) setting on your mailbox database.
    Example:
    keep deleted items: 30 days
    backup of archive db: every 14 days
    restore procedure:
    * restore archive DB content
    * add difference from recover deleted items (or Backup Exec single item recovery) for the missing 14 days.
    So it depends more on your process than on a backup principle.
    Regards,
    Martin

  • IBM Domino to Exchange 2013 Migration question

    I've been tasked with looking into migrating our company of 5500+ Domino users to Exchange 2013.  Currently, my Domino servers spread across the county and not all in one location.  Is there a document/guide that can help me get an understanding
    on what type of environment I can take my hub/spoke Domino environment to in Exchange?  Any guidance would be appreciated. Thanks!

    hi Hoss,
    I have done couple of Migrations from Domino to Exchange Migrations and pretty familiar with this. For this to happen, you have to use a third party tool like Quest or Binary Tree.
    Since you said, 5500+ users, I would recommend you using one of the quest or binary tree tools to assist you with this migration. The key to the migration is the design and planning phase.
    I am familiar with Quest tools and will give you as much as i know but I am sure every other tool out there is pretty similar in terms of functionality.
    you have to purchase Quest licenses and for quest to be installed on your server, you have to go through Quest Professional services or a Quest approved vendor. You cannot install Quest on your own - this is a small drawback that I personally think.
    While your Quest servers are being setup, you have to plan out your Exchange server design and for a 6000 user mailbox, you wont have a big of a deal. I need the hardware information that you have purchased for the Exchange servers? are you going
    to go physical or virtual? I need to know the user message profile in your existing domino environment (how many emails sent/recived /size per day/per mailbox)? I also need your inputs on how many servers are you planning with Exchange 2013 in total (all roles),
    Do you need single item recovery? Do you have any storage contrains? and a 100+ questions. If you get me the answers for what I asked, I am willing to help you with the design fo Exchange 2013.
    Re: Domino:
    What version of domino are you running? What is your max mail file size? how many mailboxes (person documents) how many mail-in databases? how is your user account provisioning currently designed? and so on. user account provisioning could be a challenge
    because you have to introduce a 3rd party app like FIM or CA's User Management apps to work between your Domino and Exchange (during the time of coexistence) and there is a lot to it.
    All the best!
    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, Siva

  • Exchange 2013 - Archive RESTRICTION

    Hello All my Exchange MS Expert, 
    I have a customer requirement --> My customer want to restrict all user in their organization not to delete archive item from their archived mailbox? can we achieve this through security
    option / from ADSI edit??? I have suggested them to go with inplace-hold but not wanted in-pace feature instead they need if a user want to delete any archived item they should get message saying "you don't have appropriate" permission
    / unable to delete.
    I have open a Microsoft advisory Case: they told me to give some time to work on this requirement for test and will comeback to me.
    Friends if you have any suggestion pls pass me. Much appreciate your valuable input.

    Hello All my Exchange MS Expert, 
    I have a customer requirement --> My customer want to restrict all user in their organization not to delete archive item from their archived mailbox? can we achieve this through security
    option / from ADSI edit??? I have suggested them to go with inplace-hold but not wanted in-pace feature instead they need if a user want to delete any archived item they should get message saying "you don't have appropriate" permission
    / unable to delete.
    I have open a Microsoft advisory Case: they told me to give some time to work on this requirement for test and will comeback to me.
    Friends if you have any suggestion pls pass me. Much appreciate your valuable input.
    Exchange doesn't work that way. Using litigation hold/ Single Item Recovery is the only supported method.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Maybe you are looking for