Exchange 2007 Search Export-Mailbox AND OPERATOR

I am looking to do a search for keywords using Export-Mailbox cmdlet. It seems like there is no way to do a AND search for two keywords (For example "BUDGET" AND "FINANCE").
It seems like the only way we could get partial results would be to put both the keywords in quotes as s ingle keyword with a space (for example "BUDGET FINANCE"). But this doesnt serve the purpose.
I have tried to use Outlook Instant Search / Search folders and OWA search but all yeild different results as it seems like the search function is not consistent across all these 3 features.
For example, the search folders it seems like do not search in the content (attachments) but Outlook online mode folder does / OWA does search etc. / I am not able to search in online folders using Outlok as this is a journal mailbox and has 500K messages
with managed folders and there does not seem to be a way to narrow down the saerch only in a specific folder and its subfolders.
Has any body else come across a situation to do a discovery for keywords with an AND operator ? Is there a way to do this using native tools?
TIA
Prakash

So, you want to do the phrase searching for “BUDGET FINANCE”, not the multiple keywords that spread in a mail?
Which cmdlet line do you use to perform the search?
“You can specify keywords and phrases to search message content. You can also use the logical operators AND, OR, and NOT”
----------Refer to <Exchange
2010: Understanding Multi-Mailbox Search>
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact [email protected]

Similar Messages

Exchange 2007 - User's mailbox disappeared in EMC but they can still send and receive email

We have a user that was complaining about not being in the address book anymore. After I did a little rooting around in management console I noticed that their mailbox was no longer listed under Recipient Configuration -> Mailbox, but what's weirder
is I can do a search and find her listed in the results - at which point I can right-click her name and do everything I normally can with no problem. Listing all of the mailboxes with PS shows her still there too. As far as I know, she is the only user
having this problem.
She can send and receive email just fine, but like I said, she is no longer in the global address list so other users have trouble sending her stuff. At her computer, I tried repairing her email (under account settings) but the process would fail when
searching for her settings. I don't know if this is a stupid thing to add, but I did run Clean-MailboxDatabase on our first storage group to see if her mailbox had been deleted or disconnected or whatnot but nothing is currently showing up in Recipient
Configuration -> Disconnected Mailbox.
Some info on our setup:
Exchange 2007 on Windows Server 2003r2
AD is on Windows Server 2008r2
Her computer is running Outlook 2010
I did restart our Exchange server 2 days ago to update VMWare tools, but no Windows updates were installed. She couldn't tell me exactly when this problem started, but it was more-than-likely in the last couple of days as she was recently married and
I had to change her name in AD and Exchange - so everything was confirmed 100% functioning 2-3 weeks ago.
I'm at a lost for what the issue could be, but then again Exchange isn't exactly my forte, so any help would be much appreciated.

First things first - is her mailbox hidden from address lists? Run
Get-Mailbox <alias> | Fl HiddenFromAddressListsEnabled to find out. It probably isn't, but we need to clear this, just in case.
Now, assuming it is not hidden, have you searched for both her maiden and married names in your directory? Often, when the name on a mailbox is changed, the display name is not - and vice versa. Also, has her email address also changed?
If so, has a secondary proxy address been added to reflect her maiden name? I'd do this, just to be sure things aren't lost that should be delivered to her.
I can't think of anything else obvious right now. After you've checked these things, get back to us with their results.

Exchange 2007 (sbs) export maiol contacts and distrubution lists an import in to Exchange 2010 (sbs)

Hello, I have a server running SBS2008 with exchange 2007.
I need to export all Mail Contacts, only need to export Dispaly Name, Alias and External email address.
I then need to import them into my new server running exchange 2010
Then i need to to dthe same with the distrubuition lists and add the contacts inoot the relavant groups.
Does anybody know if this is possible please, if so can anybody help me?

Hi
Perhaps you can export to a csv and then import from the .csv in exchange 2010?
Hope this helps. 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.

OWA still redirects to Exchange 2007 (legacy) after mailbox-move to Exchange 2013

Hi,
I am in the process of implementing Exchange 2013 in coex with 2007. I am testing now in a copy of the production environment and have installed the Exchange 2007 SP3 RU11 prior to installing Exchange 2013 using the SP1 media.
We use a wildcard certificate and I prepared the Exchange 2007 internal/external URLs for OWA/OAB/etc to use the legacy.domain.com names and in Exchange 2013 I set them all to email.domain.com. Exchange 2013 has Outlook Anywhere configured.
All tests like autodiscover (internally via SCP) run fine and for a new Exchange 2013 mailbox the Outlook and OWA functionality is as expected. A mailbox still on 2007 also connects fine via Outlook and while connecting to OWA (using the htps://email.domain.com/owa
url) also redirects me to https://legacy.domain.com/owa just fine.
HOWEVER: after a successfull mailbox-move from 2007 to 2013 my OWA logon-request STILL get's redirected to the 2007 legacy URL. When I then logon again on the 2007 OWA I get the message that I should connect to the 2013 URL and end-up in a loop.
Anyone any tips where to search?
Many thanks in advance.
Best regards and many thanks in advance, Eric Vegter

This seems to be an outstanding issue.
We just performed a fresh install of Exchange 2013 on a Windows Server 2012 R2 operating system. We're migrating from our existing Exchange 2007 server. At the moment we have everything properly setup in a co-existence state. All we lack is to complete the
migration of our mailboxes from the 2007 DB to the 2013 DB.
In performing the first mailbox move, to test the migration process and make certain mail flows as expected, we noticed this same problem. Before reading through this thread, I was able to assign Full Access to a delegate user and then perform the "Open
Mailbox" feature from a 2013 user's account. This was successful in opening the mailbox within OWA 2013. However, I still could not access the account by simply logging into the Outlook Web App. It would login, then proxy back to OWA 2007 with the message,
"Use the following link to open this mailbox with optimal performance:
http://mail.domainname.com/"
After reading about cycling the OWA app pool, I immediately tried it as a workaround and it worked. It is a little frustrating going about it in this way. Hoping to see more activity on this thread.
-Lorne

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

Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2007 cannot export pst files via its powershell

Hi,
I am trying to export pst files from Exchange server 2007.
This script used to work perfectly.
Export-Mailbox -Identity paddy -PSTFolderpath C:\pst\
But now I am getting an error message saying this
Export-Mailbox : The specified mailbox database "SRV03\First Storage Group\Mail
box Database" does not exist.
At line:1 char:15
+ Export-Mailbox <<<< -identity paddy -PSTFolderPath C:\pst\
MoveType                         : ExportToPST
MoveStage                        : Initialization
StartTime                        : 01/01/0001 12:00:00 AM
EndTime                          : 01/01/0001 12:00:00 AM
StatusCode                       : -2147467259
StatusMessage                    : The specified mailbox database "SRV03\First
                                   Storage Group\Mailbox Database" does not exi
                                   st.
ReportFile                       : C:\Program Files\Microsoft\Exchange Server\L
                                   ogging\MigrationLogs\export-Mailbox20140527-
                                   155543-8040336.xml
what would be the problem?
I checked that the account has full permission so permission would not be the issue.
Thanks

Hi,
First, please check if the mailbox database mentioned in the error message is mounted.
Besides, please check if you can export other mailbox using the Export-Mailbox cmdlet.
If all mailbox are affected, please check if you have the Exchange Server Administrator role assigned.
1. Open EMC.
2. Select the Organization Configuration node from the console tree.
3. Please check the permissions assigned in the result pane. If there is no the Exchange Server Administrator role, please add it to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2007 servers reports mailbox size full, but mailbox shows empty in OWA or Outlook.

When the users log into their mailboxes in OWA or Outlook get this warning: "You have exceeded your limit quota and can not send or receive mail" but really they have the mailbox empty, there's nothing in calendar, folders or deleted items.
I ran this command Get-MailboxStatistics and the mailbox reports for example 500 MB.
I deleted the deleted items and I configured deleted items retention to 0 days to ensure that it wasn't the problem, but the servers still reporting the same mailbox size (500 MB).
This happen to some mailboxes, not all
Please help, what can I do?

1. How many Exchange 2007 servers do you have?
2. What service pack and rollups are installed on the Exchange 2007 server(s)?
3. If you have more than one server, are you using any form of replication: LCR, SCR, CCR... etc. ?
4. What 3rd party software is installed on the Exchange 2007 server(s)? For example, antivirus, archiving, etc.
5. Can you confirm that this happens in OWA as well? I see you mentioned OWA but I've just glanced at another problem with incorrect folder size being indicated in Outlook and it apparently had to do with the .OST file. Of course, if the problem occurs with
OWA as well, then the OST file would not come into play. Sorry to insist on that but I'm trying to rule some things out, if possible (like 3rd party apps, maybe something with replication, maybe a problem that was corrected in a service pack or rollup).
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.

Exporting mailboxes and addresses to entourage

HELP! Yesterday Entourage crashed & i've lost all data and had to re-install. Fortunately, have backed up a lot of stuff in Mail. But I can't export it back to entourage. I've tried changing .emlx to .eml. Entourage still won't recognise it. Any other suggestions? IF I resolve this, I shall abandon Entourage forever!!

This ought to get you started:
From:
http://www.entourage.mvps.org/import_export/another.html
"Pre-Tiger versions of Apple Mail.app can be imported with Entourage's importer. However, starting with Tiger, Apple modified the way Mail stores its email messages. In pre-Tiger versions, Mail stored its messages in standard .mbox files; however, to enable Tiger's Spotlight to search them, Mail now stores its messages individually as .emlx files, which can be found in
<your user name>/Library/Mail/<name of the account>/<name of the folder>/Messages.
Entourage 2004 was released roughly a year before Tiger came out consequently, it doesn't take into consideration the changes that were made in Tiger. This explains why the import function does not recognize .emlx files.
To change Tiger Mail.app messages from .emlx to .eml files see these instructions:"
http://www.entourage.mvps.org/import_export/convertemlx.html

Exchange 2007 - restored (merged) Mailboxes - Problem with items in Outlook

Hey guys,
last week we had to restore and merge our Exchange Mailbox Database. We had a running Database with data until Oct 14 and merged a recent backup into the User Mailboxes.
Some mailboxes didn´t have problems, others have from then on doublicated Mails, Calendar Items, Tasks, ... even deleted/renamed folders appear now again WITH email content.
I don´t understand what happend there and if I can do something.
Hope someone could help me!
Regards

Hi,
According your post, I understand that some mailbox contain duplicate items after restore and merge mailbox.
If I misunderstand your concern, please do not hesitate to let me know.
Are you run Restore-Mailbox with AllowDuplicates parameter? Please double check in OWA.
Besides, please run below command to check the structure of mailbox folder:
MailboxFolderStatistics “identity” | Select Name,FolderSize,FolderAndSubfolderSize
If the issue only occur on Outlook client side, please run Outlook with online mode or reconfigure a new profile for testing.
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

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

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

Exchange 2007 SP3 Search Problems

I reset all the search indices on my mailbox databases. Event viewer has told me the crawl is complete and everything checks out when I do “test-exchangeSearch”
from PS. However, the index folders are considerably smaller than the original ones, (1.3GB vs 7GB) and only about 1% of database size. Multiple users can prove to me that searches are incomplete and not returning reliable results when just doing basic folder
searches from Outlook 2007. help!
Ian

After speaking with a senior MS Engineer, if you already have SP3 applied and tried to reinstall the search as I outlined above, you have corrupt your Exchange install and the ONLY option is to rebuild the box. After reinstalling Windows and Exchange, the
proper procedure to get search working perfectly is outlined below:
4. If you haven’t already,
upgrade toExchange Server 2007 Service Pack 3.
Exchange 2007 SP3 includes several major Search-related fixes and upgrades MSSearch 3.0 to MSSearch 3.1. This is a highly significant
upgrade.
5. Update to the latest available Rollup Update.
There are some very significant search fixes in the Rollup Updates for Exchange 2007 SP3. Some of these fixes are absolutely essential to install.
For example, Exchange 2007 SP3 Rollup Update 2 includes a fix that allows Exchange server to index emails even when the attachment cannot
be parsed – this is the number one call generator for Exchange 2007 search support cases.
To restate, upgrade to the very latest available Exchange 2007 SP3 rollup update, as there are many more search fixes available in the latest
rollup updates.
6.
Install IFilters and register them – follow ALL the steps below.
Install Filter Pack 1.0, which allows Exchange 2007 to index Office 2007 documents:
2007 Office System Converter: Microsoft Filter Pack
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20109
7. Install the hotfix which addresses a known issue when search crawls a .vsd file.
960502 Description of the 2007 Office system hotfix package (Offfiltx.msp, Visfilter.msp): December 16, 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960502
Additional Information on the hotfix:
960166 Error message when a search process crawls a .vsd file on a Windows 64-bit operating system that is running the 2007 Office Filter
Pack: "The filtering process has been terminated"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;960166
8.
Register the Filter Pack 1.0 IFilters. This is a manual process with Exchange 2007 but we have created a script to automate the process.:
944516 How to register Filter Pack IFilters with Exchange Server 2007
http://support.microsoft.com/default.aspx?scid=kb;EN-US;944516
9. Install Filter Pack 2.0 which allows Exchange to index Office 2010 attachments as well as some additional file types.
Download details: Microsoft Office 2010 Filter Packs
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5CD4DCD7-D3E6-4970-875E-ABA93459FBEE&displaylang=en
10. Register IFilters 2.0 with Exchange 2007.
How to Register IFilters 2.0 with Exchange 2007 and Exchange 2010
http://technet.microsoft.com/en-us/library/ff354976(EXCHG.80).aspx
11. Disable signature verification for the Exchange 2007 search services by putting 127.0.0.1 crl.microsoft.com in the HOSTS file.
Certificate Revocation List
When the Microsoft .NET Framework 2.0 loads a managed assembly, the managed assembly calls the CryptoAPI function to verify the Authenticode signature
on the assembly files. The CryptoAPI function checks a Certificate Revocation List
(CRL) that is available at http://crl.microsoft.com
. This action requires an Internet connection.
The
Microsoft Search Indexer service (Microsoft.Exchange.Search.ExSearch.exe)
is a managed assembly that is loaded by Microsoft .NET Framework 2.0. After installing Exchange 2007 SP3, if the Exchange server or DNS cannot resolve
http://crl.microsoft.com for any reason
the outgoing HTTP requests may be dropped and an error message is not returned. This delay causes the CRL to time out and cached CRLs will expire. This affects the Microsoft Search Indexer service in such a way that any new email fails to be indexed.
Instructions to Modify HOSTS file on the Exchange 2007 Server
Add the following:
127.0.0.1 crl.microsoft.com – here are the instructions:
a. Go Start – Programs and choose Command Prompt and choose Run as Administrator.
b. Within the Command Prompt, change to this directory (the drive will be the one where you installed the OS):
C:\Windows\System32\drivers\etc\hosts
c. Add the following entry to the HOSTS file:
127.0.0.1 crl.microsoft.com
d. Save the HOSTS file.
13.
Rebuild Indexes
using ResetSearchIndexes.ps1
How to Rebuild the Full-Text Index Catalog
http://technet.microsoft.com/en-us/library/aa995966(EXCHG.80).aspx
a. Go Start – Programs and choose Exchange Management Shell and choose Run as Administrator.
b. Change to this directory (the drive will be the one where you installed Exchange 2007):
C:\Program Files\Microsoft\Exchange Server\Scripts
c. It is suggested that you rebuild indexes for one or a few databases at a time – use the following command to rebuild the indexes for 1
databases called dbname1 and dbname2:
.\ResetSearchIndex.ps1 –force dbname1 dbname2
d. It is suggested not to run the following command unless you have 1 Exchange 2007 server only in your environment because it will cause
all databases on all Exchange 2007 (and all Exchange 2010 servers, if there are any) to be reindexed at that same time:
.\ResetSearchIndex.ps1 –force all
14.
Monitor the Application Event Log for Event ID 110 for a particular database.
This will indicate the new index is complete for that database.
15. After receiving Event ID 110 for a database, check to see if the size of the CatalogData folder for that database is the expected
5% to 10% of the database size. If the size of the CatalogData folder is significantly smaller than that or if the size is a few kb or a few mb, go
to Step 17.
16. After you have received Event ID 110 and the size of the CatalogData folder is normal, test searching in Outlook online mode
and OWA to make sure search is working.
<strike>
</strike>
Ian

Office365 - Move Mailbox and Export to PST

Hi Everyone
So we have moved all our Mailboxes to Office365 and I am in the process of setting up our service desk checklists etc.
One issue that i have came across is that it is not possible to directly export mailboxes from Exchange Online to PST.
We are in a Hybrid Environment so it is still possible to migrate mailboxes off to a local Mailbox Server and export from there.
In order to streamline this as much as possible i have written the following (UnTested!) script. I will be using it from the Azure Powershell Module already connected to our online tenant and so that section of code has been removed.
If anyone had any thoughts in regards to this - or can point out any glaringly obvious mistakes that would be great!
#Script to Move User MailBox from Exchange Online to OnPrem and Export To PST
#Created By: Joe McGrath
#Created On: 17/12/2013
#Mailbox move
$OnpremCred=get-credential
$User= Read-Host 'Enter the username of the user'
new-moverequest -identity $User -OutBound -RemoteTargetDatabase 'YOURDB' -RemoteHostName ‘mail.YOURDOMAIN.com’ -RemoteCredential $OnpremCred -TargetDeliveryDomain ‘YOURDOMAIN.com’
#The Next Section Checks the Status of the move every 60 seconds
$MoveStatus=""
$MoveStatus = Get-MoveRequest -Identity $User
do
    Start-Sleep -Seconds 60
    $MoveStatus = Get-MoveRequest -Identity $User
While ($MoveStatus.Status -ne 'Completed')
Write-Host "Mailbox Move Completed."
#When the Move has completed we now clear the move request
Remove-MoveRequest -identity $User
Write-Host "Move Request Cleared from System"
#This next section will carry out the Export to PST
#We need to call the Exchange 2010 Powershell cmdlets and connect to the On Premises Exchange Infrastructure to Export to PST
Write-host "Connecting to On Premises Exchange"
$ExchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "http://Server.YOURDOMAIN.local/PowerShell" -Credential $OnpremCred
Import-PSSession $ExchangeSession
$filePath='\\Server\Share\'
#This First Command Exports the Users Primary Mailbox to PST
Write-Host "Beginning Primary Mailbox Export to PST for "+$User
New-MailboxExportRequest -Mailbox $User -FilePath $filePath+$User+".pst"
$MailboxExportStatus=""
$MailboxExportStatus = Get-MailboxExportRequestStatistics -Identity $User
Do
    Start-Sleep -Seconds 60
    $MailboxExportStatus = Get-MailboxExportRequestStatistics -Identity $User
While ($MailboxExportStatus.Status -ne 'Completed')
Remove-MailboxExportRequest -Identity $User
Write-Host "The Primary Mailbox for "+$User+" Has been exported."
Write-Host "Exporting Archive Mailbox for "+$User
#This Command Exports the Users Archive to PST
Write-Host "Exporting Archive Mailbox for "+$User
New-MailboxExportRequest -Mailbox $User -IsArchive -FilePath $filePath+$User+"_Archive.pst"
$ArchiveExportStatus=""
$ArchiveExportStatus = Get-MailboxExportRequestStatistics -Identity $User
Do
    Start-Sleep -Seconds 60
    $ArchiveExportStatus = Get-MailboxExportRequestStatistics -Identity $User
While ($ArchiveExportStatus.Status -ne 'Completed')
Remove-MailboxExportRequest -Identity $User
Write-Host "The Archive Mailbox for "+$User+" Has been exported."
Remove-PSSession $ExchangeSession
Write-Host "User Mailbox has been Removed from Online and Archived to file"
Like I said this is not tested yet - I need an account to test with - after I manually migrate the data first :) - so use at your own risk etc

Hi,
You can not export the Office365 mailbox Data in to PST, you must have to bring the mailbox to on premises and then export, once done again move back the mailbox to office365,
another way is from in-place hold, search the mailbox and take users PST, or user third party tool such as messageops which is quite good.

Outlook 2010 and Exchange 2007. Outlook crashes when user opens it. Event ID 55, 100 and 3036

Hello,
We are running Exchange 2007 on our server and our user clients use Outlook 2010. One of my users is having the following issue. Whenever he opens Outlook 2010, it would crash and show this message: "Microsoft Outlook has stopped working. A problem
caused the program to stop working correctly. Please close the program". I tried recreating his Outlook profile and the issue persisted. I also tried to create his Outlook profile on a different computer and same message shows up. Both computers are domain
joined.
I checked Event Viewer both on his computer and the other computer I tried to set up his Outlook profile on. Both machines showed the same three error logs:
-First error log:
Log Name: Application
Source: Microsoft-Windows-Search
Date: 9/12/2014 12:34:16 PM
Event ID: 3036
Task Category: Gatherer
Level: Warning
Keywords: Classic
User: N/A
Computer: OSD-Assistant10
Description:
The content source <mapi://{S-1-5-21-3579767609-4209606035-2604604182-1235}/> cannot be accessed.
Context: Application, SystemIndex Catalog
Details:
No protocol handler is available. Install a protocol handler that can process this URL type. (HRESULT : 0x80040d37) (0x80040d37)
-Second Error log:
Log Name: Application
Source: Application Error
Date: 9/12/2014 12:34:13 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: OSD-Assistant10
Description:
Faulting application name: OUTLOOK.EXE, version: 14.0.7113.5000, time stamp: 0x527d636c
Faulting module name: OUTLOOK.EXE, version: 14.0.7113.5000, time stamp: 0x527d636c
Exception code: 0xc0000005
Fault offset: 0x00011c8a
Faulting process id: 0x8e0
Faulting application start time: 0x01cfceafa6be0255
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE
Report Id: 025ffc35-3aa3-11e4-bb89-001f2937f524
-Third Error log:
Log Name: Application
Source: Outlook
Date: 9/12/2014 12:34:10 PM
Event ID: 55
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: OSD-Assistant10
Description:
Calendar Folder New Download
This leads me to believe the problem has to do with his Exchange User Mailbox account. But I have no clue what could it be. He is the only user experiencing this problem.
Any help is greatly appreciated!! Thanks!

Hi,
Sorry for my delay. Have the issue been resolved?
If there are too many items in the problematic user's mailbox, please delete some and check whether the Outlook can be opened. Please uncheck Use Exchange Cached mode to use Online mode and confirm if the user can access the mailbox for Outlook.
Also try to connect to this user's maibox from your working machine with Outlook. Then check whether it works.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2007 Search Export-Mailbox AND OPERATOR

Similar Messages

Maybe you are looking for