Safe_OS Error Correction Question and TECHNICAL Poll – see https://lnkd.in/e7MJmzk4
Did you resolve the (Microsoft Server 2019) in-place upgrade problem (and how did you resolve the issue) or did you just bail to a new build?
See https://www.linkedin.com/feed/update/urn:li:activity:7039324488831770627/
A. We are still trying…
B. We built new servers
Resolution for SAFE_OS from ChatGPT.org
Question: How would I resolve Safe_OS errors while upgrading Microsoft Server 2012R2 to Microsoft Windows Server 2016 or Microsoft Windows Server 2019 Operating System on AWS Virtual Machines
Answer:
There are different causes and solutions for Safe_OS errors that may occur when upgrading to Microsoft Windows Server 2016 or 2019 on AWS virtual machines. Here are some steps that may help to resolve this issue:
- Verify the requirements: Make sure that your AWS VM meets the minimum requirements for Microsoft Windows Server 2016 or 2019. You may need to increase the RAM, CPU, or storage capacity of your instance if it falls below the minimum specifications.
- Check the compatibility: Ensure that the applications, drivers, and services that are installed on your current Microsoft Server 2012R2 operating system are compatible with the newer version of Windows Server. Some legacy applications or drivers may not work with the latest version of the OS, and it may cause Safe_OS errors during the upgrade.
- Disable antivirus or firewall: Sometimes, the third-party antivirus or firewall software installed on your server can interfere with the upgrade process and cause Safe_OS errors. Try disabling them temporarily before starting the upgrade.
- Update all drivers and firmware: Ensure that all the system drivers and firmware on your AWS VM are up-to-date. You can use the AWS Systems Manager to scan for missing patches or updates and apply them before beginning the upgrade process.
- Use the latest upgrade media: When upgrading, use the latest Windows Server 2016 or 2019 media available from the Microsoft website or AWS. Select the appropriate architecture (x86 or x64) and language version that matches your instance. Also, make sure that the ISO image or installation media is not corrupted.
- Use the command line: Try to upgrade the OS using the command-line interface (CLI) instead of the graphical user interface (GUI) method. The CLI may provide more details and flexibility when it comes to debugging or resolving Safe_OS errors that occur during the upgrade process.
- Contact AWS support: If none of the above steps work, you can contact AWS support for assistance. They may be able to provide additional guidance and resources for troubleshooting the issue.
Of course, the conclusion is clear :
-Patrick Burwell, Burwell.tech
If you have done all these steps you build a new VM.