asked on

Outlook 2007 Archiving and Exchange Server

I manage the Exchange Server on which all our internal email accounts are stored. I'm about to retire from my position.
My own "business" Outlook account has been in service for over 10 years. My account must remain accessible to my successor.
It now has several subfolders under the INBOX folder with thousands of emails in these folders.
I'd like to pick and choose which of these folders / files to archive up to a very late date: November 1, 2019.
Some of the subfolders contain personal information emails. I don't want to leave any traces of those on the Exchange Server.
My thoughts are that archiving would create an "archive" folder on my own computer's local hard drive. I can then cut / copy that archive folder to a flash drive. I'm supposing the "archive" folder would remain on my account on the Exchange Server. If so, I'd want it removed.
So:
1) Can I pick and choose the folders AND date for archiving?
2) Can I remove the archive folder from my account on the Exchange Server?

ASKER CERTIFIED SOLUTION

Kimputer

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

Saif Shaikh

1) Can I pick and choose the folders AND date for archiving?
Yes you can..

2) Can I remove the archive folder from my account on the Exchange Server?
You archive and that will be local to the user outlook profile.

You can also follow below steps to export PST from exchange server, but this will require you to install Outlook 2003 or 2007 must be installed on your client.

Step 1: Prerequisites: Exchange Server 2007 Management Tools (32-bit)
There is a fine article at the Petri IT Knowledgebase detailng how to install the management tools with links to the prerequisites. Most of these are only necessary if wanting to run the tools from Windows XP or Windows Server 2003. Here is the article for further details:

http://www.petri.co.il/installing_exchange_2007_management_tools_on_a_32bit_os.htm

Step 2: Install Exchange Server 2007 Management Tools (32-bit)
As of the writing of this How-To, the 32-bit tools for SP1, SP2 & SP3 can be found at the following link

http://www.microsoft.com/en-us/download/details.aspx?id=11876

Step 3: Install Outlook 2003 SP2 and up (32-bit)
You will have to provide your own download/installation media if you do not currently have access.

The Exchange Management Shell needs the appropriate MAPI libraries found in Outlook from version 2003 SP2 and up to create the PST file. Seems silly to me, but it's the way it works.

Step 4: Grant the Exporting User Full Access to the source mailbox
This can be done for one mailbox, an OU, a database, or the entire organization if the proper parameters are used, for my purpose, I am only selecting one mailbox.

Get-Mailbox -Identity source@domain.com | Add-MailboxPermission -User Exporter -AccessRights FullAccess

I have elected to pipe the output of the Get-Mailbox cmdlet to the Add-MailboxPermission cmdlet to make it easier (for me, anyway) to include more than one user.

Step 5: Select Items to Export (optional)

Simply exporting the mailbox as-is should require nothing more than the command in step 6; however, if only a section of items need to be recovered/exported, have a look at the following TechNet article detailing all of the parameters of the Export-Mailbox cmdlet available in Exchange 2007.

Step 6: Export the Mailbox to a PST
There are several parameters that are available to the cmdlet; for my purpose (of archiving a mailbox to a PST) I don't need any.

From the Exchange Management Shell (EMS) run the following command:

Export-Mailbox -Identity source@domain.com -PSTFolderPath C:\Users\Exporter\Desktop\source.pst

You will see a bar across the top of the shell detailing the progress of the export.

You can also use the date range i.e. as per your question: "Can I pick and choose the folders AND date for archiving?"

Export-Mailbox -Identity 'User' -StartDate "09/11/2015" -EndDate "10/19/2015" -PstFolderPath

baleman2

ASKER

Because Kimputer's solution didn't require me to use powershell commands in any way, I selected it as my solution. Have already followed those instructions and problem was resolved satisfactorily.