Some Notes on the Machines

If one has one’s LAN Active Directory synchronized with EOL/Azure, one cannot add secondary email addresses in the EOL console. In this situation:

1. Open ADSIedit from the domain controller
2. Open up the OU containing the user
3. Open the Properties of the user
4. Open the Properties for the item “proxyAddresses”.
5. The primary (the “reply”) email address for the user needs to be specified thus, with caps in the prefix:
   SMTP:user@domain.xyz
6. Secondary email addresses for the user need to be specified thus, with lowercase prefix:
   smtp:alias@domain.xyz
7. Then run the sync or wait for the automatic run, and it’s done!

Also, as a bonus, after the above is done once, user objects in Active Directory Users and Computers get a new tab, “Attributes”, from which the above can be done for other users.

Here’s a great way to get one:

https://github.com/cunninghamp/Get-MailboxReport.ps1

When a business needs a truly public calendar simply editable by all, it is not clear what best to do in Exchange or especially Exchange Online. Shared mailboxes and room calendars look like they should do it but don’t. One way is to create an ordinary user mailbox and then give all users full delegation rights in Powershell:

Get-Mailbox | foreach-object { Add-MailboxPermission -Identity "Public Calendar" -User $_.SamAcc
ountName -AccessRights FullAccess }

The only catch is that this does require a license.

Try DavMail:

http://davmail.sourceforge.net

It runs in the background on server, desktop, or laptop (Windows, Linux, or Mac), and it translates native Exchange protocols into that which Thunderbird and appropriate add-ins handle very well. In other words, it acts as a live bridge between Exchange protocols and Thunderbird with Lightning, for contacts and calendar. The instructions are thorough and functional.

If your firewall lets you bypass data checks by FQDN, this works well; just import this into an alias and use that as the “To” for a rule called ExchangeOnline, for ports 80 and 443:

*.office.com
*.office365.com
*.office.net
*.onmicrosoft.com
*.microsoftonline.com
*.microsoft.com
*.live.com
*.windows.net
*.microsoftonline-p.com
*.microsoftonline-p.net
*.microsoftonlineimages.com
*.msecnd.net
*.msocdn.com
*.glbdns.microsoft.com
*.activedirectory.windowsazure.com
*.verisign.com
*.symcb.com
*.symcd.com
*.omniroot.com
*.geotrust.com
*.entrust.net
*.public-trust.com

The above is condensed from here. It includes only Exchange Online, there are some other items to be added for other Office 365 services including Skype etcetera.

To disable Rich Text Format, and eliminate WINMAIL.DAT transmission, in Exchange Online:

1. Log into https://outlook.office365.com
2. Click the 3×3 matrix at the upper-left, click Admin
3. Scroll down on the left side, open Admin if it’s not opened, click Exchange
4. Under the heading Mail Flow, click Remote Domains
5. Edit the item Default
6. set “Use rich-text format”, to Never.

In Exchange 2010:

1. Open the Exchange GUI console,
2. Open Organization Configuration, Hub Transport, and the Remote Domains tab.
3. Open the Properties of Default/*.
4. Browse to the Message Format tab.
5. Under “Exchange rich-text format”, choose “Never use”.

Here:

“https://technet.microsoft.com/en-us/library/Dn874017(v=EXCHG.150).aspx#PSTMigrate”

appears to be a method.

Procedure:

1. Run Exchange command shell as administrator.
2. Create one or more new export requests:
   New-MailboxExportRequest -Mailbox username -FilePath \\SERVER\SHARE\username.pst
3. Check status of export request(s) in progress:
   Get-MailboxExportRequest
4. Access PSTs after export is complete, at \\SERVER\SHARE.

Here is a GUI tool written in PowerShell:

http://community.office365.com/en-us/w/exchange/1712.aspx

Here’s a great rundown, three possible methods:

https://technet.microsoft.com/en-us/library/dn554323