Which means angry users as you scramble to “fix” VDI to make it work for the use case. Just building something and then hunting for use cases means the solution won’t quite fit the use case you’ve found in most cases without a lot of redevelopment of what you’ve built. 3 Hidden gems from the field on why VDI sucks at most companiesīEFORE you begin your VDI journey… Business justificationĪlways have a clear cut use case for what you’re building.2.55 Business Liaisons, Operations, and IT Service Desk Training.2.54 Internal Branding and Marketing Campaigns.2.53 Capturing User Feedback In-Session.2.52 Naming Convention for VDI Admins and End Users.2.48 SOAR – Security Orchestration, Automation, and Response.2.44 SIEM – Security Incident Event Management.2.42 File Share and Data Security Protection.2.41 RAT – Remote Access Trojan Protection.

2.40 Vulnerability Scanning & Penetration Testing.

2.38 Release management & deployment strategy.

2.33 Network Segmentation and Micro-segmentation.

2.32 CASB – Cloud Access Security Brokers.

2.26 Gateway – Traffic Management and Security.2.25 PAM – Privileged Access Management.2.24 EDR – Endpoint Detection and Response.2.22 Application Process Control & Elevation.2.17 Windows OS Optimization – Forget what you THINK you know about Windows.2.15 Application Delivery Strategy – Masking, Layering, Streaming, Hosting, Containerizing, Just in Time.2.9 Active Directory – the silent killer of VDI environments.

2.6 Profiles & Personalization – The user’s “stuff”.2.1 IAM – Identity and Access Management.2 Identifying and building Foundational VDI by targetting the dependency layers….

Requirements for vmware vdi solution