I have a Server 2012 that I am trying to create a small test deployment for VDI. I have installed all the required roles and setup the template for the VDI. The problem I am having is when I try to create the VDI Collection. It will go through all the steps to create the machines but fails every time no matter if I use a Windows 7 image or a Windows 8.1 image. The error in the "Task Status Details" shows "RD Connection Broker could not create the computer account object in Active Directory Domain Services (AD DS). Ensure that the RD Connection Broker computer account has permissions to create computer accounts in the OU, the RD Connection Broker server can contact AD DS, and a duplicate computer account object does not exist in a different OU." I have gone through all the various documents to make sure that the proper permissions are set for the RD Connection Broker. I am actually thinking it is not a permission issue but something else entirely. I say that because whenever I try to create the Collection I notice there is a number of errors in the Event Viewer.
The errors in the Event Viewer are as follows:
Ntfs (Microsoft-Windows-Ntfs) Event ID: 140
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{ffe9cba8-a55b-11e3-9428-d48564437956}, DeviceName: \Device\HarddiskVolume110.
({Device Offline}
The printer has been taken offline.)
Ntfs (Ntfs) Event ID: 137 Task Category: 2
The default transaction resource manager on volume \\?\Volume{ffe9cba8-a55b-11e3-9428-d48564437956} encountered a non-retryable error and could not start. The data contains the error code.
Event ID 140 repeats 7 times
Application Popup Event ID: 26
Application popup: Windows - Delayed Write Failed : Exception Processing Message 0xc0000222 Parameters 0x000007FDD1627438 0x000007FDD1627438 0x000007FDD1627438 0x000007FDD1627438
Ntfs (Ntfs) Event ID: 50
{Delayed Write Failed} Windows was unable to save all the data for the file \$LogFile. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
This of course makes it where the VDI Collection fails. This will happen every time that I try to create a Collection Pool. I have tried to store the Collection on the local RAID array as well as a NAS iSCSI drive with the exact same results. I have updated the RAID Controller drivers as well as Firmware with no change.
What could the problem for this?
Just as additional information here is the permissions the Collection Broker has to the OU that the VMs are to be created:
BrokerServer$Create/Delete Computer objectsThis object and all descendant objects
BrokerServer$Full controlDescendant Computer objects