Your network contains an Active Directory domain named contoso.com. The domain
contains a file server named Server1. The File Server Resource Manager role service is
installed on Server1. All servers run Windows Server 2012 R2.
A Group Policy object (GPO) named GPO1 is linked to the organizational unit (OU) that
contains Server1. The following graphic shows the configured settings in GPO1.
Server1 contains a folder named Folder1. Folder1 is shared as Share1.
You attempt to configure access-denied assistance on Server1, but the Enable accessdenied assistance option cannot be selected from File Server Resource Manager.
You need to ensure that you can configure access-denied assistance on Server1 manually
by using File Server Resource Manager.
Which two actions should you perform?
A.
Set the Enable access-denied assistance on client for all file types policy setting to
Disabled for GPO1.
B.
Set the Customize message for Access Denied errors policy setting to Not Configured for
GPO1.
C.
Set the Enable access-denied assistance on client for all file types policy setting to
Enabled for GPO1.
D.
Set the Customize message for Access Denied errors policy setting to Enabled for GPO1.
Explanation:
Ref: http://technet.microsoft.com/en-us/library/hh831402.aspx
I believe it’s a mistake.
I have read in another documentation that if you set in GPO – “Customize message for Access Denied Errors” on “enabled”, then, in that case, you cannot configure manually from FSRM options, the desired access-denied message and this question requests precisely that. So, in this perspective, the right answers are B and C. In that article mentioned after the question, indeed appears necessary to “Enable access-denied assistance on client for all file types” with GPO.
In my tests, before turning on Enabled – “Customize message…” I was able to configure manually from FSRM this tab (Access-Denied Assistance), but after I turned on this setting and after running gpupdate /force there was no more available for me this option in FSRM. When I switched back to “Not configured”, I was able, again, to configure that message, manually from FSRM Options. Anyone could test that, with only a single VM, a DC with the FSRM role and editing the Domain Controllers policy (we are in a lab environment). Hope that helps.
0
0
answer B and D
0
0
It’s B & C
0
0
agree
0
0