- 新しい順
- 投票が多い順
- コメントが多い順
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.
関連するコンテンツ
- 質問済み 3年前
- AWS公式更新しました 3ヶ月前