fsteer
commented
1 year ago CDW quote very high. This seems much lower: https://www.microsoft.com/en-us/d/windows-server-2022-standard-cal/dg7gmgf0d6m5/0003?activetab=pivot:overviewtab
Open mca-it opened 1 year ago
fsteer
commented
1 year ago CDW quote very high. This seems much lower: https://www.microsoft.com/en-us/d/windows-server-2022-standard-cal/dg7gmgf0d6m5/0003?activetab=pivot:overviewtab
Background
Windows Server 2012 and Windows Server 2012 R2 will end on October 10, 2023. After this date, these products will no longer receive security updates, non-security updates, bug fixes, technical support, or online technical content updates. This is reaching end of life, per Microsoft..
This is a vulnerability and not responsible to let go as an institution that serves the public to continue to run this on our infrastructure. Using end-of-life software can increase costs for organizations and risk. Here are five common reasons for fixing this:
1 Incompatible Software — New releases of software have been optimized for the most recent operating systems. With an EOL OS that you cannot upgrade, you may be forced to continue running older applications. These apps themselves are probably facing their own EOLs, too.
2 New vulnerabilities — When a vendor stops issuing security patches, your system becomes a sitting duck for hackers—who will quickly start searching the globe for people who continue to operate in this defenseless mode. Using firewalls and anti-malware countermeasures are not enough to protect your servers from attacks that exploit un-patchable vulnerabilities.
3 Added expense — The operating costs required to maintain and fix bugs on an OS that’s post-EOL can be quite high. In addition, you should estimate the business impact, in dollars, of an outage caused by the EOL OS.
4 Compliance challenges — Regulatory compliance frameworks usually mandate regular patching. The audit and certification process for systems in regulated industries like healthcare and finance may prohibit the use of EOL systems.
5 Poor performance and reduced reliability — Running legacy apps on EOL OS’s leads to performance and reliability issues. Aging systems tend to break down more often than their more up-to-date and patched counterparts. It’s wise to think through the effects of the inevitable downtime that will come with an EOL OS.
Considerations
Licensing and costs We should consider joining the domains from North Campus and South Campus instead of the odd separation currently. This is important for future growth and clarity, and to reduce duplication. Definitely create documentation on this item for future reference Should complete if possible on non-business hours