Microsoft Exchange
I will be putting notes about my Exchange configuration here.
Contents |
Anti-Spam
Install Anti-Spam Agent on Hub Transport Server
Open the Exchange Management Shell.
cd "\Program Files\Microsoft\Exchange Server\Scripts" .\install-antispamagents.ps1
Configuring Anti-Spam Settings
Start/Stop Scripts
Shutdown
net stop msexchangeadtopology /y net stop msftesql-exchange /y net stop msexchangeis /y net stop msexchangesa /y net stop iisadmin /y
Start up
net start "World Wide Web Publishing Service" net start "Microsoft Exchange Information Store" net start "Microsoft Exchange System Attendant" net start "Microsoft Search (Exchange)" net start "Microsoft Exchange Information Store" net start "Microsoft Exchange Unified Messaging" net start "Microsoft Exchange Transport Log Search" net start "Microsoft Exchange Transport" net start "Microsoft Exchange Service Host" net start "Microsoft Exchange Search Indexer" net start "Microsoft Exchange Replication Service" net start "Microsoft Exchange Mail Submission" net start "Microsoft Exchange Mailbox Assistants" net start "Microsoft Exchange File Distribution" net start "Microsoft Exchange EdgeSync" net start "Microsoft Exchange Anti-spam Update"
Cross-Org Mailbox Moves
Get-Mailbox
To confirm everything is set up correctly for communication between the servers, domains, and forests, you can use Get-Mailbox as follows:
$s = Get-Credential Get-Mailbox ` -DomainController 'old-server.old-domain.local' ` -Credential $s ` -database 'old-server.old-domain.local\First Storage Group\Mailbox Database'
If the source domain cannot be reached, it is likely a DNS issue. You can temporarily change the network adapter's DNS settings as necessary.
Move-Mailbox
This will only determine whether a move is possible.
When asked for login credentials (triggered by Get-Credential) enter the username and password for the old (source) server, e.g., old-domain.local\Administrator and your password.
Note that you only need to set $s with the credentials once per PowerShell session.
$s = Get-Credential Move-Mailbox ` -TargetDatabase 'new-server.new-domain.local\First Storage Group\Mailbox Database' ` -Identity 'mailbox-name' ` -SourceForestGlobalCatalog 'old-server.old-domain.local' ` -GlobalCatalog 'new-server.new-domain.local' ` -DomainController 'new-server.new-domain.local' ` -SourceForestCredential $s ` -NTAccountOU 'CN=Users,DC=new-domain,DC=local' ` -SourceMailboxCleanupOptions DeleteSourceNTAccount ` -ValidateOnly
Remove -ValidateOnly to actually perform the move.
In order to delete the source mailbox (as specified by -SourceMailboxCleanupOptions DeleteSourceNTAccount) the AD user account must be disabled on the source server.
For many mailboxes, it would be beneficial to use multiple threads and to pipe the data from Get-Mailbox into Move-Mailbox. This is described in full at the following URL:
Exchange 2007 Cross Org Mailbox Migration
RPC over HTTP
Exchange & Server setup
SSL Certificate
Coming soon...
Exchange
Coming soon...
Outlook setup
Mailbox Merge Wizard
This apparently allows you to convert between Exchange and Outlook PST files.
Certificates
Also, it has been necessary for me to restart Outlook after applying a new certificate. Outlook may show "All folders are up to date" but a restart is still necessary.
OWA
OWA showing a blank page on Exchange 2010
Recreate the OWA directories
Get-OwaVirtualDirectory -server server-name | ? {$_.OwaVersion -eq "Exchange2010"} | remove-owavirtualdirectory -domaincontroller server-name
New-OwaVirtualDirectory -DomainController server-name
