Exchange Server Deployment Assistant Updated with New Exchange 2016 Scenarios

We’re happy to announce the latest addition to the Exchange Server Deployment Assistant!

You can now use the Deployment Assistant to help you configure an Exchange 2016-based hybrid deployment in organizations where Exchange 2010 is already installed. Configuring an Exchange 2016-based hybrid deployment gives you access to features like cross-premises e-discovery, enhanced secure mail, multiple Active Directory forest support, OAuth federation support, and more!

In addition to this new scenario, the following scenarios are already available in the Deployment Assistant:

  • Deploy Exchange 2016 into an organization with no existing Exchange deployments
  • Upgrade to Exchange 2016 from Exchange 2010

And, we’re working on adding more scenarios to the Deployment Assistant as fast as we can! We’ll post announcements here when they’re available.

In case you're not familiar with it, the Exchange Server Deployment Assistant is a web-based tool that helps you deploy Exchange in your on-premises organization, configure a hybrid deployment between your on-premises organization and Office 365, or migrate to Office 365. Supported on most major browsers, the tool asks you a small set of simple questions and then, based on your answers, creates a customized checklist with instructions to deploy or configure Exchange. Instead of trying to find what you need in the Exchange library, the Deployment Assistant gives you exactly the right information you need to complete your task.

eda

Do you have a deployment success story about the Deployment Assistant? Do you have suggestions on how to improve the tool? We would love your feedback and comments! Feel free to leave a comment here, or send an email to edafdbk@microsoft.com directly or via the 'Feedback' link located in the header of every page of the Deployment Assistant.

Happy deploying!

The Deployment Assistant Team

On .NET Framework 4.6.1 and Exchange compatibility

We wanted to post a quick note to call out that since yesterday, the .NET Framework 4.6.1 has been made a recommended update on WU (Windows Update).

As we have already stated in the Exchange Supportability Matrix, at this time, this version of .NET framework is not supported by Exchange. In fact, we know of some issues if it is installed.

We are working with the .NET team to ensure that Exchange customers have a smooth transition to .NET Framework 4.6.1, but in the meantime, delay this particular .NET update on your Exchange servers (information on how this can be accomplished can be found in the KB article 3133990, How to temporarily block the installation of the .NET Framework 4.6.1).

Update 2/12/2016:

We had several questions on how our customers should go about rolling back to .NET Framework 4.5.2 if 4.6.1 was already automatically installed. Here are the steps:

  1. If the server has already automatically updated to 4.6.1 and has not rebooted yet, do so now to allow the installation to complete
  2. Stop all running services related to Exchange.  You can run the following cmdlet from Exchange Management Shell to accomplish this:  (Test-ServiceHealth).ServicesRunning | %{Stop-Service $_ -Force}
  3. Go to add/remove programs, select view installed updates, and find the entry for KB3102467.  Uninstall the update.  Reboot when prompted.
  4. Check the version of the .NET Framework and verify that it is showing 4.5.2.  If it shows a version prior to 4.5.2 go to windows update, check for updates, and install .NET 4.5.2 via the KB2934520 update.  Do NOT select 4.6.1/KB3102467.  Reboot when prompted.  If it shows 4.5.2 proceed to step 5.
  5. Stop services using the command from step 2.  Run a repair of .NET 4.5.2 by downloading the offline installer (https://www.microsoft.com/en-us/download/details.aspx?id=42642), running setup, and choosing the repair option.  Reboot when setup is complete.
  6. Apply the February security updates for .NET 4.5.2 by going to Windows update, checking for updates, and installing KB3122654 and KB3127226.  Do NOT select KB3102467.  Reboot after installation.
  7. After reboot verify that the .NET Framework version is 4.5.2 and that security updates KB3102467 and KB3122654 are installed.
  8. Follow the steps here to block future automatic installations of .NET 4.6.1.

Thanks to Marc, Nasir and Brett for testing the above to make sure it all works as expected!

Nino Bilic

ownCloud Desktop and Android Client Updates

Android client showing share dialog

Android client

Today, we published an update to the ownCloud Android client which introduces improved file upload handling and UI improvements; and an update to the ownCloud Desktop client bringing updated HiDPI support, networking improvements and better syncing. Get your updates now and keep your data safely at home!

Android Changes

The most notable improvements in the Android client are related to handling file uploads. Thanks to hard work by several community members, some changes were merged which help avoid file duplication and when uploading files, users can choose how to deal with duplication. Other changes were made to the user interface, allowing different views to be selected per folder (grid or list) and some visual improvements related to Material Design. The share dialog now allows you to determine what permissions to give to the people you share with. And last but not least, a battery drain issue has been resolved.

The full Android client change log:

  • Set and edit permissions on internal shared data
  • Instant uploads: avoid file duplications, set policy in app settings
  • Control duplication of files uploaded via ‘Upload’ button
  • Select view mode: either list or grid per folder
  • More Material Design: buttons and checkboxes
  • Fixed battery drain in automatic synchronization
  • Security fixes related to passcode
  • Wording fixes

Grab the latest Android client from the Play store. Find other stores here.

Desktop Client Changes

The desktop client will now work better on high resolution screens and the overlay icons in various file managers have received some improvements.  Network handling was improved and users can now change the upload chunk size if needed in the configuration file.

ownCloud Desktop Client in action

Desktop Client


The full Desktop Client change log:
  • UI improvements for HiDPI screens, error messages, RTL languages
  • Fix occurences of “Connection Closed” when a new unauthenticated TCP socket is used
  • Fix undeliberate WiFi scanning done by Qt Network classes
  • Several fixes/improvements to the sharing dialog
  • Several fixes/improvements to the server activity tab
  • Create the directory when using –confdir and it does not exist
  • Windows Overlay icons: Fix DLL and icon oddities
  • Mac Overlay icons: Don’t install legacy Finder plugin on >= 10.10
  • Linux Overlay icons: Nemo plugin
  • Overlay icons: Fix several wrong icon state computations
  • Allow changeable upload chunk size in owncloud.cfg
  • Crash fixes on account deletion
  • Forget password on explicit sign-out
  • OS X: Fix the file system watcher ignoring unicode paths (#4424)
  • Windows Installer: Update to NSIS 2.50, fixes possible DLL injection
  • Sync Engine: .lnk files
  • Sync Engine: symlinked syn directories
  • Sync Engine: Windows: Fix deleting and replacing of read-only files (#4308, #4277)
  • Sync Engine: Fixes for files becoming directories and vice versa (#4302)
  • Misc other fixes/improvements

Get the new client for Windows, Mac OS X and Linux.