Clarify LTSB support lifecycle and LTSC distinction#4936
Open
tkaji-w wants to merge 1 commit intoMicrosoftDocs:mainfrom
Open
Clarify LTSB support lifecycle and LTSC distinction#4936tkaji-w wants to merge 1 commit intoMicrosoftDocs:mainfrom
tkaji-w wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Added clarification on LTSB support lifecycle and its distinction from LTSC.
tkaji-w
requested review from
Brenduns,
LauraWi,
MandiOhlinger,
Yupiter2005,
bhuney,
lenewsad,
nicholasswhite,
paolomatarazzo and
umair0204
as code owners
Contributor
|
Learn Build status updates of commit a9868ac: ✅ Validation status: passed
For more details, please refer to the build report. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added clarification on LTSB support lifecycle and its distinction from LTSC.
This statement is intended to clearly document the support position regarding the end-of-support (EoS) mismatch between Configuration Manager LTSB and its dependent component, SQL Server 2016.
Please note that this clarification is considered a special case applicable only to LTSB.