Hacker News Reader

Comment by cwyers | Hacker News Reader

All of the file-sharing features are tied into "OneDrive For Business," which isn't OneDrive and is just some Sharepoint garbage. The new sync client helps a lot, but it doesn't work for the sharing part at all, which is what Teams uses. It's a huge liability for Teams until Microsoft can make OneDrive For Business not terrible. And when I evaluated it, it was missing any kind of snippet support, which I consider a dealbreaker (some workflows may not think this way, which is fine).

View on HN

You mention onedrive, funny (perhaps not) story: I've seen 5~ situations at different organisations where malware in the form of cryptolocker spreads through onedrive destroying everyone's files and connected computers more often than not, also interestingly I've seen onedrive completely mess up its versioning system and rid the organisation at hands files dated and resulting in days if not weeks of re-work. I can't believe these things seem to go unreported as if I've seen it (at least) 5 times others must have witnessed it many more, onedrive seems like one the carrier of bad all that is bad and vulnerable in the Microsoft ecosystem. Note: I am not some anti-corp / anti-ms fanboy, I'm simply stating what I've witnessed which I have not with other platforms.

I assume the organizations were using ODB as on-prem only? If they were using it with SharePoint Online they could request a point in time restore. --With on-prem solutions, they have to be managing their own backup strategy, which many companies are horrible at. In this respect, I don't think it's really any different than it would be with Dropbox or another cloud provider, although I suppose they could have tools that require less manual intervention to do the restore?

No, at least three of them were online / part of the O365 bundle (fumble if you ask me), it was an absolute nightmare dealing with Microsoft support, the level of incompetence they showed two of the times (when I was involved) was astounding, I'd heard bad things but it was next level and what made it worse is they were paying for the service, both with money and with the downtime while they were messed around both by the initial disruption and the messing around with the seemingly endless running with Microsoft support engineers, finally files were restored but the damage from the downtime and time spent on trying to get the vendor to deliver the cost to the business in at least one of the cases (I'm under an NDA for the one) was immeasurable but large. They experienced had previously experienced many problems with MS support and with the O365 (completely online / hosted) platforms it is enough that they're now underway evaluating alternatives, it might be the same products but on-prem or something entirely different but I am not involved in that process.

They will probably fix it over time, and also closely integrate with everything else, like LinkedIn, O365, Word / PPT / Task Tracking etc..

I highly doubt that, the yammer, SharePoint, onedrive, O365 etc... integration is abysmal and every product seems to get worse as they seem to tie them together with silly string behind the scenes.

With as long as I've been using OneDrive For Business -- yeah, they'll probably fix it over time. It's been getting fixed over time. It's just happening really slowly, and I wouldn't be optimistic about it getting fixed on a timeline I cared about.

They did the same thing with Skype for Business, which is just Lync, warmed over.

Skype for business is bad, you can't do simple things like share a file through the chat, you have to send an email attachment.

Yeah, there are some glaringly simple things Skype For Biz has trouble doing. Try to figure out how to view your chat conversation history.

The established standard UX across IM apps is that you click on the contact you are interested in, and scroll up in the chat window to view your old IMs. Not on Skype for biz.

I have stability issues with Skype for business, but I share files daily with colleagues. Are you sure that's not some restriction put on by your IT department?

That might be the case :)

Reply on news.ycombinator.com