4 ms·

BYOD gives you the freedom to pick whatever device you want and do the actual work with it, not just enter working time and book vacation. But you're connecting

BYOD gives you the freedom to pick whatever device you want and do the actual work with it, not just enter working time and book vacation. But you're connecting that device to the network and using it to access the most sensitive parts of that network, the most delicate data. Most users have little to no "tech hygiene" so allowing random devices maintained by these users to connect will open your company to a world of hurt. For basic standard activities most companies offer locked down environments like Citrix or externally facing portals that can be safely accessed form any home computer. The alternative is to use a company issued device for work.

Someone1234 7y ago
> But you're connecting that device to the network and using it to access the most sensitive parts of that network and the most delicate data. That's not the usage I set out above at all. Not even ballpark. I am talking about an externally accessible "internal" enterprise website, and that IE Mode cannot be used well with it. I'm not sure how you got from website to "access sensitive parts of the enterprise network." Employees are BYOD to access the company's "internal" website from an external endpoint. That's the topic. That's where IE Mode applies. It reads like you and the sibling comment forgot what is even being discussed. This is IE Mode for websites. Specifically for "internal" enterprise websites. I am discussing the highly common practice of allowing access to "internal" websites externally (inc. via privately owned employee's devices over the internet).
- mrkstu 7y ago
  At this point any such site that you want universally accessible should be refactored into a true standards compatible website. Trying to fix the problem on the browser side is the wrong answer, which is what Microsoft is trying to nudge enterprises to by progressively making it harder to use legacy dependent apps like that.
  - Someone1234 7y ago
    > At this point any such site that you want universally accessible should be refactored into a true standards compatible website. That logic could be used to magic anyway any need for IE Mode for anyone. Why even take part in this discussion if you dismiss the need for the very thing we're discussing? Seems fruitless. I honestly have no interest in discussing the merits of IE Mode conceptually. I am talking about the implementation from the point of it existing on-wards. You're welcome to find someone else to argue this with however.
- close04 7y ago
  > That's not the usage I set out above at all. Not even ballpark. I replied to to your later generalization related to the devices' "managed" status, the one turning your original point into an "inflexibility" and "employee privacy" issue. BYOD is/should not be 100% your regular private device. Moreover it's there to allow you more flexibility not less, so you don't have to use a company device and work from the office. You can't give perfect flexibility/privacy to your employees while ensuring even a modicum of security. And someone will always complain about something. The problem isn't that companies manage BYOD devices, it's that they still use legacy sites that only work with IE. So coming back to your original point, the solution as I already said is to provide you with something like Citrix or equivalent (device is no longer relevant), or for the company to fix its websites. Not for MS to implement the magic button that makes your company's legacy sites work for another 20 years. But if you have a security team at all your BYOD will still remain a (partially) managed device regardless. MS is on one hand intentionally restricting the compatibility mode to force lazy companies with bad practices to upgrade their aging sites without straight up cutting them off. On the other hand I'm not sure if MS could even implement a true "IE mode" since nobody wants that legacy code in any modern browser.

Someone1234 7y ago

> But you're connecting that device to the network and using it to access the most sensitive parts of that network and the most delicate data. That's not the usage I set out above at all. Not even ballpark. I am talking about an externally accessible "internal" enterprise website, and that IE Mode cannot be used well with it. I'm not sure how you got from website to "access sensitive parts of the enterprise network." Employees are BYOD to access the company's "internal" website from an external endpoint. That's the topic. That's where IE Mode applies. It reads like you and the sibling comment forgot what is even being discussed. This is IE Mode for websites. Specifically for "internal" enterprise websites. I am discussing the highly common practice of allowing access to "internal" websites externally (inc. via privately owned employee's devices over the internet).

mrkstu 7y ago
At this point any such site that you want universally accessible should be refactored into a true standards compatible website. Trying to fix the problem on the browser side is the wrong answer, which is what Microsoft is trying to nudge enterprises to by progressively making it harder to use legacy dependent apps like that.
- Someone1234 7y ago
  > At this point any such site that you want universally accessible should be refactored into a true standards compatible website. That logic could be used to magic anyway any need for IE Mode for anyone. Why even take part in this discussion if you dismiss the need for the very thing we're discussing? Seems fruitless. I honestly have no interest in discussing the merits of IE Mode conceptually. I am talking about the implementation from the point of it existing on-wards. You're welcome to find someone else to argue this with however.
close04 7y ago
> That's not the usage I set out above at all. Not even ballpark. I replied to to your later generalization related to the devices' "managed" status, the one turning your original point into an "inflexibility" and "employee privacy" issue. BYOD is/should not be 100% your regular private device. Moreover it's there to allow you more flexibility not less, so you don't have to use a company device and work from the office. You can't give perfect flexibility/privacy to your employees while ensuring even a modicum of security. And someone will always complain about something. The problem isn't that companies manage BYOD devices, it's that they still use legacy sites that only work with IE. So coming back to your original point, the solution as I already said is to provide you with something like Citrix or equivalent (device is no longer relevant), or for the company to fix its websites. Not for MS to implement the magic button that makes your company's legacy sites work for another 20 years. But if you have a security team at all your BYOD will still remain a (partially) managed device regardless. MS is on one hand intentionally restricting the compatibility mode to force lazy companies with bad practices to upgrade their aging sites without straight up cutting them off. On the other hand I'm not sure if MS could even implement a true "IE mode" since nobody wants that legacy code in any modern browser.