A user named User1 is a member of the local Administrators group on Node1 and Node2.
User1 creates a new clustered File Server role named File1 by using the File Server for general use option.
A report is generated during the creation of File1 as shown in the exhibit. (Click the Exhibit button.)
File1 fails to start.
You need to ensure that you can start File1.
What should you do?
A. Log on to the domain by using the built-in Administrator for the domain, and then recreate the clustered File Server role by using the File Server for general use
B. Assign the user account permissions of User1 to the Servers OU.
C. Assign the computer account permissions of Cluster2 to the Servers OU.
D. Increase the value of the ms-DS-MachineAccountQuota attribute of the domain.
E. Recreate the clustered File Server role by using the File Server for scale-out application data option.
Scenario: You have created a Windows Server 2012 Scale-Out File Server. The cluster, including the network and storage, pass the cluster validation test.
Everything looks and is good. You create a File Server role for application data (SOFS) but it fails to start.
Problem: Basically, the cluster needs permissions to create a computer object (for the SOFS) in the same Active Directory OU that the cluster object (Demo-FSC1)
is stored in.
Resolution: Reconfigure the permissions on the Servers OU.
In this case we assign the user account permissions of User1 to the Servers OU.
Reference: Scale-Out File Server Role Fails To Start With Event IDs 1205, 1069, and 1194