Best Practices for Windows Layered Management, a video from BriForum 2011 - Videos - BrianMadden.com
Brian Madden Logo
Your independent source for desktop virtualization, consumerization, and enterprise mobility management.
Videos's Blog

Past Videos

Best Practices for Windows Layered Management, a video from BriForum 2011

Written on Mar 27 2012 2,466 views, 0 comments


by BriForum Video

(this was originally posted in August, 2011)

 

Presented by: John Whaley

 

Layering is a promising new way of managing Windows installations. Rather than having to individually manage each Windows instance, you can split Windows into individual layers that can be managed independently. This makes it possible to manage a single base image while still allowing user-specific customizations (including user-installed applications, drivers, system services, etc.) to be layered on top. Layering makes desktop management vastly more scalable, makes updates and refreshes much easier, improves performance, reduces storage, and gives you instant recovery from malware attacks. However, there are some challenges that come up when trying to manage Windows while using layers. How do you separate data into each layer so the user data is kept while administrators can still update the base image? How do you deal with conflicts between layers, when both the administrator and user update the same files and registry keys? How do you treat tricky software like anti-virus software, Windows updates, and application virtualization packages? This session will cover best practices we have learned over the past two years working with customers on their layered Windows (XP and 7) deployments. These best practices are vendor-independent and apply equally well no matter which layering product you choose.

 

Click to browse all of the BriForum 2011 videos.

 
 




Our Books


(Note: You must be logged in to post a comment.)

If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.