Category: Office 365

Automatic upgrades to Office 2016
article #926, updated 524 days ago

Reportedly in February 2016, Microsoft began to automatically upgrade all Office 365 customers to version 2016. One has to search for the words “February” and “automatic” in the page below to see it:

https://support.microsoft.com/en-us/kb/3097292

Among many others, this can cause major problems for users of QuickBooks of all versions before 2016; all integration with Excel fails, and we can expect other problems (e.g., Outlook integration) as well. There is no easy revert procedure, we just have this:

https://community.office365.com/en-us/f/172/t/409681

There is a method to prevent the upgrade via Group Policy:

https://support.microsoft.com/en-us/kb/3097292

Categories:   Office 365   QuickBooks

==============

Windows Server Essentials integration with Office 365
article #916, updated 565 days ago

If it’s not working or not working well for you, try this:

  1. In the Dashboard, Disable Office 365 integration and Azure integration. It’s two separate steps. If you disable just Office 365 integration you won’t be able to continue.
  2. Set up Office 365 integration.
  3. See lots of interesting information come up quite quicly, in the Office 365 tab after you restart the Dashboard, to confirm that your integration is working very nicely.
  4. If it didn’t work well, open your firewall per Microsoft, and test again.

Categories:   Office 365   Servers

==============

Bypass firewall checking for Exchange Online data paths
article #899, updated 587 days ago

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.

Categories:   Exchange and Exchange Online   Office 365

==============

Connect to Office 365 via PowerShell
article #804, updated 630 days ago

Contributed by the excellent Matt Quick:

https://mattthequick.wordpress.com/2015/11/25/connect-to-office-365-via-powershell/

Categories:   Exchange and Exchange Online   Office 365

==============

Outlook Autodiscover After Migrating To Office 365 / Exchange Online
article #839, updated 744 days ago

After migrating all email accounts from an on-premises Exchange 2008 or later server to Exchange Online, there remains the problem of what to do about new Outlook profile creation. Outlook will still look for the old server name, and especially if you want to keep the old server alive for a while, you will have significant problems getting Outlook 2013 to do anything with Exchange Online. Here is what the extraordinary Matt Quick and I did recently with beautiful results.

For the sake of this discussion, “localdomain.local” is the LAN-local AD-enabled domain, and “publicdomain.pub” is the Internet domain. The on-prem Exchange originally had local DNS name “exchange.localdomain.local” and Internet DNS name “exchange.publicdomain.pub”.

  1. Migrated all mailboxes from on-premises Exchange 2010 to Exchange Online. Dirsync was used for initial account setup, then turned off for the actual copyover process which was done with MessageOps.
  2. In Exchange Management Shell, ran Get-ClientAccessServer to get the canonical name of on-prem Exchange (we’ll say it was EXCHANGENAME), and then Set-ClientAccessServer -Identity EXCHANGENAME -AutoDiscoverServiceInternalUri $NULL (replacing EXCHANGENAME with the actual name) to nullify as many defaults as possible.
  3. Set autodiscover.localdomain.local as a CNAME to autodiscover.outlook.com.
  4. Set autodiscover.publicdomain.pub as a CNAME to autodiscover.outlook.com in Internet DNS. This LAN has a local copy of publicdomain.pub in its domain controllers, so copied this record to the local server as well.
  5. Unregistered the NIC for the on-premises Exchange server in DNS. The checkboxes are in the DNS tabs of both TCP/IPv4 and TCP/IPv6, within the Advanced area of the NIC. This is done so that DNS changes which are next, will not be undone automatically.
  6. Removed DNS A records exchange.localdomain.local and exchange.publicdomain.pub from local and Internet DNS respectively.
  7. Added DNS CNAME records exchange.localdomain.local and exchange.publicdomain.pub, both pointing to outlook.office365.com, to local and Internet DNS as appropriate.
  8. Set up oldexchange.localdomain.local and oldexchange.publicdomain.pub as A records pointing to the IP being used by the on-premises Exchange, to local and Internet DNS as appropriate, for archival uses and until we are ready to decommission the on-prem Exchange altogether.

Categories:   Exchange and Exchange Online   Office 365

==============

Setting up Outlook for Office 365 / Exchange Online Etcetera
article #733, updated 1063 days ago

Try this:

http://office.microsoft.com/en-us/support/set-up-your-office-365-or-other-exchange-based-email-in-outlook-2010-or-outlook-2013-HA102823161.aspx

For Outlook 2007:

http://office.microsoft.com/en-us/office-online-help/set-up-email-in-outlook-2007-HA102823160.aspx?CTT=5&origin=HA102823161

Categories:   Office 365   Outlook

==============

Turn off WINMAIL.DAT in Office365
article #669, updated 1251 days ago

The widely recommended method, is to connect to the Office365 Exchange server via PowerShell. This may need to be done in PowerShell run as administrator; certainly the first line has to be run thusly, although that one line may have to be run only once per client machine.

Set-ExecutionPolicy Unrestricted

(type Y for Yes)

$LiveCred = Get-Credential

(enter your Office365 administrative credentials)

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session
Set-RemoteDomain Default -TNEFEnabled $false
Remove-PSSession $Session

Categories:   Office 365