T
tlyczko2
I'm puzzled how this works now.
We started out with what I believe is version 1607 of Win2k16 Datacenter.
I haven't seen any update/upgrade come in via WSUS.
The OS build number of our Win2k16 servers is 14393.2580, I understand this is a fairly current build number.
We do have 'Defer feature updates' enabled.
Can we update/upgrade Win2k16 to a more current version or not??
If so, how do I do this and how do I determine if I *should* upgrade it??
I see on VLSC that obtaining and running newer versions of Windows Server, version 1709 and 1803 requires active Software Assurance, I don't know how much longer our SA lasts, it appears to have enabled our RDS/server CALs to 2019 version though when I read on VLSC, they were 2016 CALs when purchased, I assume this means I could use these CALs again with Win2k19 (the domain controllers will stay at Win2k16)??
Thank you, Tom
Continue reading...
We started out with what I believe is version 1607 of Win2k16 Datacenter.
I haven't seen any update/upgrade come in via WSUS.
The OS build number of our Win2k16 servers is 14393.2580, I understand this is a fairly current build number.
We do have 'Defer feature updates' enabled.
Can we update/upgrade Win2k16 to a more current version or not??
If so, how do I do this and how do I determine if I *should* upgrade it??
I see on VLSC that obtaining and running newer versions of Windows Server, version 1709 and 1803 requires active Software Assurance, I don't know how much longer our SA lasts, it appears to have enabled our RDS/server CALs to 2019 version though when I read on VLSC, they were 2016 CALs when purchased, I assume this means I could use these CALs again with Win2k19 (the domain controllers will stay at Win2k16)??
Thank you, Tom
Continue reading...