Microsoft Sucks: FACT

[5268282]

As a tech professional, Windows 10 is probably the worst OS for a professional environment. With the privacy concerns, self promotion, the force fed apps (especially for gaming… yes Pro version), and the fact that whenever a user logs into a workstation forcing the apps to AUTOMATICALLY download (sucking up bandwidth and making the machine unuseable for 10 minutes). Microsoft has dropped the ball here and most tech users agree.

My point of posting this here is because of the native Mail debacle. This is important for professional users, as well as the average user. Of course Microsoft said the work around is to have the user use their iOS app, quite frankly I think it's terrible.

https://www.macrumors.com/2017/09/20/apple-microsoft-email-server-issue-mail-app-ios-11/amp/

I would like to believe Apple tried to fix this issue, but Microsoft is with holding information in order to force users of their mail to use the iOS app. I use Outlook for my personal email (over a decade) and Office 365 for business and I can tell you that it evolved into an uncontrollable mess. It's literally nothing but pointless add-ins and a far reach from professional (not to mention slow to load on any browser including Edge).

Sorry, just had to vent!

 

[dumastudetto]

I agree with you 100%. It is completely insane for anyone to blame Apple for this. And quite frankly, nobody needs Microsoft for anything anymore.

 

[TheGoog]

As a tech professional, Windows 10 is probably the worst OS for a professional environment. With the privacy concerns, self promotion, the force fed apps (especially for gaming… yes Pro version), and the fact that whenever a user logs into a workstation forcing the apps to AUTOMATICALLY download (sucking up bandwidth and making the machine unuseable for 10 minutes). Microsoft has dropped the ball here and most tech users agree.

My point of posting this here is because of the native Mail debacle. This is important for professional users, as well as the average user. Of course Microsoft said the work around is to have the user use their iOS app, quite frankly I think it's terrible.

https://www.macrumors.com/2017/09/20/apple-microsoft-email-server-issue-mail-app-ios-11/amp/

I would like to believe Apple tried to fix this issue, but Microsoft is with holding information in order to force users of their mail to use the iOS app. I use Outlook for my personal email (over a decade) and Office 365 for business and I can tell you that it evolved into an uncontrollable mess. It's literally nothing but pointless add-ins and a far reach from professional (not to mention slow to load on any browser including Edge).

Sorry, just had to vent!

I'm responding to this as an IT professional managing multiple business Exchange environments, and owner of multiple Mac workstations/mobile devices.

The OP's statement is entirely ridiculous, and given his level of apparent understanding of the matter, it's probably also worth pointing out that Microsoft doesn't build ActiveSync for partners. Rather publishes the spec, and then partner's have to build their own software from scratch. This means Apple is entirely responsible for their implementation of ActiveSync.

Apple's implementation of ActiveSync was working great in iOS 10, but fails to deliver (pun intended) with iOS 11. Major code change there from Apple.

Microsoft has not delivered a code change to Exchange server in the last few weeks. Mind, the iOS11 issues aren't just with Outlook.com and Office365, but also with self-hosted Exchange. Our servers have not been delivered any updates for Exchange server in the last couple of weeks, and this includes everything from Server 2012 to Server 2016.

The fact that Microsoft has not delivered a recent code change that could affect Exchange, but Apple has delivered a BIG one, I don't see how anyone could reasonably fathom that Microsoft could be responsible in anyway for Apple's failures here.

 

[AsherN]

Agree with TheGoog. Furthermore, changes in the behaviour of a component like AS would have been noticed across all platforms dependent on AS, and that would include mail.app on iOS10. A change was made to mail.app that broke something. It does not seem to affect everybody, all the time.

 

[Geckotek]

I think I'm likely one of the more qualified to comment on this as an experienced Exchange engineer who used to work in Premiere Support and has migrated or managed several enterprise level environments over the last 20 years.

OP is way off the mark here. Apple has had a long track record of screwing up their ActiveSync implementation. (See here.) Things were working fine in iOS 10 and still are. (I also wouldn't say iOS 10 works perfectly as there are still documented bugs being tracked.)

So how a "tech professional" could possibly come to the conclusion that this is a Microsoft issue when it is SPECIFIC TO iOS 11...is beyond me. I seriously doubt OP has any real IT experience as even a lay person can see that the unique factor is the new OS version. The thing that has changed is Apple's product, not Microsoft's.

Also, a tech professional would be using GPOs to disable the Windows Store and generally lock down the OS to address the other issues OP mentioned.

Edit: Always frustrated that TheGoog has me beat by 11 days.

 

[AFEPPL]

I'm responding to this as an IT professional managing multiple business Exchange environments, and owner of multiple Mac workstations/mobile devices.

The OP's statement is entirely ridiculous, and given his level of apparent understanding of the matter, it's probably also worth pointing out that Microsoft doesn't build ActiveSync for partners. Rather publishes the spec, and then partner's have to build their own software from scratch. This means Apple is entirely responsible for their implementation of ActiveSync.

Apple's implementation of ActiveSync was working great in iOS 10, but fails to deliver (pun intended) with iOS 11. Major code change there from Apple.

Microsoft has not delivered a code change to Exchange server in the last few weeks. Mind, the iOS11 issues aren't just with Outlook.com and Office365, but also with self-hosted Exchange. Our servers have not been delivered any updates for Exchange server in the last couple of weeks, and this includes everything from Server 2012 to Server 2016.

The fact that Microsoft has not delivered a recent code change that could affect Exchange, but Apple has delivered a BIG one, I don't see how anyone could reasonably fathom that Microsoft could be responsible in anyway for Apple's failures here.

Spot on, but don't let facts colour other peoples opinions..

 

[Phil A.]

Mod note

Please continue the discussion in the news article discussion about this issue