-
Notifications
You must be signed in to change notification settings - Fork 282
Update windows-in-place-upgrade.md #308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
For workloads hosting critical infrastructure roles or applications such as SQL Server, Domain Controller (DC), Active Directory (AD), or similar, we do not recommend performing an in-place OS upgrade. Deploying a new VM with latest desired version and copying the data will always be a best option. This approach will not only address certain roadblocks but will also ensure a safer, more controlled, and supportable upgrade path across your critical environment.
|
@ManishaSinha0410 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 6fd0482: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
@ju-shim Could you review this proposed update to your article and enter Thanks! |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a critical warning to the Windows in-place upgrade documentation, advising against in-place OS upgrades for VMs hosting critical infrastructure roles like SQL Server, Domain Controllers, and Active Directory.
- Adds a new note section warning against in-place upgrades for critical infrastructure workloads
- Recommends deploying new VMs and copying data as the safer alternative approach
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <[email protected]>
|
Learn Build status updates of commit b91cee1: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Any update please? |
|
I sent an email to the content owner today. @MicrosoftDocs/public-repo-pr-review-team |
|
@v-dirichards @v-ccolin @ju-shim |
For workloads hosting critical infrastructure roles or applications such as SQL Server, Domain Controller (DC), Active Directory (AD), or similar, we do not recommend performing an in-place OS upgrade. Deploying a new VM with latest desired version and copying the data will always be a best option. This approach will not only address certain roadblocks but will also ensure a safer, more controlled, and supportable upgrade path across your critical environment.