Exchange 2007
Export and Import PST Files from the Exchange 2007 PowerShell
Must Setup Permission before creating pst files
Get-Mailbox -Database ’servername\Private Information Store (xxx_xxx)’ | Add-MailboxPermission -User administrator -AccessRights FullAccess
Export All Mailboxes to pst files. Get-Mailbox -Database ’servername\Private Information Store (xxx_xxx)’ | Export-Mailbox -PSTFolderPath E:\PSTs
Export Single user to PST file.
Export-Mailbox -Identity john@contoso.com -PSTFolderPath C:\PSTFiles\john.pst -BadItemLimit 9999
IMPORT All PST Files into Exchange.
(must run permission on for user to import, mailboxes in target server must be created before import.)
Get-Mailbox -Database ’servername\Private Information Store (xxx_xxx)’ | Import-Mailbox -PSTFolderPath E:\PSTs
DSQuery Primary Email Addresses command:
dsquery.exe * -limit 0 -filter “(&(objectCategory=person)(objectClass=user)(mail=*))” -attr name mail >PrimaryEmailAddresses.txt
Exchange 2007 OWA 440 Login Timeout
fix 440 Login timeout in Exchange 2007
REF:http://techrepublic.com.com/5208-6230-0.html?forumID=101&threadID=215256&messageID=2226713
here’s what i did to solve the problem on my server:
We have only one Exchange server (2007), so everything described here is made on the same machine.
a) In the Exchange management console, I copied all the properties of OWA.
Go to “server configuration\ClientAccess”, then pick up the correct server, then “OWA” tab, right click owa (default web site): properties . I had to restore them later on.
b) use the Exchange Management shell and run the following:
(please refer to http://technet.microsoft.com/en-us/library/aa998624.aspx for details)
1) Get-OwaVirtualDirectory -Server to check the settings
2) Remove-OwaVirtualDirectory -Identity to remove the existing virtual dir (only owa in this case, I didn’t touch the others)
3) New-OWAVirtualDirectory –Name “owa” (I only used the -name parameter, that worked for me)
c)Go back to the management console and restore properties of owa.
d) restart IIS via command iisreset /noforce
Web Outlook was running again after that.