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 option.
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.
Explanation:
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.Scale-Out File Server Role Fails To Start With Event IDs 1205, 1069, and 1194
http://www.aidanfinn.com/?p=14142
C
Certain requirements must be met before clustered services and applications can be successfully configured on a failover cluster.
Nodes: All nodes must be in the same Active Directory domain.
Account of the person who installs the cluster: The person who installs the cluster must use an account with the following characteristics:
The account must be a domain account. It does not have to be a domain administrator account. It can be a domain user account if it meets the other requirements in this list.The account must have administrative permissions on the servers that will become cluster nodes. The simplest way to provide this is to create a domain user account, and then add that account to the local Administrators group on each of the servers that will become cluster nodes.The account must be given the Create Computer objects andRead All Properties permissions in the container that is used for computer accounts in the domain. Another alternative is to make the account a domain administrator account.If your organization chooses to prestage the cluster name account (a computer account with the same name as the cluster), the prestaged cluster name account must give “Full Control” permission to the account of the person who installs the cluster.
Assign the computer account permissions of Cluster to the Servers OU” does not need in this case. The point is that Create Cluster wizard assigns permissions to CNO (cluster’s computer account) automatically (see the very first sentence of the article) to successfully create VCOs later.
The option Assign the user account permissions of User1 to the Servers OU” looks good
this is incomplete question.
complete one is
Your network contains an Active Directory domain named contoso.com. The domain contains two servers named Node1 and Node2. Node1 and Node2 run Windows Server 2012 R2. Node1 and Node2 are configured as a two-node failover cluster named Cluster2. The computer accounts for all of the servers reside in an organizational unit (OU) named Servers. 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 option.
B.Recreate the clustered File Server role by using the File Server for scale-out Application data option.
C.Assign the computer account permissions of Cluster2 to the Servers OU.
D.Assign the user account permissions of User1 to the Servers OU.
E.Increase the value of the ms-DS-MachineAccountQuota attribute of the domain.
Correct Answer: B
… continue…
explanation is
you can’t create a file server for general use on a clustered storage volume. instead you have to create File Server for scale-out application data.
I didn’t see in the question anything being mention about a CSV?
Storage = Cluster Disk 2 (top of the report)
Anyone else feel that’s an indication of CSV
No, Cluster Disk 2 doesn’t mean it is CSV. I have the same name on my iSCSI volume
It also says “Configuring cluster storage device.” Does that correlate to CSV?
Surely once the account is assigned the correct permissions, the file server role would need recreating yes? If that’s the case then why wouldn’t A be the answer? Built in administrator would have permission.
If you were to just assign the relevant permission that alone wouldn’t solve the problem it needs recreating.
Actually yeah I have just re-read the question and user 1 is a local account, so A would be the correct answer surely??
You can also prestage a CNO (Cluster Name Object) in AD, but there is no mention of this. Either the account that runs the wizard needs to be able to create the account, or the account needs to be pre-created. My vote is for A as the built-in Administrator account will have permissions to create the CNO in AD when the wizard is ran.
It’s the computer account of Cluster2 that needs to create the role objects in AD.
User has nothing to do with it.
Correct answer is C.
JeanMalot says:
May 3, 2016 at 1:30 pm
Surprised at the number of people that got this wrong.
Correct answer is
C. Assign the computer account permissions of Cluster2 to the Servers OU.
You guys are mixing it all up.
Please read *carefully* https://technet.microsoft.com/en-us/library/dn466519.aspx
The issue here is that computer object “File1” cannot be created in Servers OU, hence service cannot start.
The CNO (the Cluster object, in our case Cluster2) needs full access permissions on the Servers OU to be able to create VCOs (the cluster role, in our case File1). This has got nothing to do with user1.
-User1 needs full permissions on CNO (Cluster2)
-CNO needs full permissions on Servers OU
Tried it in lab: giving permissions to User1 will not allow the service to start. Giving permissions to Cluster2 on Servers OU (actually, only “create computer objects” permission is needed) will start File1 successfully.
C. Assign the computer account permissions of Cluster2 to the Servers OU
Kurt mentioned is correct by testing in lab.
give permission of Cluster2 on Servers OU (only ‘create computer object’) to start File1 successfully.
btw, you also will see a new computer object Cluster2_File1 created in Servers OU, and File1 start successfully.