<h2>Windows</h2> <ul> <li> <p>updated Microsoft Windws Server Images with current Microsoft Windows Server Patches of November 2019 (12th) including fixes for CVE-2018-12207 and CVE-2019-11135</p> <ul> <li>Windows Server 2008 R2 <ul> <li>2019-11 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB4525233)</li> <li>2019-11 Cumulative Security Update for Internet Explorer 11 for Windows Server 2008 R2 for x64-based systems (KB4525106)</li> <li>2019-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4525235)</li> <li>2019-11 Servicing Stack Update for Windows Server 2008 R2 for x64-based Systems (KB4523206)</li> <li>Windows Malicious Software Removal Tool x64 - November 2019 (KB890830)</li> </ul></li> <li>Windows Server 2012 R2 <ul> <li>2019-11 Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 R2 for x64-based systems (KB4525106)</li> <li>2019-11 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4525250)</li> <li>2019-11 Servicing Stack Update for Windows Server 2012 R2 for x64-based Systems (KB4524445)</li> <li>2019-11 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4525243)</li> <li>Windows Malicious Software Removal Tool x64 - November 2019 (KB890830)</li> </ul></li> <li>Windows Server 2016 <ul> <li>2019-11 Servicing Stack Update for Windows Server 2016 for x64-based Systems (KB4520724)</li> <li>2019-11 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4525236)</li> <li>Windows Malicious Software Removal Tool x64 - November 2019 (KB890830)</li> </ul></li> <li>Windows Server 2019 <ul> <li>2019-11 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB4523204)</li> <li>2019-11 Cumulative Update for Windows Server 2019 for x64-based Systems (KB4523205)</li> <li>Windows Malicious Software Removal Tool x64 - November 2019 (KB890830)</li> </ul></li> </ul> </li> <li> <p>Driver and tools of all Windows Server types</p> <ul> <li>Cloudbase-Init: 0.9.12.dev86</li> <li>XEN GPL driver: 5.0.128.10</li> <li>KVM UVP Vmtools: 2.5.0.151</li> <li>Intel SRIOV (High Performance ) driver : Version 24.2, August 1, 2019</li> <li>NVIDIA vGPU driver: 370.39 (fixes CVE‑2019‑5683 - CVE‑2019‑5687)</li> <li>NVIDIA pGPU driver: 441.22 (fixes CVE‑2019‑5690 - CVE‑2019‑5693, CVE‑2019‑5695)</li> <li>NVIDIA V100 driver: 426.26 (fixes CVE‑2019‑5698)</li> </ul> </li> </ul> <h2>SUSE</h2> <ul> <li><strong>SLES15 SP0</strong> updated image released <ul> <li>A new and updated SLES15 SP0 image has been published.</li> <li>Our technology partner confirmed that the SCSI EVS volumes are known not to work for some of the BMS flavors including the physical.o2.medium. </li> <li>This is because of differences in the SD100 cards that are installed in some of those machines and the mounting of SCSI EVS volumes is not gauranteed to always work.</li> </ul></li> <li><strong>SLES-SAP-12_SP1_SAPHANA</strong> uses a workaround for BMS /boot mount issue <ul> <li>The new SLES-SAP-12_SP1_SAPHANA image has the /boot entry commented in /etc/fstab</li> <li>The /boot fstab entry <strong>MUST</strong> be kept commented to make the image work on BMS as it creates a race condition between systemd and dracut probably (needs more investigation)</li> <li>The /boot partition is mounted using a separate systemd service (boot_mount) and systems works normally</li> </ul></li> </ul>