tag:blogger.com,1999:blog-970736710331308901.post3386152991379712074..comments2023-09-12T15:14:03.392+01:00Comments on Application Management in the 21st Century: The Microsoft Compatiblity database - Dynamic ShimsGreg Lamberthttp://www.blogger.com/profile/07983481321915505115noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-970736710331308901.post-40231019990966281162008-08-14T04:32:00.000+01:002008-08-14T04:32:00.000+01:00I completely agree with the notion of having a bet...I completely agree with the notion of having a better (or even an existing) management story around shims, but I'm kind of curious regarding the value of a per-user shim...? If an app doesn't work, which user is going to not want to have it fixed? If you can set up the fix through policy, then that should obviate problems of permission.<BR/><BR/>Of course, you can apply layers per-user via the registry, but that's more of a convenience feature for things such as PCA, where you do have a problem of permissions.Chris Jacksonhttps://www.blogger.com/profile/05126002088601352636noreply@blogger.com