A VDI data-drive root can create folders but not files: how to repair the ACL consistently
Review advanced root permissions, OI/CI inheritance, user SIDs, persistent disks, and the master image, then repair through a pilot and controlled script or GPO rollout.

Establish a factual baseline with “D: root ACL” and “OI/CI inheritance flags”, then move to “user SID and ownership”. Use logon, desktop establishment, protocol, resource and application experience as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking D: root ACL, OI/CI inheritance flags and user SID and ownership independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · D: root ACL | Checking D: root ACL helps establish whether the failure is isolated to a specific authentication, session or desktop stage; compare it with a known-good baseline and the incident timeline. | Record the actual state of D: root ACL. Correlate client, authentication, agent and transport logs and reproduce on one controlled desktop. |
| 02 · OI/CI inheritance flags | Checking OI/CI inheritance flags helps establish whether the failure is isolated to a specific authentication, session or desktop stage; compare it with a known-good baseline and the incident timeline. | Record the actual state of OI/CI inheritance flags. Correlate client, authentication, agent and transport logs and reproduce on one controlled desktop. |
| 03 · user SID and ownership | Checking user SID and ownership helps establish whether the failure is isolated to a specific authentication, session or desktop stage; compare it with a known-good baseline and the incident timeline. | Record the actual state of user SID and ownership. Correlate client, authentication, agent and transport logs and reproduce on one controlled desktop. |
| 04 · persistent-disk mounting method | Checking persistent-disk mounting method helps establish whether the failure is isolated to a specific authentication, session or desktop stage; compare it with a known-good baseline and the incident timeline. | Record the actual state of persistent-disk mounting method. Correlate client, authentication, agent and transport logs and reproduce on one controlled desktop. |
| 05 · golden-image and clone strategy | Checking golden-image and clone strategy helps establish whether the failure is isolated to a specific authentication, session or desktop stage; compare it with a known-good baseline and the incident timeline. | Record the actual state of golden-image and clone strategy. Correlate client, authentication, agent and transport logs and reproduce on one controlled desktop. |
| 06 · pilot script and rollback | Checking pilot script and rollback helps establish whether the failure is isolated to a specific authentication, session or desktop stage; compare it with a known-good baseline and the incident timeline. | Record the actual state of pilot script and rollback. Correlate client, authentication, agent and transport logs and reproduce on one controlled desktop. |
Investigation and change sequence
- Capture a baseline for D: root ACL and OI/CI inheritance flags and compare it with a known-good system.
- Correlate evidence from user SID and ownership and persistent-disk mounting method to distinguish the direct fault from dependent symptoms.
- Only if evidence points to golden-image and clone strategy, plan a controlled change with backups, a change window and rollback triggers.
- Finally check pilot script and rollback and the real business workflow. Retest representative sign-in, application access and session or file redirection from the actual user location.
Validation and rollback evidence
- Retest representative sign-in, application access and session or file redirection from the actual user location.
- Recheck golden-image and clone strategy and pilot script and rollback against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming D: root ACL is sufficient while overlooking OI/CI inheritance flags and dependent checks.
- Changing several settings before preserving the original evidence for user SID and ownership.
- Success on one desktop does not prove all pools and access locations are healthy.
Common questions and acceptance criteria
What should be checked first?
Begin with D: root ACL and OI/CI inheritance flags. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Retest representative sign-in, application access and session or file redirection from the actual user location.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
