Office 365 Advantages (not found in your typical ads)

I am going to outline some advantages available to current Exchange users that migrate to Office 365.

  • If you have Exchange on premise, it is fairly easy to setup a hybrid environment. This means you can have some users with mailboxes on premise and some mailboxes in Office 365 and your end uses experience seamless communication.
  • Users in the cloud see the same address book as users on premise.
  • Users logon to Office 365 using their email address as their logon name and the SAME password as they do on premise.
  • Hybrid configuration allows mail flow between on premise and cloud users to be seen as internal (SCL = -1) if you understand that.
  • Hybrid allows free/busy lookups between on premise and Office 365 to work when creating a meeting.
  • When mailboxes are moved to the cloud, the Outlook client re-configures itself using the autodiscover service and the same profile is used. This means the Outlook OST file does not need to be rebuilt.
  • Mailbox moves can be ramped up to 99% and held there. When you, the admin clicks “finish migration”, the mailbox move is completed within 10 mins or less and the Outlook client is prompted to restart. This allows you control over when the mailbox is migrated. Very important for those “high touch” end users.
  • Phones experience the same automatic reconfiguration as the Outlook client.

Other advantages in going to Office 365 with the E3 or E4 licenses.

  • 50 GB mailboxes with Unlimited Archive mailboxes.
  • An extremely fast installation of Office 2013 (Word, Excel, Powerpoint, etc) that is branded Office 365. We call this a click to run install.
  • Up to 5 installations per user of this version of Office. The license is tied to the user’s Office 365 credentials, so the end user can install Office at home, and when they are no longer with the company, their license expires. No more handing out CDs with the product key written on it with a sharpie (Hoping their kids won’t get a hold of it.)
  • OneDrive with UNLIMITED storage; OneDrive is built into Windows 8.1 and Windows 10
  • Continuous updates to Office 365 online portal (you may know this as OWA) allowing you to take advantage of the latest features without any effort from you, the administrator.
  • High Availability that would cost way more if you tried to implement on premise.
  • The administrator will never have to worry about backups again.
  • End to end encryption is available without having to install an additional appliance such as ZixGateway or Entrust appliance.
  • Ability to keep all mail with “in place hold” feature for a desired duration (such as 7 years), including deleted mail which does NOT affect the 50 GB mailbox quota.
  • The ability to link URLs (Web addresses) that point to large files stored in your OneDrive rather than using traditional attachments. Can’t attach that 100 megabyte powerpoint or visio document? No problem with OneDrive linking.

I haven’t touched on ALL the advantages, but hopefully this will give you some technical insight to the advantages of migrating to Office 365. In future posts, I will go deeper into these advantages.

Office-365-664x374

Advertisements

Disable outbound TLS on Exchange 2007

The outbound send connector on Exchange 2007 will try to establish TLS with the other side (if the other side asks). To disable outbound TLS on send connector, perform this powershell command:
set-sendconnector -IgnoreSTARTTLS:$true
If there are multiple send connectors then and you want to disable TLS on all of them.
Then do this
Get-sendconnector| set-sendconnector -IgnoreSTARTTLS:$true
I had a customer that routed the outbound ip address of the exchange smtp to match their inbound spam appliance, then the certificate did not have a name that matched the host name.
The easiest solution was to disable TLS.
The other solution was to add another name to the certificate

OAB to fail on "outlook anywhere clients"

Consider the following
You setup a client as an outlook anywhere client. sending and receivng mail works, autodiscover worked fine, it found the user account and properly setup the user, but you can’t get the client to download the offline address book via web.
The server side had “publish oab via web” enabled, but it won’t work.

Go into your email policy, change the @company.dom to alias or whatever you use, such as cn@company.com. You don’t have to apply the policy, it just can’t contain blank space before the @ sign.

see
http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/af8e769e-0718-488d-a24a-7b2ddbbfb0ee/
frigging bizarre

RPC Proxy problems Windows 2008 / Exchange 2007

In short, RPC Proxy, and IPv6 on Windows server 2008 has some “issues”.

This only occurs when you have Exchange installed on Windows 2008, not Windows 2003.
This also only applies to a "all roles installed on same server”. For my situation, this was a single exchange server installation.

The rpc proxy component is not compatible with IPv6, and even if you have it disabled (uncheck the ipv6 on the nic settings), it still uses the loopback component.

From the msexchange.org team, we find this:

If you’re in a single-server scenario where the RPCProxy and Mailbox are on the same machine, then the above does not work since the loopback interface still uses IPv6. In this case, you need to make the following changes in the system32\drivers\etc\hosts file:

  1. Comment out the line ":::1    localhost"
  2. Add the following two lines:
       <IPv4 address>    <hostname of the computer>
       <IPv4 address>    <FQDN of the computer>

When I tried the “rpcping” command (see the above link for how to), on port 6004, it gave me an error of Exception 1722 Port 6001 and 6002 worked ok. It is normal for the command to ask you passwords twice, and you can’t mess up and use the backspace key. You have to type it correct both times.

Also I noticed that the rpc proxy ports were wrong in the registry. The Valid Ports entry  was set to servername:593;servername:49152-65535 instead of
servername:6001-6002;servername:6004;servername.domain.ad:6001-6002;servername.domain.ad:6004
Honestly, I don’t know if those registry settings were bad or not, but I changed them to 6001-6002 and 6004.

I also tried uninstalling rpc over http, reboot server, and reinstalling rpc over http, but that did not fix it.

There is a good article related to this also at Exchange Genie.

And to clarify, I do have Exchange 2007, sp1, with rollup 5 installed. And Windows 2008 with SP1.