Rollup 13 for Exchange Server 2010 Service Pack 3

This update rollup includes the following changes: 

  • A new Office 365 Hybrid Configuration wizard (HCW) is used in Exchange Server 2010 that was bundled in the Exchange Management Console (EMC). This change makes sure that EMC always runs the latest version of the HCW that contains up-to-date experience when the HCW is initiated from the EMC.
  • An updated Secure/Multipurpose Internet Mail Extensions (S/MIME) Control for Outlook Web Access. The control is signed to use aSHA-2 compliant code signing certificate. After you install this update, an updated version of the control on the Exchange server will be replaced. Users who have installed the earlier version of the control into a computer’s browser must log on to Outlook Web Access and download the updated control after the Exchange server updates are completed.
  • Exchange Server 2010 Service Pack 3 Update Rollup 13 (KB3141339) Download

Important notice about certificate expiration for Exchange 2013 Hybrid customers

If you’re running Exchange 2013 and you’ve configured a hybrid deployment with Office 365, this post contains important information that might impact you. Please evaluate this information and take any necessary action before April 15, 2016.

On April 15 2016, the Office 365 TLS certificate will be renewed. This certificate is used by Office 365 to provide TLS encryption between Office 365 and external SMTP servers. The new certificate, which will help improve the security of mail sent to and from Office 365, will be issued by a new Certificate Authority and it will have a new Issuer and Subject.

This change has the potential to stop hybrid mailflow between Office 365 and your on-premises Exchange servers if one of the following conditions applies to you:

  • Your on-premises Exchange servers are running Exchange 2013 Cumulative Update 8 (CU8) or lower.
  • You’ve upgraded the Exchange 2013 servers that handle hybrid mailflow to Exchange 2013 CU9 or higher. However, since upgrading to CU9, you HAVE NOTre-run the Hybrid Configuration wizard (either from the Exchange Admin Center or via the direct download link).

If one of the previous conditions applies to your organization, hybrid mailflow between Office 365 and your organization will stop working after April 15, 2016unless you complete the steps below.

Note: This only affects hybrid mailflow. Regular mailflow and TLS encryption is NOT affected.

How to keep hybrid mail flowing (MUST be completed before 4/15/2016)
Let the new Hybrid Configuration wizard do it for you

You can use the latest Hybrid Configuration wizard (HCW) to configure your Exchange 2013 servers to work with the new TLS certificate. Just follow these steps:

  1. If the Exchange 2013 servers handling hybrid mailflow are running Exchange 2013 CU8 or lower, follow the instructions in Updates for Exchange 2013 to install the latest cumulative update on at least one server.
  2. After you install the latest cumulative update, download the new HCW application and run the wizard following the instructions here .

Note: For information on which releases of Exchange are supported with Office 365, see Hybrid deployment prerequisites.

Manual update

If you can’t upgrade Exchange 2013 to latest cumulative update right now (although we would like to remind you of our support policy), you can manually configure your servers to work with the new TLS certificate. On each Exchange 2013 server that’s used for hybrid mailflow, open the Exchange Management Shell, and run the following commands:

$rc=Get-ReceiveConnector |where {$_.TlsDomainCapabilities -like “*<I>*”}

Set-ReceiveConnector -Identity $rc.Identity -TlsDomainCapabilities “mail.protection.outlook.com:AcceptCloudServicesMail

http://blogs.technet.com/b/exchange/archive/2016/02/19/important-notice-about-certificate-expiration-for-exchange-2013-hybrid-customers.aspx

Download Office 2016 with Click-to-Run for Office 365 products by using the Office Deployment Tool

There are two different versions of the Office Deployment Tool available – one for Office 2013 and a different one for Office 2016. Each Office Deployment Tool works only with that specific version of Office. You can download them from the Microsoft Download Center by using the following links:

Configuration.xml

<Configuration>
  <Add SourcePath=”d:\2016\” OfficeClientEdition=”32″ Branch=”Current”>
    <Product ID=”O365ProPlusRetail”>
      <Language ID=”en-us” />
      <Language ID=”nl-nl” />
    </Product>
    <Product ID=”VisioProRetail”>
      <Language ID=”en-us” />
      <Language ID=”nl-nl” />
    </Product>
  </Add>

  <!–  <Updates Enabled=”TRUE” Branch=”Current” /> –>

  <Display Level=”Full” AcceptEULA=”TRUE” />
 
  <Logging Name=”OfficeSetup.txt” Path=”%temp%” />

  <Property Name=”AUTOACTIVATE” Value=”1″ />

</Configuration>

Download

D:\2016\setup.exe /download d:\2016\configuration.xml

Install / Configure Office 365 (2016)

D:\2016\setup.exe /configure d:\2016\configuration.xml

Source: https://technet.microsoft.com/en-us/library/jj219424.aspx

Skype for Business Basic Client

Lync Basic 2013 provides all the basic functionality that’s available in the full version of Lync (Lync 2013). However, if you want to use any of the following features, you will need to upgrade to Lync 2013:

  • Advanced call features (not available with all Office 365 subscriptions); advanced call features include team ring, call forwarding, simultaneous ring, voice mail, call park, call delegation, response groups, and remote call control
  • Calendar delegation
  • Gallery video view
  • OneNote sharing
  • Recording
  • Skill search (not available with Office 365)
  • Virtual Desktop Infrastructure (VDI) (not available with Office 365)

Download Skype for Business Basic

Microsoft Skype for Business Basic (64 Bit)
http://www.microsoft.com/en-us/download/details.aspx?id=49440

Microsoft Skype for Business Basic (32 Bit)
http://www.microsoft.com/en-us/download/details.aspx?id=49439