Export mailbox to PST - Exchange 2007

I ran this command on my Domain Admin Account from our 2007 Exchange Server 2007 w/ SP3:
[PS] C:\Users\jesse\Desktop>Get-Mailbox | Add-ADPermission -User "jesse.Sams" -
AccessRights GenericAll -ExtendedRights Send-As, Receive-As, MS-exch-store-admin
When I run the command:
Export-Mailbox –Identity <mailboxUser> -PSTFolderPath <pathToSavePST>
-StartDate "<//span>08/29/12" –EndDate "08/29/12"
-DeleteContent
I get the error:
Export-Mailbox : Error was found for First Name ([email protected]) because: Error occurred in the step: Moving messages. Failed to copy messages to the destination mailbox store with error: MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000, error code: -1056749164 At line:1 char:15 + Export-Mailbox <<<<
-Identity first.last -PSTFolderPath d:\archive -StartDate "08/29/12" -EndDate "08/29/12" -DeleteContent
+ CategoryInfo
: InvalidOperation: (0:Int32) [Export-Mailbox], RecipientTaskException
+ FullyQualifiedErrorId : 70397370,Microsoft.Exchange.Management.Recipient Tasks.ExportMailbox
Any help on this issue would be greatly appreciated.
Thanks, Jesse

Hello jwmms,
You can use this command to do that:
Get-mailbox| add-mailboxpermission -user "jesse.sams" -AccessRights fullaccess
Add-MailboxPermission
http://technet.microsoft.com/en-us/library/bb124097(EXCHG.80).aspx
Thanks,
Evan Liu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

Similar Messages

Export mailboxes to PST (Exchange 2007)

Hi All,
Is there an 'export-mailbox' cmdlet I can use to export each of the mailboxes in our mailbox database using the following file name format, so that the full smtp address is used as the filename of each the PST file exported:
[email protected]
[email protected]
etc, etc
We are currently migrating to a cloud email provider and they have strict rules on processing PST files. The exchange database is only 65GB in size, so not that big in the grand scheme of things.
Any help appreciated.
Thanks.

Untamed, you sure can. Here's the original code I sent:
Get-Mailbox -Database <databasename> | Sort name | % {
    $MbxSmtp = $_.PrimarySmtpAddress.ToString()
    Export-Mailbox $MbxSmtp -PstFolderPath "\\Servername\Share\$MbxSmtp"
Note the first line, which ties the code to a single database. You can change that line to focus on any group of mailboxes, even to a single mailbox. Here's code for a single mailbox:
Get-Mailbox <mailbox alias> | Sort name | % {
    $MbxSmtp = $_.PrimarySmtpAddress.ToString()
    Export-Mailbox $MbxSmtp -PstFolderPath "\\Servername\Share\$MbxSmtp"
Here's code for an OU:
Get-Mailbox -OrganizationalUnit <OU DN, as in "ADDomain.company.com/OURoot/SubOUName"> | Sort name | % {
    $MbxSmtp = $_.PrimarySmtpAddress.ToString()
    Export-Mailbox $MbxSmtp -PstFolderPath "\\Servername\Share\$MbxSmtp"

Export Mailboxes to PST using CSV

Hello - I'm in the process of exporting mailboxes from another exchange server from a company we acquired so I can import email into their new mailbox. I have a CSV formatted with headers
old,new which has their old alias and new alias. I also only want to capture the last 60 days of email. However, I seem to be missing something in formatting as it keeps creating a new line instead of just executing the script. I'm at a loss and can't seem
to get this working.
$sixty = get-date -format "M/d/yyyy" (get-date).AddDays(-60)
$UserList=Import-CSV C:\users.csv
FOREACH ($Person in $UserList) {
New-MailboxExportRequest -Mailbox $Person.old -ContentFilter {(MessageKind -eq 'Email') -and (Received -gt $sixty) -or (Sent -gt $sixty)} -FilePath "\\server\pst\"$Person.new".pst"
Any help would be appreciated!

Try
$sixty = get-date -format "M/d/yyyy" (get-date).AddDays(-60)
$UserList=Import-CSV C:\users.csv
FOREACH ($Person in $UserList) {
New-MailboxExportRequest -Mailbox $Person.old -ContentFilter {(MessageKind -eq 'Email') -and ((Received -gt $sixty) -or (Sent -gt $sixty))} -FilePath "\\server\pst\$($Person.new).pst"
CRM Advisor

Exchange 2010 Export Mailbox to PST using only .EDB file

I have Exchange 2010 SP2 Update Rollup 4, SBS 2011 (which is similar to Server 2008 R2). I have recently recovered from a server crash due to a faulty RAID controller and need to recover some e-mail (and possibly contacts) from a couple of mailboxes.
My main concern is that my old .edb file is in a old forest that is different than my current forest. Due to the length of the old internal domain name having more than 15 characters (I previously migrated using a answer file) and my current internal
domain name is 15 characters.local they are different.
I also dont have the log files or STM file
With the two internal domain names being different will I still be able to follow this related topic:
http://social.technet.microsoft.com/Forums/zh/exchange2010/thread/8f4eb425-72ff-4d18-abfc-5c00be7113e2
If not please let me know which direction I should be going. I know there are third part tools that can get this done but not in the budget right now.
Teron

Hi,Teron,
Cross forest export mailbox is not possible,if you have the old forest server still running you can export the mailbox in the old forest to PST file then import the pst file to your current forest.
Otherwise you should convert the edb file to PST with thirdparty tool as the above guys said.
Some additional information just for your reference.
http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/d731ac97-416b-4ff6-a4d9-861ce4345292
http://social.technet.microsoft.com/Forums/en-US/exchangesvr3rdpartyappslegacy/thread/74233836-38d9-4682-81d2-7dd395066574
Regards,
Sharon
Sharon Shen
TechNet Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

Export mailbox to pst from exchange 2010 shell - without calendar

Is there a way to edit this command:
New-MailboxExportRequest -Mailbox Kweku -IsArchive -FilePath "\\SERVER01\PSTFileShare\Kweku_Archive.pst"
that it would export mailbox without calendars?
with best regards,
bostjanc

You can use the -ContentFilter option to filter folders \ date
Exchange Blog:
www.ntweekly.com
MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

Export-mailbox to PST file: unknown error in approving object

Hi
I'm trying to validate export/import of PST files with Ex2K7 SP1.
I have this error during export-mailbox, and didn't find anything about it on the Net:
[PS] C:\Documents and Settings\Administrator>Export-Mailbox user01 -PSTFol
derPath C:\temp\
Confirm
Are you sure you want to perform this action?
Exporting mailbox content from the mailbox 'user01' into .pst file
'C:\temp\user01.pst'. This operation may take a long time to complete.
Yes Yes to All No [L] No to All Suspend [?] Help
(default is "Y"):
Export-Mailbox : Error was found for user01 ([email protected]
) because: Error occurred in the step: Approving object. An unknown error has o
ccurred., error code: -2147221241
At line:1 char:15
+ Export-Mailbox <<<< user01 -PSTFolderPath C:\temp\
I'm doing test on one virtual machine hosting AD (win2K3SP2 En), Ex2k7SP1 En, Outlook 2007 Fr.
Could it come from the Outlook or user mailbox language ?
The mailbox have been "initiated", I opened it with OWA, select French language, self sent message. I also opened it with Outlook 2007 on the server.
Thanks.

Hello,
Details u needed.
SUMMARY
The Fixmapi.exe tool is included with Internet Explorer 5 & above to detect and aid in resolving conflicts with Messaging Application Programming Interface (MAPI) files that may affect your ability to send and receive mail and faxes from other programs.
FixMAPI ( What Exactly it does ?).....
Makes a backup copy of the current copy of mapi32.dll on the client computer, and restores mapi32.dll with the MAPI stub library, mapistub.dll.
Quick Info
Exported by:
mapistub.dll
Called by:
Client
Implemented by:
Windows
DWORD STDAPICALLTYPE FixMAPI(void);
Return Values
If the function succeeds, the return value is a non-zero value.
If the function fails, the return value is zero. To get extended error information, call the Microsoft Platform Software Development Kit (SDK) function, GetLastError.
Remarks
FixMAPI does not replace the current mapi32.dll file if the file is marked as read-only.
FixMAPI does not replace the current mapi32.dll if Microsoft Exchange Server is installed on the computer.
When FixMAPI makes a backup copy of the current copy of mapi32.dll on the computer, it assigns the backup copy a name different from "mapi32.dll". It then directs subsequent calls intended for that assembly to the backup copy
URL - > for u r more info. http://support.microsoft.com/kb/228457

What is the maximum size for mailbox per user (Exchange 2007)

Hello,
I'd like to know:
What is the maximum size per mailbox, and is it not recommended to exceed 3 GB and about the items how many is the maximum per folder (inbox, .. )
I've Exchange 2007 SP2, Outlook 2007 and 2010.
Thank you.

Hi
There is no size limit on mailboxes up to the maximum size of your database. I normally recommend 2GB mailbox limits if you have some form of archiving in place. If you have no archiving in place then the limit should be set at the amount of
data people need to keep - it is not a good idea for people to store mail in PST files because there is a limit on their mailbox.
See this article for item count recommendations:
http://support.microsoft.com/kb/905803
Also you need to upgrade your Exchange 2007 server to SP3 ... SP2 has been out of support for nearly 3 years already:
Exchange 2007 Support Lifecycle
Steve

Veiwing mailbox sizes in exchange 2007

Is it me or is Exchange 2007 missing mailbox size? i cant anywhere to veiw the size of a users mailbox.

Sunil;
Never use a Format- cmdlet before sending data to Export-Csv
Use Select-Object instead.
PowerShell V1:
Get-MailboxStatistics -Database "Mailbox Database" |Select-Object DisplayName, LastLoggedOnUserAccount, ItemCount, @{expression={$_.totalitemsize.value.ToMB()};label=”Size(MB)”}, LastLogonTime, LastLogoffTime | Export-Csv MailboxSize.csv -NoTypeInformation
PowerShell V2:
$MailboxStatistics = @{
Database = "Mailbox Database"
$Select = @{
Property = "DisplayName","LastLoggedOnUserAccount","ItemCount",
@{expression={$_.totalitemsize.value.ToMB()};label=”Size(MB)”},
"LastLogonTime","LastLogoffTime"
$Csv = @{
Path = "MailboxSize.csv"
NoTypeInformation = $true
Get-MailboxStatistics @MailboxStatistics |Select-Object @Select |Export-Csv @Csv
Karl
http://unlockpowershell.wordpress.com
-join("6B61726C6D69747363686B65406D742E6E6574"-split"(?<=\G.{2})",19|%{[char][int]"0x$_"})

Executable or batch script for end users to export mailbox to PST

We are in the process of taking over a small firm and proceeding with manual migration of mailboxes from this firm , currently we do not have full access to their environment and having a hard time depending on admins of their organization dealing over
to exporting mailboxes and then importing them back to our exchange environment, my idea is to rather provide a executable or batch script to user's of their organization get their mailboxes exported out directly from end users so that we do not
have to depend on remote organization's admins for every single user out there . is there a batch script or some executable code that end users can run to have their mailbox exported out directly ?
Aditya Mediratta

Seems like, this informative article would be a good approach to resolve your concern :
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/managing-pst-import-export-process-exchange-server-2013-part2.html
Moreover if you wish, you may also give a shot to this automated solution (http://www.exchangemailboxtopst.org/) in order to accomplish this job in more easier and quicker way.

Inter-Org Mailbox moves from Exchange 2007 to Exchange 2013

G'Day All,
Is it possible to move Exchange 2007 mailboxes to Exchange 2013 in a different forest? Both environment has all the required patches and service packs.
There is a two way trust, and I don't want to introduce Exchange 2010 CAS in the source forest if I don't need to.
I have read the following article http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/ but it is not clear what is the required to setup in Exchange 2007. I have read many other articles to do with Exchange 2013 mailbox moves, endpoints,
etc, but non of them is clear of how does it work having Exchange 2007 source.
Thanks in advance.

Hi Atonal,
Could you please take a look at this technet blog that has been well elaborated about your concern :
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The blog provides step-wise assistance while you are planning to move from exchange 2007 to 2013.
Here is another library available from technet team that includes all the terms while preparing mailboxes for cross-forest move request : http://technet.microsoft.com/en-us/library/ee633491%28v=exchg.150%29.aspx
Alternatively, you can checkout this proficient application (http://www.exchangemigrationtool.com/) in order to avoid any interruption and proceed hassle-free migration from exchange 2007 to 2013.

Mailbox Move from Exchange 2007 to Exchange 2013

I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
Thanks

When you do a mailbox move it stays connected during the initial sync. Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
to access their mailboxes.
You can control this behavior by setting the SuspendWhenReadyToComplete
switch either by command line when creating the move request via the EMS
https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Concurrent mailbox moves from Exchange 2007 to 2013

We are in the process of migrating from Exchange 2007 to Exchange 2013. We have about 200 mailboxes and we want to move them in groups of 40-50 at a time. I am trying to get more then 1 mailbox to actually sync to the new database at once.
I start the batch with 49 mailboxes but only 1 mailbox is showing any progress when I go to details. They all have a status of "syncing" but only one has any "items synced".
I have run multiple articles about increasing concurrent migrations from 2007 to 2010 and 2010 to 2013 and they all mention going to MsExchangeMailboxReplication.exe.config on the destination server and setting the “MaxActiveMovesPerTargetMDB" value
to something larger. By default 2013 has it set to 20 would should be more than enough for me. However despite this setting I still only see 1 mailbox syncing at a time.
Is there someplace I should be making a similar change on the 2007 box? I can't find a file with that name so I am not sure if there is something to change or if it's even needed.
Why is this not working? Any help is much appreciated. Thanks!

Outlook will show the infamous login popup and users will not be able to access Exchange 2013 Public Folders.
You can check the Outlook Clients version in Exchange Management Shell with Get-LoginStatistics (ex. Outlook 2010):
Get-Logonstatistics | select-object username,clientversion | where {$_.clientversion -gt "14.0*" -AND $_.clientversion -lt "14.0.6117.5001"}
Step by Step Screencasts and Video Tutorials

Outlook cannot connect after mailbox move from Exchange 2007 to 2013

I am in the middle of migrating an Exchange Server 2007 to 2013. Everything went fine up until I moved the first mailbox. I can access the mailbox via OWA, but not Outlook 2010. When I checked the account settings, the server is incorrect. It shows [email protected]
If I manually enter the name of the Exchange 2007 server, it changes to the Exchange 2013 server, as it should. I save the settings, open Outlook, the connection fails, and the server setting is changed to [email protected]
I then ran the Microsoft Connectivity Analyzer. There are 2 lines which caught my attention:
AutoDiscoverInternalRpcClientServer
[email protected]
AutoDiscoverHomeMdbDn
/o=mydomainMail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected]/cn=Microsoft Private MDB
I've checked and rechecked everything and can't seem to locate my error.
Any thoughts? Thanks.

Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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 active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

How to create new storage group and mailbox database on exchange 2007 CCR

Hi, Our Environment:
Exchange 2007 SP3 CCR.
Now I want to create a new storage group with edb file and log files on the new drive.
My plan is as below:
Once we have new drive ready on both active node and passive node,
1): Create new storage group with log files for this new storage group on other new drive from Active Node.
2): Create new mailbox database under this newly created storage group with the DB file on the new drive from active node.
My question is:
1): Do I need to perform above steps from active node only? or Do I need to do it from both active node and passive node?
2): How many storage groups can we create on one Exchange 2007 Enterprise server, we already have 25 SGs in place.
Thanks in advance.

Hi,
Here are my answers you can refer to:
1. We can just create new storage group on the active node. And it’ll be replicated to the passive node.
We can use the following command in EMS to verify the new Storage Group is being replicated to the passive node:
Get-StorageGroupCopyStatus "Second Storage Group" | Select SummaryCopyStatus,CCRTargetNode
http://exchangepedia.com/blog/2007/08/how-to-create-new-storage-group-in-ccr.html
2. For Exchange 2007 enterprise version, we can have up to 50 storage groups:
http://www.computerperformance.co.uk/exchange2007/exchange2007_storage_groups.htm
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Export mailbox to PST - Exchange 2007

Similar Messages

Maybe you are looking for