Tag: Office 365

Office 365

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

Outlook 2010 support for Office 365 will end 13 October 2015

About two weeks October 13, 2015 this is the final day of mainstream support for Outlook 2010.

This is especially relevant to Exchange Online users as the system requirements for Office 365 state that it is designed to work with “any version of Microsoft Office in mainstream support”. While Microsoft does not actively block you from connecting to Office 365 with legacy versions or client applications, the text around older versions includes phrases like “does not recommend”, “limited support” and “quality of user experience will diminish over time”.

image

new CMDlet parameters missing in Exchange 2013 CU9 KB3075700

When you upgrade your Exchange 2013 server to CU9 some command are missing.

These you need wen you want more control over Sent Items when using shared mailboxes.

Whether a mailbox is used by multiple users as a communication tool, a shared mailbox remains an important business requirement.
Early releases from Exchange 2013 there was a no way to configure this behavior.

In Office 365 and Exchange 2013 CU9, this feature on shared mailboxes is disabled by default.

If you mis it run:
setup.exe /preparead /iacceptexchangeserverlicenseterms

Get-Mailbox -RecipientTypeDetails Shared | Set-Mailbox -MessageCopyForSentAsEnabled $True
Get-Mailbox -RecipientTypeDetails Shared | Set-Mailbox -MessageCopyForSendOnBehalfEnabled $True

https://support2.microsoft.com/kb/3075700/

Public Folder Migratie to Office365

Move Public Folder script from 2007/2010 to Office 365 Script created by Ward Vissers
www.wardvissers.nl

THIS CODE IS MADE AVAILABLE AS IS, WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK
OF THE USE OR THE RESULTS FROM THE USE OF THIS CODE REMAINS WITH THE USER

                                        
Please Select the Choice You Want

Prepare for Migration (Legacy Exchange Server
00) Add the Office 365 Domain Name
01) Take a snapshot of the original source folder structure
02) Take a snapshot of public folder statistics such as item count, size, and owner.
03) Take a snapshot of the permissions
04) Locate public folders that have a backslash in the name
05) Rename Public Folder
06) Checks the public folder migration status.
07) Set PublicFolderMigrationComplete to False

Check Office 365
08) Get-PublicFolderMigrationRequest
09) Get-Mailbox -PublicFolder
10) Get-PublicFolder

Generate CSV Files and create Public Folder Mailboxes (Legacy Exchange Server)
11) Export-PublicFolderStatistics PFSizeMap.csv
12) PublicFolderToMailboxMapGenerator PFMailboxMap.csv

Create the public folder mailboxes on Exchange Online
13) Master Public Folder Name
14) Create Public Folder Mailboxen (Check PFMailboxMap.csv)

Migrating the Public Folders
15) Export mail-enabled public folders from Active Directory
16) LegacyExchangeDN Administrator
17) LegacyExchangeDN Public Folder Server
18) External Name Outlook Anywhere
19) Set the XML file
20) Give the CSV file to start the Migration
21) Public Folder Migration Status

Lock down the public folders on the legacy Exchange server for final migration (downtime required)
22) Lock the legacy public folders for finalization

Finalize the public folder migration (downtime required)
23) Finalize the public folder migration (downtime required)

Test and unlock the public folder migration
24) Add Public Folder to Test User
25) Unlock the public folders for all other users
26) Public Folder Migration Complete (Legacy Exchange Server)
27) Public Folders Enabled Local

Final Check
28) Take a snapshot of the original source folder structure.
29) Take a snapshot of the public folder statistics such as item count, size, and owner
30) Take a snapshot of the permissions

99) Exit
Public Folder Migratie to Office365

Download: https://gallery.technet.microsoft.com/scriptcenter/Public-Folder-Migratie-to-25bd50a0

Microsoft Ignite first things about Exchange Server v.Next & Skype for Business

Microsoft Ignite will be hell add may 4-8. The session catalog contains 275 sessions, covering products like Exchange (49), Office 365 (85) and Skype for Business (26). It will be the first major Microsoft event where details will emerge on the next version of Exchange, Exchange v.Next.

The next version of Exchange Server is arriving in the second half of 2015. A short heads-up as the session catalog for Microsoft Ignite has been published. So, if you are still undecided or already want to pick ‘must see’ sessions for your schedule, you can check the session catalog here.

I will not attend Ignite. But i hope the sessions wil be publishd on Channel 9 here.

Short List of sessions:
Tools and Techniques for Exchange Performance Troubleshooting
Meet Exchange Server v.Next
Choosing between Server, Online and Hybrid with Skype for Business
Deploying Exchange Server v.Next
Deep Dive into How Microsoft Handles Spam and Advanced Email Threats
Exchange Server Preferred Architecture
Experts Unplugged: New Exchange Scenarios
Exchange on IaaS: Concerns, Tradeoffs, and Best Practices

Moved al mailboxen to Office 365 & Still using dirsync! Can you remove the last Exchange 2010/2013 Server. Yes It Can! Just don’t do it!! You will have a support issue when you have problems!!

After a customer migrated  to Exchange Online some time ago.
They wanted not a hybrid situation. but they are using still DirSync!

After reading: Decommissioning your Exchange 2010 servers in a Hybrid Deployment a I read its not a real problem.

Changed DirSync & After that Uninstalling Exchange 2013 was very easy.

I had only to disable the Arbitration mailboxes: I did that with the following powershell command:

Get-Mailbox -Arbitration | disable-Mailbox -arbitration -RemoveLastArbitrationMailboxAllowed

I did not publish this article because i has still some doubts!!

I had still a question: Do want to remove the last Exchange Server? Have you a supported Environment without a local Exchange Server and still using DirSync??

Yes & No!!

After reading Concerning Trends Discovered During Several Critical Escalations

Microsoft Says:
You may remove the last Exchange Server locale when you move totally to Office 365/Exchange Online, but change Exchange Attribuuts trough ADSI is not supported.

If you don’t have a third party tool for that. The only way is trough ADSI and that is not supported.

My Conclusion:

You have a support issue when you dropped a Call at Microsoft and they investigate your environment.
Don’t remove the last Exchange Server even when all mailboxen exist in Office 365/Exchange Online and keep them up to date!
You can always install a Exchange Server but most of the times it will be always to late!

Exchange & Patching!!!

Microsoft recommends adopting a software update strategy that ensures all software follows N to N-1 policy, where N is a service pack, update rollup, cumulative update, maintenance release, or whatever terminology is used by the software vendor. Microsoft strongly recommend that our customers also adopt a similar strategy with respect to hardware firmware and drivers ensuring that network cards, BIOS, and storage controllers/interfaces are kept up to date.

Software patching is not simply an issue for Microsoft software. You must also ensure that all inter-dependent solutions (e.g., Blackberry Enterprise Server, backup software, etc.) are kept up-to-date for a specific release as this ensures optimal reliability and compatibility.

Customers must also follow the software vendor’s Software Lifecycle and appropriately plan on upgrading to a supported version in the event that support for a specific version is about to expire or is already out of support.

For Exchange 2010, this means having all servers deployed with Service Pack 3 and either Rollup 7 or Rollup 8 (at the time of this writing). For Exchange 2013, this means having all servers deployed with Cumulative Update 6 or Cumulative Update 7 (at the time of this writing).

For environments that have a hybrid configuration with Office 365, the servers participating in the hybrid configuration must be running the latest version (e.g., Exchange 2010 SP3 RU8 or Exchange 2013 CU7) or the prior version (e.g., Exchange 2010 SP3 RU7 or Exchange 2013 CU6) in order to maintain and ensure compatibility with Office 365. There are some required dependencies for hybrid deployments, so it’s even more critical you keep your software up to date if you choose to go hybrid.

Translate »