I just upgraded from VDM 2.1 to View 3.1. Our strategy in VDM was to have a pool of non-persistent desktops to hand out to our users, the thought being a universal pool of desktops would be most reliable and efficent so that if one desktop was unavailable or corrupted for some reason we could easily swap that image out for a new, in fact we had extra desktops to hand out for this purpose.
I've found out now that in view 3.1 Recompose and Refresh can't be done in a non-persistent pool. Can someone explain to me the technical reason for this and is switching to a persistent desktop strategy in order to reap the benefits of these features worth it? I see that I can do sort of a manual refresh using non-persistant, but i'd really prefer to automate it.
