EOS 날짜 이후에 이미지를 계속 사용할 경우 Google은 EOS 버전에 대해 새 버전의 이미지를 테스트하지 않으므로 게스트 환경을 업데이트하지 않는 것이 좋습니다. Google에서 추가 이미지 계열을 출시할 때 새로 출시된 이미지 계열은 이미지의 EOS 버전을 지원하지 않을 수 있으므로 사용 중인 이미지 계열을 계속 사용하는 것이 좋습니다.
다음 표에는 더 이상 지원되지 않는 Microsoft 운영체제, EOS 날짜, Microsoft의 EOS 공지를 찾을 수 있는 위치, 업그레이드 또는 마이그레이션 관련 콘텐츠 링크가 나와 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-05-15(UTC)"],[[["\u003cp\u003eMicrosoft's End of Support (EOS) for Windows operating systems means Google can no longer provide updates or security patches, and the OS image is deleted from the Compute Engine images project.\u003c/p\u003e\n"],["\u003cp\u003eVMs using images beyond their EOS date will continue to operate, but future Google Cloud features may not perform as expected, and using an unpatched version can create security risks.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends upgrading or migrating to a supported Windows version before the EOS date, and to copy any images needed for future VM creation after the EOS date.\u003c/p\u003e\n"],["\u003cp\u003eFor enhanced security when using EOS images, it is recommended to remove external IP addresses, utilize internal IPs, and consider configuring a Remote Desktop Gateway to restrict remote access.\u003c/p\u003e\n"],["\u003cp\u003eAfter an EOS date, you should not update the guest environment and continue using the current image family because new image families may not support EOS versions.\u003c/p\u003e\n"]]],[],null,["# Windows end of support\n\nWindows\n\n*** ** * ** ***\n\nPeriodically, as part of the [Microsoft Lifecycle\nPolicy](https://support.microsoft.com/en-us/hub/4095338/microsoft-lifecycle-policy), Microsoft might announce an end of support (EOS)\ndate for a version of their operating system that you are using for VM instances\non Compute Engine. On the EOS date for that version of the operating\nsystem:\n\n- Google can no longer access updates.\n- Google can no longer access security patches.\n- The OS image is deleted from the Compute Engine images project. If you need to create VMs that use any of these EOS versions after the EOS date, [make copies of the images](/compute/docs/images/create-custom) before the EOS date.\n\nIf you are running VM instances on Compute Engine based on one of these\noperating system images, keep in mind that beginning on the EOS date:\n\n- VMs based on images that are beyond their EOS date continue to operate, and\n billing continues for [premium images](/compute/disks-image-pricing#premiumimages).\n\n- Future Google Cloud features might not perform as expected if you\n use an image that is beyond its EOS date.\n\n- Google can no longer provide updates or security patches. Microsoft\n might provide additional support through its [Extended Security\n Update (ESU)](https://support.microsoft.com/en-us/help/4497181/lifecycle-faq-extended-security-updates)\n program. It is your responsibility to install and test all updates provided by\n Microsoft.\n\n- Google provides support for VMs that use EOS images. For more information,\n review [End of support (EOS)](/compute/docs/images/os-image-lifecycle#eos)\n documentation.\n\nUsing an unsupported and unpatched version might create material security risks.\nIf you are running VM instances based on an operating system image with an\nannounced EOS date, Google recommends that before the EOS date, you:\n\n- Upgrade or migrate to a [supported version of the Windows operating\n system](/compute/docs/images/os-details#windows_server).\n\n- If you anticipate needing to create VM instances after the EOS date, make\n copies of the images in your projects.\n\n- Remove any [external IP address](/compute/docs/ip-addresses#externaladdresses)\n because publicly accessible instances might be\n vulnerable to unpatched security exploits. Instead, use the instance's\n [internal IP address](/compute/docs/ip-addresses#networkaddresses) to host\n services and enable\n [Private Google Access](/vpc/docs/configure-private-google-access).\n\n- Consider configuring a\n [Remote Desktop Gateway](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-plan-access-from-anywhere) to\n restrict remote access to your instance.\n\nIf you continue to use an image after the EOS date for that image, Google\nrecommends that you not update the [guest\nenvironment](/compute/docs/images/guest-environment) because Google doesn't test\nnew versions of the image against the EOS version. When Google releases\nadditional [image families](/compute/docs/images#image_families), those newly\nreleased image families might not support the EOS versions of the images,\nso we recommend that you continue to use the image family that you\nare using.\n\nThe following table shows Microsoft operating systems that are no longer\nsupported, their EOS dates, where to find Microsoft's EOS\nannouncements, and links to content about upgrading or migrating:\n\nWhat's next\n-----------\n\n- Learn about the [licensing options for Microsoft\n software](/compute/docs/instances/windows/ms-licensing) on\n Compute Engine.\n\n- Learn more about the [operating system images](/compute/docs/images) that\n Compute Engine provides."]]
