• _NetNomad@kbin.run
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    so Delta’s non-Windows machines were the ones that suffered the most from a Windows software malfunction? that makes sense

    • Buelldozer@lemmy.today
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 months ago

      It didn’t say “non-windows” it said “served by other providers like IBM”. It could easily be Windows servers in IBM’s cloud and wouldn’t ya’ know…IBM uses Crowdstrike.

      • _NetNomad@kbin.run
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        i’m gonna level with you, i completely forgot IBM cloud was a thing and just thought this was MS pointing fingers at system Z or system . thanks for catching that!

    • some_guy@lemmy.sdf.orgOP
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      Having to reset or recalibrate other old systems that were disrupted by newer ones going offline makes sense to me. If servers were providing Network Time Protocol and older clients drifted without it, that could cause them to be unable to rejoin a domain. I’m speculating wildly, but it’s an example of how losing important infra can cause issues even after it’s restored.