B
Ben_22
Hi all,
Windows server 2016 server builds where the June 2018 CU is integrated into the wim.
.NET framework 3.5 is installed as part of the install process, however the CU updates for .NET framework do not seem to apply.
I found this out by running a Nessus scan against a number of server 2016 machines and finding they all reported old versions of .net framework 3.5 files.
Since the .NET framework roullups are no longer available for Server 2016, I cannot run them, and since the latest CU is already installed, I cannot re-run that.
Has anyone else run into this? and anyone found a away around it ?
As far as the inevitable responses of "don't integrate your CU's into your wim" - when you have over 1000 servers to build, saving that bit of time per server is worth it
Continue reading...
Windows server 2016 server builds where the June 2018 CU is integrated into the wim.
.NET framework 3.5 is installed as part of the install process, however the CU updates for .NET framework do not seem to apply.
I found this out by running a Nessus scan against a number of server 2016 machines and finding they all reported old versions of .net framework 3.5 files.
Since the .NET framework roullups are no longer available for Server 2016, I cannot run them, and since the latest CU is already installed, I cannot re-run that.
Has anyone else run into this? and anyone found a away around it ?
As far as the inevitable responses of "don't integrate your CU's into your wim" - when you have over 1000 servers to build, saving that bit of time per server is worth it
Continue reading...