When a container is becoming corrupt we are finding that the VHD/VHDX is stuck on 0MB and is pretty much useless. Rather than troubleshooting/manually deleting the container it would be good if a GPO could attempt to re-create a fresh container on logon rather than mounting the same container that is obviously corrupt.
If a there was a configurable GPO that could for example delete and re-create any container that was <500mb then it would fix the corrupt container itself by re-creating it.8 votes
This is being tracked for possible inclusion. Other than size, what variables would need to be considered (if any)?
It would be really useful if you could make exclusions using the Office 365 Container like you can with the Profile Container. After speaking with an FSLogix SME this was not setup to protect the O365 Container and ensure there are no problems. As new versions have been released and the product has matured, is this something that can be introduced?7 votes
Please provide specific examples of the type of exclusions contemplated.
- Don't see your idea?