System administrators fall into this trap for several reasons.
1) Do not plan ahead and use the “if isn’t broke, do not fix it mentality”. So hardware gets older, things get tighter, and while demand increases, the capacity and durability of the old system become very susceptible to fail sooner or later. To overcome this issue, it is ok to use if broke do not fix it only as a way to fix other issues that are currently becoming problematic, but then, schedule upgrade and updates and set policies on how often hardware should be replace. Between 3 to 6 years is usually a good rule of thumb. 2) Incompatibilities: as systems get older and so does the operating systems over time, newer applications will slowly become incompatible. This starts forcing IT administrators to push back on application upgrades due to the fact they are not compatible with company OS image. This also holds true when and if the application requires an older OS which could then hold the company image to remain on an older OS so users can still use this old legac...