Filter Mailbox database by size in Exchange 2007

How do I filter the mailbox database to determine mailbox size, i.e. users who are near their limit.

Hi,
Please try to use the cmdlet like
Get-Mailbox -Database "Mailbox Database"
-retrieves a summary list of all mailboxes in the mailbox database named Mailbox Database.
Get-Mailbox -Server EXCH01
-retrieves a summary list of all mailboxes on the server named EXCH01.
Get-MailboxStatistics -Database MailboxDatabase
-retrieves the mailbox statistics for all mailboxes in the mailbox database named MailboxDatabase.
Get-MailboxStatistics -Server EXCH01
-retrieves the mailbox statistics for all mailboxes on the server named EXCH01
find it here http://www.windowsadmin.info/viewtopic.php?f=20&t=116
Regards from www.windowsadmin.info

Similar Messages

Maximum Database size in exchange 2007

Hi Team,<o:p></o:p>
What is the maximum database size we can have in Exchange server 2007 SP3 RU8 standalone server.<o:p></o:p>
In our environment we have 1800 users hosted on the
exchange 2007 server with DB size(EDB file) of 1.61TB. What is the maximum size it can grow upto. Any response appreciated.
Thanks<o:p></o:p>
Srini<o:p></o:p>

Amit just beat me to posting Harold Wong's article! :-) Since you're currently on 1.61TB the artificial limit has already been adjust via the registry setting mentioned (the article mentioned 50GB though I've seen others mention 250GB). So the maximum limit
is 16TB, but whoever adjusted things to allow your current size may have set the artificial limit as something smaller, so you'd want to check the registry to see what it has been set to in your case.
I'd also echo the comments about database size. Depending on how you handle backups then they may also play a part. Since most backups work on the basis of backing up / restoring the entire database (obviously backing up changes rather than the whole thing
each time), then the event of you needing to restore it's much easier if you have smaller databases to deal with. Splitting your mailboxes across multiple stores will help minimise the time required before you can get some users online again in the case of
a total failure. Also, if you split your mailboxes across 5 databases and then have a problem (for instance corruption) on one of them, then only around 1/5 of your users are effected rather than all of them.

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$_"})

Move mailboxes and public folders from exchange 2007 to Exchange 2013

1. How do i move mailboxes from exchange 2007 to exchange 2013. I have more than 1000 mailboxes.
What is the correct way to migrate. do i need to move a single mailbox. During migration do the mailboxes get corrupted
2. I want to move public folders from Exchange 2007 to Exchange 2013.
I ran powershell commands and got these results please do guide me how to move to exchange 2013.and what are the shell commands
Get-publicfolder
Name Parent Path
IPM_SUBTREE
Get-publicfolder | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
Get-PublicFolderStatistics | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
exchangeV1 schema-root\microsoft\exchangeV1
Internet Newsgroups Internet Newsgroups
Get-PublicFolder -Recurse | fl name,replicas > c:\publicfolder.txt
Name : IPM_SUBTREE
Replicas : {}
Name : Internet Newsgroups
Replicas : {MAIL\Public Folder Storage\Public Folder Database}

I have started moving mailboxes , i have tried moving few individual mailboxes to see how things go
MAIL is my exchange 2007 and MAIL1 is my exchange 2013, please do refer the below result
PS] C:\Windows\system32>Get-MailboxDatabase -server mail
Name                           Server          Recovery
ReplicationType
Mailbox Database               MAIL            False           None
[PS] C:\Windows\system32>Get-MailboxDatabase -server mail1
Name                           Server          Recovery
ReplicationType
Mailbox Database 1460777952    MAIL1           False           None
[PS] C:\Windows\system32>New-MoveRequest -Identity '[email protected]' -TargetDatabase "Mailbox Database 1460777952"
DisplayName               StatusDetail              TotalMailboxSize
TotalArchiveSize         PercentComplete
[email protected]          Queued                    363.6 MB (381,217,115 ...
0

Moving the mailbox database copy from one exchange server to another exchange server 2010 DAG

Hello Team
is it possible to the move the passive copy of database and logs from one server to another exchange server in the same DAG with out removing and deleting the mailbox database copies in exchange 2010
normaly procedure is
Remove the mailbox database copies and manually delete the .edb files and logs from the physical location and re-add the mailbox database copy to the new server in the DAG.
is that any way to achieve to move the passive database copy to another exchange 2010 server in the same DAG ?

From your note, you appear to have a two-member DAG (with a server hosting your active database, and a second hosting the passive copy), and you want to move your passive database copy from the current passive server to another. Your note
about what "the normal procedure is" isn't 100% correct - there are many ways to handle this task, and all can be considered "normal". Why not just add the third server to the DAG and
add a database copy on that third server? Once it is fully seeded, you can remove the current passive copy. This way, you never lose your redundancy.
Yes i can add the third and fourth serve in DAG , but i cannot add the mailbox database copies to the 3rd and 4th mailbox server in DAG as am using RTM version of exchange 2010 which is allowing to have only 5 database inclding mailbox datbase copies
and also currently my lab setup is two member dag (with a server hosting your active database,
and a second hosting the passive copy) in the same site named SITE A
and recently i have created new SITE B and included the 3rd and 4th DAG members in the same DAG
i want the mailbox database copies from the mailbox server database in SITE A to
Mailbox server database in SITE B as passive copy
That is why i want to move the mailbox database without deleting / removing it manually
Hope you understand my situation!

Moving messages to mailboxes on multiple computers under Exchange 2007

My work email was recently switched to Exchange 2007, which behaves like IMAP. However, since space is limited on the server, I need to move messages from my Inbox and save them "on my Mac", and some of these messages are moved automatically using Rules that I have set up.
Now, I have two computers with the same Rules. The problem is that when I open my mail on one computer, rules are applied and the messages are moved from my Inbox, but then, on my second computer, these messages are nowhere to be found since they were removed from the Inbox.
The only Mailboxes that are synced through Exchange are the Inbox, Sent, Drafts, and Trash. All my other mailboxes are on my Mac (on both computers, same mailboxes).
How can I move messages from the Inbox to archive them on my Mac on one computer and still have access to these emails on the other computer? As soon as I move a message from the Inbox, it disappears on my other computer before I have a chance to apply the same move. The result is that depending where I open my email, some messages are stored on one machine or the other, but not both. Is the only solution to copy messages instead of moving them? I will then end up with many duplicates eventually, and it will be hard to know which has already been copied from my Inbox and which has not.
Am I missing an easier solution? It used to work well when my email was a POP account, and other IMAP emails (Gmail) are OK because I can store all my mailboxes on the server. But in the case of my work email, because of space constraint, I cannot store all my messages (>30,000) in Exchange mailboxes.
Thank you for your help.

You’re welcome.
Unfortunately, I don’t know what happened here and I’m afraid you may have lost those messages. If the messages have disappeared in Mail, they are not on the server, and you don’t have a backup, your only option is probably to try to salvage as many deleted *.emlx files as possible with a data recovery tool such as Data Rescue II, TechTool Pro, or FileSalvage. Of these, the only one I know for sure that can currently recover deleted *.emlx files is FileSalvage. Stop using your computer right now if you want to try that, as anything you do with the computer may cause the deleted files to be overwritten.
You should also verify/repair the startup disk (not just permissions), as described in the following article, in case there is something amiss in the filesystem that has a bearing on this:
The Repair functions of Disk Utility: what's it all about?
When done, report the names of the files and folders present at the first level of the ~/Library/Mail/Mac-username/ account folder.
In order to post the exact file names and avoid typing mistakes, proceed as follows. In the Finder, go to ~/Library/Mail/Mac-username/. With that folder open, if you’re looking at it in View > as List mode, first collapse any expanded folders so that the Finder only shows the files and folders at the first level. Now, do Edit > Select All (⌘A), then Edit > Copy (⌘C), and paste it in your reply to this post -- you may disguise any mailbox names you wish to keep private.
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder, i.e. ~/Library is the Library folder within the user’s home folder.

Shared mailbox - send as and auditing Exchange 2007

Got 3 users A,B,C who all access a shared mailbox X.
They have a requirement to be able to answer emails sent to mailbox X BUT the return address to be X (i.e. not their own or send on behalf etc) so any subsequent relies still go to X and not the individual email addresses.
However, enother requirment is that there needs to be a way to determine which user (A, B, or C) actually sent the email from shared mailbox X.
Any way at all to do this?

Hi,
Since the full access permission has been assigned to users, please give Send As permission to these 3 users (A,B,C) for this shared mailbox X. Then user A,B,C
can send as the mailbox X with the From field shown as Mailbox X. Please follow these steps to set it:
1. Make sure the Full Access permission have been configured correctly.
2. Give send as permission to UserA, UserB and UserC for shared mailbox X.
Add-ADPermission -Identity “Mailbox X” -User UserA -Extendedrights "Send As"
Add-ADPermission -Identity “Mailbox X” -User UserB -Extendedrights "Send As"
Add-ADPermission -Identity “Mailbox X” -User UserC -Extendedrights "Send As"
3. Then UserA, UserB and User C can send messages by the following steps in Outlook:
a. Click New Email > OPTIONS > From, then the From field is shown in the message.
b. Click From > Other E-mail Address, and select the Mailbox X.
Then the recipients would receive the messages which the From field is shown the Mailbox X name instead of UserA, UserB or UserC.
To track which user has send as Mailbox X to the recipients, we can enable message tracking log or
Mailbox audit logging to track it.
Regards,
Winnie Liang
TechNet Community Support

Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824
Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288
StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115
Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970
StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
Jon

Any update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

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

Mailbox database Size

Hi,
   I have DAG enabled Exchange Server 2010 installed with three mailbox databases having sizes 282GB,162GB and 129GB respectively. I have started with a total of 250GB in 2010 and now it has reached a size more than 650GB.
   It has become very difficult to take the backup of such huge database files now and restoring it in case of a DR.
   Presently I have not enabled online archiving in any of these mailboxes mainly because most of the PCs are installed with outlook 2007 which doesn't show online archive.Of course OWA is another candidate to see those mails.
   Please suggest a best practice to reduce the size of these mailbox databases without losing any of the mails.
Thanks
Thomas

As mentioned above, Exchange database files do not shrink.
If you do a defrag, then since you have copies of this DB in the DAG then you have to reseed. take a look at this
http://blogs.technet.com/b/rmilne/archive/2013/08/23/offline-defrag-and-dag-databases_2c00_-oh-my_2100_.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.

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?

Exchange 2007 database won't mount due to MapiExceptionCallFailed errors

A server is running Exchange Server 2007 SP2 on Windows Server 2008 64-bit. After a couple years of running smoothly, the Windows Application event log started filling up with several instances every minute of the following error:
MSExchangeIS (2644) First Storage Group: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 5, PgnoRoot: 10) of database H:\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb (165296 => 3185, 817790).
Messages sent to a specific mailbox on the server started getting returned as undeliverable with the message:
#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionCallFailed..."
I assumed that the event log messages and the delivery errors were related so I ran "eseutil /d" on the database but it exited with the message, "Operation terminated with error -1605 (JET_errKeyDuplicate, Illegal duplicate key) after 76.578 seconds. Running
eseutil /mh reports the database state as clean shutdown.
The Exchange database had been backed up nightly using Windows Server 2008 Backup. I restored the latest backup of the .edb file. Unfortunately, the corruption behind the bad page link error seemingly had propagated through the backups because the restored
.edb file had the same issues.
I then attempted to create a new clean database with the goal of then transferring mailbox data from the old to the new as described in the article "Simplifying the Dial Tone Database Recovery Process in Exchange 2007" (http://blogs.technet.com/b/dhardin/archive/2009/08/25/simplifying-the-dial-tone-database-recovery-process-in-exchange-2007.aspx).
I successfully created the new storage group and database with empty instances of all mailboxes but attempts to mount the old database yield this message:
Error: Exchange is unable to mount the database that you specified. Specified database: FASTMAIL\NewStorageGroup\Mailbox Database; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-344)
I then tried to return to the initial state of having a corrupted database but one that would at least function temporarily for all but the one broken mailbox. The idea would be to instruct individual users to run the Outlook archive command to back their
messages up locally into .pst files. Unfortunately, all attempts to mount the original .edb file yield the same MapiExceptionCallFailed error. I also tried to mount the database after deleting the transaction log files.
I searched the web for information on this error. There are some pages describing similar errors such as "hr=0x80004005, ec=2417" but I could not find any for "ec=-344". Some articles recommend running IsInteg.exe but this utility only works for databases
that are already mounted and I am unable to mount the database.
The Exchange server is running again using the empty database so that the users can at least send and receive mail. I get the sinking feeling that all hope is lost and the historical mail data that was stored on the server is gone for good. Before I face
the pitchforks of the angry mob, I figured that I would at least post an inquiry on an Exchange-related forum.
Are there any other steps I should take to try to recover the old data?

have you checked the health of the database using eseutil /mh "edbfilename.edb" ?
is the state: Clean Shutdown ?
If it is in clean shutdown state, then move the old logs, chk, .jrs files and select the option "This database can be overwritten by a restore" and mount the database.
In case if your database is not in clean shutdown state then you would need to work towards getting the database to clean shutdown using any of the following strategies based on the criteria that the database is affected with !
1. soft recovery
2. Hard Recovery
3. Hard repair
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
Information is provided is "AS IS" and confers NO Rights!!

Export Mailbox from Exchange 2010 and Import to Exchange 2007

Hello,
I exported mailbox (1GB in size) from Exchange 2010 to *.pst file; I need to import it into
Exchange 2007 mailbox. Is it supported ?
The operation completed successfully (no errors) but no items were imported; is it due to unsupported backward compatibility or some other issue ?
Thank you,
Luca
Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

I also have the same issue. Exported mailboxes on Exchange 2010 SP3 latest updates using
New-MailboxExportRequest and then tried to import into mailbox on Exchange 2007 SP3 with latest updates. The 32-bit client machine used for the import has Outlook 2010 SP1 (SP2 and later updates causes a different error). I used Outlook 2010 because the E2K10
New-MailboxExportRequest documentation states that you have to use Outlook 2010 or later. The PST files created can be opened and imported via Outlook but not with the
Import-Mailbox cmdlet (with no error as stated in this thread). Other PSTs, not created from E2K10 export do import just fine. I also ran ScanPST.exe against the exported PST and then ran the import again and it worked, everything got imported. Interestingly
the test mailbox PST file I was using was 761 KB but after the ScanPST it was 1,257 KB - must be some difference in the PST format that the Import-Mailbox cmdlet can't deal with.
Does anyone have any other solutions or
workarounds to this. I've got over 900 mailboxes I need this for due to an
acquisition? Has anyone tried using Outlook 2013 on the machine used for doing
the Exchange 2007 imports or does Outlook 2013 also have the same issue as later versions of Outlook 2010 (Exchange Mailbox import failed with error code 2147221233)?

Exchange 2007 to Exchange 2013 Mailbox Migration (moved twice)

I have an Exchange 2007 mailbox that I migrated to Exchange 2013 and works fine. I migrated it back to Exchange 2007 and still works fine during coexistence with Exchange 2013. I try to migrate the mailbox back to Exchange 2013 and now it won't open in
Outlook 2007. It says disconnected when it's trying to connect. I can't figure out what's causing this.

Hi,
According to your description, I understand that all mail client works fine after migrate mailbox form Exchange 2007 to Exchange 2013, however Outlook 2007 cannot connect to Exchange server when mailbox moved to Exchange 2007 then move back to Exchange 2013
If I misunderstand your concern, please do not hesitate to let me know.
Basis on previous steps testing, the mailbox and mailbox database is available in Exchange server. How about another computer with same Outlook version and problematic account?
If it works in another client, please open Control Panel\User Accounts\Credential Manager in problematic computer, then clear the remains credential and try again.
This issue may be related to the connection between Outlook and Exchange server, please click “Send/Receive All Folders” or “Update Folder” to update data. Also, run Test E-mail AutoConfiguration and Outlook Connection Status with problematic account to
narrow down issue. Please post relevant error message, it’s more helpful for further troubleshooting.
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

Mailboxes are moved to Exchange 2007 but still appearing in exchange 2003 With Red Cross

Hello,
I am moving mail boxes from exchange 2003 to exchange 2007 sp1. Excahnge 2007. After the mailboxes
are moved successfully to exchange 2007 i can still see some mailboxes in exchange 2003 with red mark on them. Please check the attached snapshot.
http://www.arabitpro.com

Followed this Kb article and finished
http://support.microsoft.com/kb/930363
http://www.arabitpro.com

Filter Mailbox database by size in Exchange 2007

Similar Messages

Maybe you are looking for