This is due to the changes to Windows Installer (MSI) this month. In addition to these standard testing guidelines, we recommend that all core applications undergo a testing regime that includes self-repair, uninstall, and update. Ensure that you deploy and revoke access as part of your test cycle. Test deploy sample applications using AADJ and Intune.Perform shadow copy operations using VSS-aware backup applications in a remote VSS deployment over SMB.Test your Hyper-V servers and start/stop/resume your Virtual Machines (VM).(These tests will require Kerberos authentication, and may only be used with the RDP protocol. Test remote Credential Guard scenarios.
The following changes are not documented as including functional changes, but will still require at least " smoke testing " before general deployment: Use SHA-1 signed versus SHA-2 signed drivers.Įach of these high-risk test cycles must include a manual shut-down, reboot, and restart.Run drivers that are signed and unsigned.Run applications that have binaries (.EXE and.Test your signed drivers using physical and virtual machines, (BIOS and UEFI) and across all platforms (x86, 64-bit): These high-risk changes are likely to include functionality changes, may deprecate existing functions, and will likely require new testing plans.
0 kommentar(er)
