Group policy, Microsoft Endpoint Manager, and other methods can be used to onboard a persistent machine. Onboarding a persistent VDI machine into Microsoft Defender ATP is handled the same way you would onboard a physical machine, such as a desktop or laptop. In short, the persistent VDI machine behaves much like a physical machine in that local data is saved or persisted across these actions (reboot, shutdown, logoff). Persistent VDI is a deployment type where the virtual machines (VM) persist their state, meaning that the machine doesn’t lose its state or data when it is rebooted, shutdown, or when a user logs off. Let’s look at both of these types and explore how they interact with Microsoft Defender ATP onboarding. When we talk about VDI, we often talk about two different deployment types: persistent and non-persistent. In this blog post, we’ll cover VDI, how it works with Microsoft Defender ATP, best practices, and some lessons learned. As such, we want to ensure that Microsoft provides protection for VDI machines, and that you understand how Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP) works within your VDI deployment. Virtual Desktop Infrastructure (VDI) is fairly common in customer environments, especially in today’s world where many are working from home as a result of COVID-19.

Find pvs server vdi