Looking for a util to identify "abandoned" mailboxes in Exchange 2007

I am looking for a (hopefully free or inexpensive) tool to identify mailboxes that are no longer in use and candidates to be pulled and archived.  My exchange admins have not been able to find anything, so I am posting here in case one of you folks
might have run accross something.  The exchange environment is 2007 SP2.  One fact that might be an issue is that our desktops and user accounts are not in the same AD as the Exchange environment.  Overtime I am sure that we have had many accounts
removed from the desktop domain, without taking care of the equivalent account in the Exchange domain.

What I do is use PowerGUI (Free from Quest) and run a Powershell command.  I use Get-Mailbox with the option "Sort-Object
-property
'WhenChanged"
and sort
the results by date.  This way your using when the last time the mailbox was used.
Good luck
To build on SG_Dan's post, this command works for me in 2010:
Get-mailbox | Select Name, Whencreated, Whenchanged | Sort Whenchanged | Export-CSV c:\InactiveMailboxes.csv
This will give u all mailboxes in your environment and show you the user, when the mailbox was created and when changed. It will sort by when changed and outputs it to a csv file for you to look at.

Similar Messages

  • Looking for a Utility to map error code to error message

    Hi All
    I am looking for a utility that would map my error codes to corresponding error messages. If you know there such a utility, please point me to it. In addition, I am looking for a utility that would validates input -- eg. length, range of input. Thanks.

    In addition, I am looking for a utility that would validates input -- eg. length, range of input. Whatever you do, don't use asserts for this.

  • Looking for a way to turn Push off with Exchange

    I am looking for away to turn push OFF with an Exchange email account. Since I added it I have started going over my data plan limits. I just want it to featch emails every 30min or so. This seems simple enough but Exchange email accounts do not seem to allow you to turn off Push for the inbox. So far I have tried the things listed below. The Gmail accounts work fine and check for mail every 30 min, but the Exchange account is still getting mail pushed from the inbox immediately.
    o I turned off Push option in Settings > "Mail, Contacts, Calendars" > "Fetch New Data".
    o I Set the fetch option to 30 min in "Settings" > "Mail, Contacts, Calendars" > "Fetch New Data".
    o I found that the checked setting for Inbox in "Settings" > "Mail, Contacts, Calendars" > "<Selected The Exchange acct>" > "Mail Folders to Push" > is grayed out and can not be unchecked.
    iPhone: 3Gs
    Version: 4.1 (8B117)
    Firmware: 05.14.02

    Exchange by definition is a Push service. the whole point of it is to keep the two systems in sync.
    You could speak to your provider and ask them to provide a POP3 service.

  • Recreation of user mailbox from exchange 2007 to Exchange 2013

    In my domain I was using Exchange 2007 earlier. I have installed Exchange 2013 successfully and running perfectly. I have one Issue:
    1. A user's mailbox in Exchange 2007 was disabled from Exchange 2007 and recreated on Exchange 2013.
    When a user try to send mail from outlook be it old one(2007) or new exchange(2013), gets NDR
    If user send via owa it get delivered.
    2. External mails are coming and user can send also like gmail or yahoo.
    This is not an issue of cached address (outlook) I have checked this possibility.
    Any luck
    Deepak Vashistha
    Deepak Vashistha Network Admin. Mayo College Ajmer

    Hi,
    From your description, OWA works well, the issue is related to Outlook side. In your case, I recommend you update the Address Book manually on Outlook and check the result. If the issue persists, you need to re-create the profile.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Looking for Sync utility like Beyond Compare

    I'm looking for a folder/file synchronization utility like Beyond Compare (which is a Windows-only product). Beyond Compare has a few features that make it outstanding. I know of no Mac synchronization utilitiy that has all of these features:
    1) You can set up compare sessions with individual preferences for each.
    2) The individual preferences includes a list of file/directory names to be ignored.
    3) You can perform a compare and have it display the differences.
    4) I can dispatch file/folder moves individually and instantly.
    5) It can display differences of files (binary or text).
    The 4th item is key. While I'm displaying differences, I only see the differences. It could be dozens or hundreds or thousands of files and folders. If I conclude that folder97 needs to be sync'd to the right, I select the command from a pop-up menu and it syncs to the right and disappears off of my display as it is no longer a difference. As I go through the differences one by one, they disappear off of my screen. This goes on until I have resolved all of the differences.
    Beyond Compare is extremely powerful, flexible and intuitive. It should be a Mac app. I just wish there were something on the Mac like it.

    There is actually. It's called chronosync:
    http://www.econtechnologies.com/pages/cs/chrono_overview.html
    it does everything you listed.

  • 3rd party tool for online EDB repair & live mailbox move - Exchange 2007

    Please advise a 3rd party tool, a reliable one that can do live mailbox migrations in Exchange 2007 from a corrupted DB to a new fresh DB?
    Also a tool that can do live repair of the DB.
    The corrupted DB is mounted but users are facing many issues and the application logs are throwing the below error:
    MSExchangeIS (920) DB001: Database F:\Exchange Server\Mailbox\DB001.edb: Index FidDeleteTimeIndex of table IndexAge is corrupted (0). 
    An error occurred on database "DB001\DB001". Function name or description of problem: Restrict/SetSearchCriteria Error: -1414 Warning: fail to apply search optimization to folder (FID 4-DBC987)   Retrying without optimization. 

    Hi,
    As additional, the reason for this Event ID is that this message is logged when the Query Processor (QP) tries to use an index to perform a query optimization but, at the same time, that index was updated by a concurrent transaction. In this situation the
    QP will just abandon the optimized path and revert to the default search algorithm.
    Basis on my research and knowledge, this warning is not indicative of a serious problem and can be ignored. Response he warning can be safely ignored, but for preventive measures it is recommended To run Isinteg -s <server name> -fix -test alltest
    on the store where we are getting these warnings. More details about Isinteg, for your reference:
    https://technet.microsoft.com/en-us/library/bb125144%28v=exchg.80%29.aspx?f=255&MSPPError=-2147217396
    Note: We recommend that you should back up your Exchange mailbox database before you run the tool.
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Allen Wang
    TechNet Community Support

  • Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

    Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
    I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
    "Could not find a valid mailbox migration for this organization"
    Do you know that you can be?
    regards
    Microsoft Certified IT Professional Server Administrator

    Hi,
    From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
    Migration.8f3e7716-2011-43e4-96b1-aba62d229136
    If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
    Hope this can be helpful to you.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Amy Wang
    TechNet Community Support

  • Using Recovery Storage Group to recover a single mailbox in Exchange 2007 CCR

    Hi, there:
    Our Environment: Exchange 2007(SP3) CCR
    Now we got a task to recover a mailbox which is still on Exchange 2007 now(but it is suspected the owner deleted many emails before he left and these deleted items is NOT recoveralble through dumpster). They want to recover this mailbox to a point
    of time where they believe these email items is not deleted at that time.
    By reserach below is the steps which can be porformed:
    1): Create a RSG and a mailbox database which is linked to the original mailbox database which host the single mailbox that we want to recover.
    2): restore the mailbox database backup to this mailbox DB under the RSG.
    3): Merge the recovered single mailbox to the existed one.
    My question is:
    When I create the RSG and the mailbox DB under this RSG using the tool on EMC, can I specify the path of "System folder path" and "mailbox DB file path" on  drive other than C:, the C: drive on Exchange CCR active node does
    NOT have enough disk space so it has to be created somewhere othan than C: drive?

    Hi, Andy:
    Thans for your post.
    I have a look at
    http://technet.microsoft.com/en-us/library/aa997694(v=exchg.80).aspx.
    One thing I have question is when you use cmdlet to create a RSG:
    new-storagegroup -Server <Server_Name> -LogFolderPath <path_to_Logfiles> -Name <RSG_Name> -SystemFolderPath  <Database_Path> -Recovery.
    What should be the <server_name>?
    we use CCR, if I want to use this cmdlet to create a recovery storage group on current active node of CCR, do I need to enter the actual name for this active node, or I juts need to enter the cluster name?

  • Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

    Hi,
    I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
    Configuration server Exchange 2007 SP3 :
    Domain : test.com
    OS : Windows 2008 server SP2 (not R2)
    Firewall : OFF
    Exchange roles are on separate three  servers : CAS - MAILBOX - HUB.
    Configuration Server Exchange 2013 :
    Domain : new.com
    OS: Windows 2012 R2
    Firewall : OFF
    This environment is on a closed network unable to reach internet.
    I have try to restart the Replication service, but it didn't worked.
    I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
    Anyone ever had this issue?
    Thanks you and have a nice day.

    Hi ,
    Based on my knowledge below things need to checked.
    1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
    2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
    DataMoveReplicationConstraint : None
    Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
    3.Restart the Microsoft exchange mailbox replication service and check the results.
    4. Have you tried moving the same mailboxes to the different databases.
    5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
    Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
    Please feel free to reply me if you have any queries.
    Thanks & Regards S.Nithyanandham

  • Error: The specified mailbox database [Mailbox Database Name] does not exist, when you try to export mailbox in Exchange 2007

    [Symptom]
    ======================
    In Exchange 2007, when you want to export mailbox to a .pst file, you should run the
    Export-Mailbox cmdlet from a 32-bit computer that has the following installed:
    The 32-bit version of the Exchange management tools
    Microsoft Office Outlook 2003 SP2 or later versions
    If not, you may encounter the following error message:
    You check that you have these required installed, but you get the error below when you run Export-Mailbox in EMS.
    “The specified mailbox database [Mailbox Database Name] does not exist.”
    [Cause Analysis]
    =======================================
    This is because that the account you use to run Export-Mailbox cmdlet don’t have the Exchange Server Administrator role assigned.
    You can check if this account has been delegated the Exchange Server Administrator role through the following path.
    EMC -> Organization Configuration-> Check permissions in the result pane.
    To delegate this Exchange Server Administrator role, right click on the
    Organization Configuration node and choose Add Exchange Administrator,
    you will see the Add Exchange Administrator window.
    [More Information]
    ==============================
    Export-Mailbox
    http://technet.microsoft.com/en-gb/library/aa998579(v=exchg.80).aspx
    How to Export and Import mailboxes to PST files in Exchange 2007 SP1
    http://blogs.technet.com/b/exchange/archive/2007/04/13/3401913.aspx
    Exchange 2007 cannot export pst files via its powershell
    http://social.technet.microsoft.com/Forums/forefront/en-US/b3bc0dce-35f3-4a69-9a33-4f2a855b9f94/exchange-2007-cannot-export-pst-files-via-its-powershell?forum=exchangesvrgenerallegacy
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi,
    Based on my test, if you make the user the owner of the database (rather than a user with the db_owner role), when you create a query, it creates it under the dbo schema rather than DOMAIN\username.
    Steps to do so (in Management Studio):
    Right click database, select Properties 
    Click File 
    Change Owner in the textbox 
    OK to confirm 
    Downside - other users under db_owner role will still have their username appended. So schemas have to be created for these users.
    Jaynet Zhang
    TechNet Community Support

  • OIM 9.1.0.18 - Unable to create User MailBox in Exchange 2007

    Hi,
    I am using OIM 9.1.0.18 configured AD resource with SSL (636).
    AD SSL is done. I was able to provision user & change passwords too.
    Remote Manager is configured & running fine.
    Exchange Connector version *9.1.1.4*
    Followed ActiveDirectoryExcServ_guide.pdf doc
    Exchange 2007 was installed on another system. All my systems are Windows 2003 R2 SP2
    Exchange 2007 has been configured with Remote Manager
    User got created on Exchange Server with Recipient Type as Mail User.
    The Recipient Type should be UserMailBox.
    Pls share some thoughts.
    Regards,
    Praveen

    I created a new user. In User Detail >> Resource Profile --> Exchange the status is Provisioned.
    User is created in Exchange but still the RecipientType in Exchange is MailUser.
    The Recipient Type should be UserMailBox.
    Exchange Mailbox Details
    AD Server     ----     ADITResource
    Object GUID     ----     b6304538ae3bb847a9c1fe0f334f94e7
    Log On Name     ----     [email protected]
    Mail Store Name     ----     ADITResource~CN=Mailbox Database,CN=First Storage Group,CN=InformationStore,CN=PWEXCHANGE,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=pwad,DC=com
    Email Alias     ----     paul
    Display Name     ----     paul smith
    Weblogic logs.
    Running CHECKPROCESSORDEREDFORUSER
    Target Class = com.thortech.xl.util.adapters.tcUtilXellerateOperations
    Running GETVALUE
    Target Class = com.thortech.xl.integration.Exchange.tcExchangeTasks
    Running GETSTRINGLENGTH
    Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
    Running Create mailbox
    CN=PWEXCHANGE,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative G
    roups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=pwad,DC=com--
    Running SETUSERPROPERTIES
    Target Class = com.thortech.xl.integration.Exchange.tcExchangeTasks
    Can anyone help me out with this.
    Regards,
    Praveen

  • How to create custom folder in every mailbox of Exchange 2007 mailbox : not using Managed folder

    Hello ,
    We want to create custom folder in mailbox as root or inside inbox for every user of mailbox but not using managed folder .
    I have found below article , but we do not get success to do that .
    http://careexchange.in/create-a-custom-root-folder-in-all-the-mailboxes-bulk-in-exchange-2010/
    Any idea how to do that ?
    It will be great helpful for  us.
    Thank you in advance.
    Regards
    faiz

    What happens when you try that method? What errors do you get? Have you ensured you've installed EWS 1.2 per the requirements listed in the script? (it actually mentions 1.1, but that no longer seems to be available, but 1.2 is here
    http://www.microsoft.com/en-gb/download/details.aspx?id=28952 ).
    I'm assuming you're running Exchange 2007 (since you're posting in the 2003/2007 forum, and this won't work on 2003), is that correct?
    While I don't know for sure that the script will work on 2007, have you ensured that you've amended the file paths to the correct locations? Eg, assuming it should work you'll need to amend the line :
    $service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2010_SP1)
    to reflect the version of Exchange you're running, and the line :
    Import-Module -Name "C:\Program Files\Microsoft\Exchange\Web Services\1.1\Microsoft.Exchange.WebServices.dll"
    with whatever version of EWS you've installed.

  • Moving mailboxes in Exchange 2007

    Does anyone know what is the effects of moveing VoIP-enabled mailboxes to another Exchange 2007 servers?

    The key text from the link I cited in my initial response:
    Moving Subscriber Mailboxes for Cisco Unity 8.x
    From time to time you may need to move subscriber mailboxes to another server that is faster or has more disk space available, or you may want to move mailboxes when you add new servers to your network. It is possible to move subscribers between servers without having to shut down Cisco Unity.
    Caution If you are moving a group of subscriber mailboxes at once, confirm that you do not inadvertently select the Unity Messaging System, UAmis, UVPIM, UOmni, or USbms Exchange mailboxes. To move these special mailboxes, see the "Moving the Unity Messaging System, UAmis, UVPIM, UOmni, and USbms Exchange Mailboxes for Cisco Unity 8.x" section.
    To move Exchange mailboxes from one server to another, follow the instructions in the Microsoft Exchange documentation. "

  • Move Mailbox from Exchange 2007 to 2013 creates additional Contacts and Junk E-mail folders in Outlook Clients

    I have moved a handful of mailboxes from my Exchange 2007 server to my new Exchange 2013 server.  When the users logon to Outlook, usually Outlook 2007 Pro, they have a new default Contacts folder and Junk Email folder that are empty.  I
    have to copy all the user's contacts into the new default folder and delete the old one.  Not sure why this is happening.  Any information would be appreciated.  Thanks.

    Are you sure your Outlook 2007 is compatible with Exchange 2013?
    http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    http://support.microsoft.com/default.aspx?kbid=2687404
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Creating multiple mailboxes on Exchange 2007 fails

    Hi All,
    We have a problem to create multiple mailboxes simultaneously on Exchange 2007 using the OIM Exchange connector. Only one of the mailboxes is created when multiple powershell scripts are launched at the same time. This problem only occurs in the production environment and not on the Exchange 2007 test server. Therefore it's likely to be an Exchange 2007 server setting causing the other powershell processes and mailboxes to fail. Has anyone else experienced this problem?
    Thanks,
    Albin

    hi.
    have you managed to solve this issue? we have a similar problem when updating some exchange mailbox variables through powershell cmds via OIM. if we run several cmds simultaneously, or right after each other, only the first one is run. tried googling it, but no luck so far.
    thanks,
    tinba

Maybe you are looking for