It might have at large your attention that Windows XP problems with Exchange 2015 came to the tip of the support runway in Gregorian calendar month 2014, a undeniable fact that definitely seems to be the case for the oldsters UN agency have according problems running Outlook 2010 on Windows XP against Exchange 2013 CU7 servers.
CU7 shipped in Dec 2014, some six months once XP was shuffled off to the aspect (at least within the minds of everybody at Microsoft). There’s a good probability – maybe even a 100 percent probability – that Microsoft didn’t take a look at Outlook 2010 purchasers on Windows XP against CU7 throughout the event cycle. It’s thus altogether unsurprising that some options don’t work. what’s shocking is that the options that appear to be inflicting issues as a result of they’re not new stuff.
For the lifetime of Pine Tree State, I can’t assume why Outlook 2010, that may be a fairly recent consumer, would fail to access public folders once mailbox servers area unit upgraded to CU7. Everything works with CU6 however fails with CU7. Microsoft has been operating with public folders to enhance their performance and quantifiability, however it’s not that. the matter report expressly mentions public folder databases, thus we all know that old-style public folders area unit within the combine. In turn, this makes the matter even intruder as a result of old-style public folders are, well around see you later, or definitely long enough to own created Outlook 2010 understand precisely the way to deal with the limited beasties.
Another odd issue may be a report that shared mailboxes aren’t functioning additionally as they ought to once Outlook 2010 purchasers (again on XP) hook up with CU7. The mailboxes work as shared repositories, however synchronization isn’t operating as mechanically because it did before. Manual synchronization works, however users area unit upset that one thing has modified.
The folks coverage these problems have noted that they’re making ready for migration and simply have to be compelled to keep these Windows XP problems with Exchange 2013 purchasers around for a couple of a lot of months. From their perspective, it’s a royal pain within the fundament to suddenly discover that a server upgrade wreaks mayhem on purchasers, particularly in area unitas of practicality that you just would have assumed are stable. thus I actually have some sympathy for his or her complaints.
But I conjointly compassionate Microsoft. They told customers that XP was for the scrap heap for a really durable before the day of destiny arrived. Six months on, it’s troublesome to criticize Microsoft for failing to make sure that a fairly new Outlook consumer running on a really previous OS (in cloud terms) has problems once connected to the most recent and greatest on-premises Exchange server.
It might be that Microsoft viewed the end of Windows XP as a chance to trim a number of the previous code within the server from the Exchange code base. like every product that has been around for a really durable, Exchange is choked with conditional code ways necessary to deal with totally different circumstances. The rewrite of the knowledge Store into managed code for Exchange 2013 was a type of code purge for the server, however some stuff still lingers on.
And at an equivalent time, Exchange is evolving to deal with cloud services and choices area unit being created to upgrade practicality to figure higher within the cloud. Windows XP problems with Exchange 2013 purchasers don’t seem to be on it specific style chart, thus why would we have a tendency to be shocked once issues happen?
I can’t supply a lot of joy to the oldsters UN agency have to be compelled to deal with the outrageous slings and arrows of XP. maybe you must keep some Exchange 2013 CU6 servers around and place all of your public folder databases and mailboxes for XP users on those servers. The manoeuvre can work and reflects reality, though it looks to be a shame to not be able to run the most recent code.
Life will be exhausting now and then, particularly if you run XP in 2015.
Follow Tony @12Knocksinna
What Microsoft has to do to upgrade the Outlook apps
Worried concerning security and privacy in Outlook for iOS and Android? Here’s your probability to discussion the problems
Discuss this journal Entry four
ARMSB on February five, 2015
Windows XP is not any longer supported, it’s done and finished. though some places have procured extended support…at a value that is supposed to steer them to upgrade, I feel no sympathy for individuals with this issue.
Windows XP is finished.
Login or register to post comments
TRedmond Follow on February six, 2015
Although I agree that Windows XP is finished, I still have to be compelled to report that a number of my Microsoft contacts are taking a glance at this example (it would possibly disguise a drag which will erupt on a supported platform) and you ne’er understand… No guarantees…
Login or register to post comments
declanconroy on February seven, 2015
I’ve had an equivalent issue with a client running Outlook 2007 on XP.
We tested with a consistent version of Outlook 2007 and it works on Windows seven and higher than.
I perceive that XP is finish of life, and in a perfect world you may simply go forth, however once associate existing established client that for no matter reason hasn’t nevertheless upgraded the desktop OS has a difficulty, it isn’t as straightforward within the planet to inform them it’s their own fault, though inside that is what we’re all thinking.
I used associate communications protocol person to appear at the traffic between the 2007 consumer and Exchange, and everything appearance traditional.
The itinerary is subtly totally different for 2007 on XP than it’s on W7.
On XP Outlook appearance up the autodiscover universal resource locator for the first hierarchy mailbox folder public, associated gets an communications protocol /1.1 two hundred OK response.
Then you see the RPCDIAG affiliation standing for Public Folders cycle via some very fast referrals, before you get the error that “your profile isn’t configured”.
It looks to Pine Tree State just like the issue is within the RPC stack on XP, and not most in Outlook itself.