- Le plus récent
- Le plus de votes
- La plupart des commentaires
In general, I think they're looking at this wrong. First WorkSpaces snapshot the D drive every 12 hours. Under normal usage, rebuilding a WorkSpace (redeploying the OS from the bundle) will restore their profile from that last Snap. As long as the customer is updating the bundle properly / rather than creating completely new ones, they can update the existing WorkSpace without nuking the D drive.
If they want to leverage constant rebuilds, I would suggest looking at partners that offer profile layering and/or Windows File and Folder redirection. This gets the profile off the system and makes it more disposable.
This is a lot of work for little to no payoff. WorkSpaces are designed to be persistent. So leveraging post-deployment tools is far more efficient and creates less potential for issues.
Contenus pertinents
- demandé il y a un an
- demandé il y a 9 mois
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans