Exchange 2010, Powershell and Outlook

Configure Exchange 2010 Remote Administration
You're gonna do some funky stuff with your PC so follow the instructions diligently!

Config Exchange 2010 remote admin

Powershell Popular Snap-ins

PoSh-Snap good list of snapins that could prove to be damn handy!!!

Get Mailbox Permissions

get-mailboxpermission -identity "username" | format-list user,accessrights

Add an account to a mailbox

add-mailboxpermission -identity mailboxtobemanaged -user emailaddrusertobeadded -accessrights fullaccess {access level}

List Disconnected Mailboxes

get-mailboxserver | get-mailboxstatistics | where{$_.disconnectdate -ne $null} |format-table displayname,originatingserver

Poisoned Mailboxes & Quarantining

Oh this is kind of a self monitoring thing Exchange 2010 does and it takes down mailboxes that could hang Exchange...here is a good read on the subject....

Poisoned Mailboxes Exchange2010

And more from Microsoft

How to check for a poisoned Mailbox...use the Powershell Exchange Console on an Exchange box. Type

Get-MailboxStatistics –identity "Malboxtobetested" | FL Isquarantined

List Mailbox Rules

Get-inboxrule -mailbox mailboxname | select,name,description | format-list

Out Of Office Notifications

Check the status of the autoreply

get-mailautoreplyconfiguration -identity email.address@domain.name

Disable the out of office

set-mailautoreplyconfiguration - identity email.address@domain.name -autoreplystate disabled

Tracking Emails

Good couple of links on this subject

Intro Email Tracking

Search Exchange tracking Logs

The command I used was this

Get-MessageTrackingLog -Sender Senderaddr@SomePunter.com -Recipients recieveraddr@external.somepunter.com | fl serverhostname,service,eventid,messagesubject,timestamp

You should get a response similar to this

ServerHostname : Exchange.Sompunter.com
EventId : RECEIVE
MessageSubject : RE: FW: REPRINTING ORDER
Timestamp : 24/06/2014 16:16:57

ServerHostname : Exchange.Sompunter.com
EventId : RECEIVE
MessageSubject : Test
Timestamp : 08/07/2014 12:29:18

ServerHostname : Exchange.Sompunter.com
EventId : RECEIVE
MessageSubject : test
Timestamp : 08/07/2014 15:31:59

ServerHostname Exchange.Sompunter.com
EventId : TRANSFER
MessageSubject : test
Timestamp : 08/07/2014 15:31:59


ServerHostname : thirdparty.vendor.emailsecurity.cluster
EventId : SEND
MessageSubject : test
Timestamp : 08/07/2014 15:32:00

Soon as you see the email hit the thirdparty.vendor.emailsecurity.cluster the email has left your network.
Proof it has been sent internally just use the internal sender and reciever email addresses and you get something like this

ServerHostname : Exchange.Sompunter.com
EventId : RECEIVE
MessageSubject : Systems list probably out of date
Timestamp : 08/07/2014 12:35:38

ServerHostname : Exchange.Sompunter.com
EventId : DELIVER
MessageSubject : Systems list probably out of date
Timestamp : 08/07/2014 12:35:38

ServerHostname :Exchange.Sompunter.com
EventId : RECEIVE
MessageSubject : Systems list probably out of date
Timestamp : 08/07/2014 12:35:38

ServerHostname :Exchange.Sompunter.com
EventId : DELIVER
MessageSubject : Systems list probably out of date
Timestamp : 08/07/2014 12:35:38

Job Done!!

Outlook 2010
Autoreplies not working? You may have to do some funky stuff to test from the Outlook client and test the exchange Auto Discovery.

Debug Autoreplies

Exchange 2010 Autodiscovery
A good 2 part Article

Part 1    Part 2

Removing Email Addr Office 365
Found this, thought it might be useful, Email addr removal Office 365

Exchange Client Access Server

Microsoft Installation Guide

Outlook Certificate Warning
So I tell the Project Manager "If you are rolling out Win7 we need to do stuff to prepare the infrastructure, mind it is not just an OS you are rolling out it's a whole new client environment with a different email and desktop publishing apps, there will be training issues and Outlook 2010 connecting to an Exchange 2010 server will behave differently to the current email app, and I've not even touched printing yet" all I got was a blank stare back...not what he was wanting to hear. PMs dont get me started.

Anyway we are forced in to a tight schedule and the support calls start coming in, Outlook flashes up all these security warnings...we need the Exchange environment to be secured with new Certs....read this...

Outlook Certificate Warning