Microsoft Office & Exchange 2010- end of support

Image by Gerd Altmann from Pixabay

3 more Microsoft products fell out of support on October 13, 2020:

  • Office 2010
  • Office 2016 for Mac
  • Exchange Server 2010

If you’re on these older versions, upgrading should certainly be on your roadmap. If not to Office 365, then to a more recent on-premises release. As corporate security becomes an ever greater focus, and ransomware becomes an ever greater threat, now is not the time to be running unsupported software that’s over a decade old!

The changes for access to Office 365 have kicked in too, meaning the only releases of Office that are supported to access Office 365 are:

  • Office 2016
  • Office 2019
  • Microsoft 365 Apps (formerly Office365 Pro Plus)

While Microsoft aren’t proactively blocking older versions, they’ve stated that as they fall further behind, performance and/or reliability issues may start to occur.

Further Reading

Office 2010

Exchange 2010

Microsoft BPOS: More new features

Microsoft BPOS has, yet again, been something of a star of the Worldwide Partner Conference and a bunch of new features have been confirmed/announced. They are:

Exchange Online:

  • Voice mail with Unified Messaging
  • Integrated archiving
  • Retention policies and legal hold
  • Transport rules
  • Multi-mailbox search
  • Conversation View
  • MailTips
  • Enhanced Web-based administration
  • Role-Based Access Control
  • Remote PowerShell
  • Free/busy between cloud and on-premises
  • Cross-premises management
  • Native migration tools


    Sharepoint Online:


  • Portal site templates
  • Extranet access
  • Anonymous Access
  • Multi-Lingual UI
  • Office 2010 integration
  • Tagging, Rating, Tag Cloud
  • Activity Feed, Social Networking, Note Board
  • Improved Wikis & Blogs
  • Content publishing
  • Navigation controls
  • Cross site-collection search
  • Phonetic search
  • People search
  • Visio Services
  • Excel Services
  • Sandboxed Solutions
  • Improved workflows
  • Improved SharePoint Designer 2010
  • Access Services
  • Better controls of FQDNs


    Office Communications Online:


  • P2P A/V across firewall
  • File transfer across firewall
  • Presence with pictures
  • Federation
  • IM with Windows Live


    Platform Updates:


  • Free/Busy co-existence
  • Single Sign On
  • Identity federation
  • Redesigned admin interface
  • More administration and access control

    There are some really awesome additions here, which will make BPOS hugely more attractive and credible to users in the mid-market segment. Some of the game changes are, in my opinion,:

    Exchange Online:

    • Transport Rules
    • Legal Hold
    • Unified Messaging
    • Remote Powershell

    Sharepoint Online:

    Extranet & Anonymous Access

    Cross Site Collection Search

    Visio, Access & Excel Services

    Office Communications Online:



    These new features bring Microsoft’s Online Services so much closer to feature parity with their existing on-premise brethren which is what I, and most people, have been waiting/asking/pleading/clamouring for. The number of times I’ve had a customer opportunity collapse due to BPOS missing a standard and relatively basic feature isn’t funny!

    This is a very positive move from Microsoft which will make the world of Online Services a much better place for Microsoft, it’s partners and our customers 🙂

  • BPOS 2010 aka Wave 14

    BPOS (Business Productivity Online Suite), Microsoft’s Online Services offering has been somewhat successful over the last year or so, but it is about to become a much more robust platform. Over the next few months the “Wave 14” rollout will begin, with an aim to being completed by the end of 2010.

    The biggest update is that the products will match the versions that are available to purchase “on-site”. That is, BPOS will offer Exchange 2010 and Sharepoint 2010 with near feature parity; removing one of the biggest hurdles to BPOS adoption…at least in my experience.

    However, there are a number of other additions and improvements coming…

    Identity and authentication has been an issue for many people, as this whole area is quite clunky & “un-modern”. As Program Manager Dan Kershaw says:

    “the password policy isn’t configurable, you can’t use the same credentials used inside the company for single sign-on with BPOS so admins have to maintain separate credentials, there’s no two-factor authentication and no role-based administration”.

    The fact that Microsoft recognise these limitations is great as that means they’re also working on fixes. The update will bring:

    • Password Policy controls
    • Five admin roles
    • Federated ID’s w/ 2 factor authentication for single sign-on
    • New Admin Console
    • Service connector for managing Pcs & apps.


    Powershell is definitely the way forward for 21st century system admins and, while it can be used for certain things with the current iteration of BPOS, more is coming soon.

    I covered off some of the new features of Sharepoint Online 2010 in this post but now there is more information on what’s coming for Office Communications Online (OCO) over the next year.

    Currently OCO gives IM and presence, along with peer to peer video, only within the customer’s domain. One of it’s biggest limitations is the inability to “federate” with on-premise OCS servers…this slightly puzzling block will be removed with Wave 14.

    It’s said there will be “full integration” with Exchange & Sharepoint, both on-site and online.

    This will lead to:

    • using the calendars on Exchange/Sharepoint to determine someone’s IM availability
    • voicemail in Exchange Online
    • IM functionality in OWA 2010.

    One of the biggest questions people have is whether Office Comms Online will have VOIP/Voice capabilities.

    "it might be more than a year later," says Ziv Fass, Senior Product Manager in the OCS team "but it won’t be years".

    From a reseller AND a customer point of view, the updated versions of Microsoft’s Online Services will be a real benefit to us all.

    Exchange 2007 & Server 2008 R2

    Windows Server 2008 R2 doesn’t support Exchange 2007. That is a fact and it has caused confusion, consternation & anger among many of Microsoft’s customers and indeed partners (I can confirm that!).

    The big question was “Why"?”…as when Server 2008 R2 was released in September, Exchange 2007 was the current version. While Exchange 2010 is almost upon us it is still unlikely that companies will instantly move to the new version…particularly on something as important as their email infrastructure. So that meant either:

    a) Customers stayed on Exchange 2007 and Server 2008

    b) Customers had a mixed Server 2008/2008 R2 environment

    and, aside from the technical aspect, many people viewed it as a cynical ploy by Redmond to force them to upgrade. The message alongside Windows 7 is “Deploy with Server 2008 R2, they’re better together” (which is true!) but then it seemed a little like “Gotcha! Now you’re got R2…you’ve got to buy Exchange 2010”. While that wasn’t the case, that’s how it seemed to customers and really-that’s what matters. Vista wasn’t anywhere near a terrible as a lot of people say it is…but it didn’t do very well did it…and that was because of user perception.

    Now however, that’s all changed! This post on the Exchange Team Blog (You had me at EHLO) reveals that:

    “In the coming calendar year we will issue an update for Exchange 2007 enabling full support of Windows Server 2008 R2”

    They say that customers spoke, Microsoft listened and the change is happening…brilliant 🙂

    Good work Microsoft!

    Thanks to @JohnFontana for the tweet that flagged this up…

    Exchange 2010 Licensing Considerations

    Exchange 2010 is now in the price files so you can all go out and buy it 🙂 There is a lot of information about the technical differences, but not so much about the licensing changes…so let me change that 😉

    Replication Licensing

    The current “Local Continuous Replication” is being replaced by “Mailbox Resiliency” in 2010; Mailbox resiliency requires 2 active instances of Exchange 2010…and thus 2 licences.

    As a one-time exception, customers with Exchange 2007 and Software Assurance (SA) on Select, Enterprise Agreement, Open, Open Value, Campus & School get:

    “One complimentary Exchange Server 2010 Standard license for each datacenter where the customer has at least one server licensed for Exchange Server 2007 Standard with active Software Assurance as of November 1, 2009.”

    The additional licences that you receive under this offer all included SA that expires at the same time as your originally purchased licence.

    As an additional offer, if your Exchange SA expires between November 1st 2009 – November 1st 2010 you can renew just the SA for the original licence, and that will also renew the SA for the 2nd additional licence 🙂 However, after that the licences will need to be renewed separately.

    The original MS post is here.

    New features of Exchange 2010

    Microsoft Exchange 2010 is nearly here so I’ve just been going through some of the free e-learning that’s available (here) to see what’s new.

    Unified Communications:

    There have been many improvements around the Unified Messaging piece including:

    SMS Notification of missed calls

    Message waiting indicators

    Personal Auto Attendant

    Users can have voicemail transcribed into their chosen language

    Voice mails are now protected from unauthorised forwarding, copying and extracting

    These enhancements should lead to the UC aspects of Exchange gaining more traction. Previously they’ve been seen as quite superfluous and “nice to have” rather than a “need to have” (at least in my experience); now however the user productivity gains are apparent.

    Another big one is Federated Calendar Sharing, allowing you to easily share info with 3rd party organisations, using Windows Live as the trust broker. You need an internet accessible Client Access Server (CAS) as calendar sharing is done via web services – thusno special ports need opening.

    Microsoft Clustering Services are no longer needed to get High Availability (HA) with Exchange 2010.

    Things to know for deployment:

    Can upgrade from 2003 to 2010

    AD must be at least in

    Windows Server 2003 forest functionality mode

    Also, you must have at least one Windows 2003 Service Pack 2 Global Catalog server in every Active Directory site that will have an Exchange 2010 server.

    Note that Read-only domain controllers (RODC) and read-only global catalog (ROGC) servers are not supported.

    Exchange 2010 does NOT support in place upgrades.

    Read-only domain controllers (RODC) and read-only global catalog (ROGC) servers are not supported


    Microsoft have made a number of changes in this area and, at least to me, they seem like great improvements. They’ve worked hard to reduce the I/O traffic and this is done via:

    IOPS changed to write more data at fewer intervals

    Merged I/O instances

    Both of these reduce the number of operations and improving performance. Two more improvements include:

    Larger cache size (32kb)

    Sequential data storage reduces I/O

    They have also removed the Database maintenance windows by pushing the defrag process into the background.

    All that and more, along with moving diagrams and voiceovers can be found here:

    A look at Exchange 2010

    I’ve been looking around the Microsoft New Efficiency site (blog post here) today and there are a number of great videos giving an overview and introduction to the new features of Exchange 2010. One of the key ideologies behind the new version of Exchange has been that it will behave the same whether it’s on-site or hosted in the cloud. The slide below shows the main pillars of Exchange 2010:


    The following screenshots go into more detail on the features behind the above:






    You’ll see here that Exchange 2010 now has integrated archiving capabilities. As you can see below, it gives users a 2nd mailbox which can be used to store archived data with all the familiarity and ease of Outlook.



    It also has a new “Legal Hold” feature which tracks all edits etc on a user’s email-even those that are deleted.

    Other features/news:

    I saw this week that Exchange 2010 has the ability to migrate users during an upgrade (from 2007) without any downtime! A huge bonus to System Admins everywhere 🙂

    Outlook Web Access is now called Outlook Web App, so still the same initials but it shows a different approach. Rather than it simply being a way to get your emails when you’re without Outlook…it is now a proper, defined entity in it’s own right. That is also shown by the fact that OWA 2010 will have around 95% feature parity with the full Outlook client. I don’t know what the percentage is currently but certainly in my opinion OWA 2007 is lacking a lot; so roll on OWA 2010! This will be of big interest to people looking at Exchange Online aswell…

    %d bloggers like this: