This content has been marked as final. Show 2 replies
VDI mostly reads data (users) from Active Directory.
The only 'write' action VDI does in Active Directory is to delete the machine from AD when the cloned desktop is destroyed (provided the Administrator you configured in VDI to access AD has 'write' access to the machine location).
Some customers with large AD deployments (multi-sites), have reported a problem with VDI (3.3.x) where new machines cannot be created in AD because the previous one with the same name has not yet been deleted from every site, due to the replication latency between sites.
So in VDI 3.4, we introduced a new pool setting (domain-cleanup) to disable the deletion of machines from AD (see more details in the doc http://docs.oracle.com/cd/E26217_01/E26214/html/tshoot-directory.html#tshoot-directory-computer-cleanup).