Exam 70-742 topic 1 question 241 discussion

As per this link: https://docs.microsoft.com/en-us/windows-server/administration/server-core/server-core-roles-and-services Identity Federation Support is included in Core, just disabled by default. None of the answers really match up, the only one it could really be is A, but installing that feature installs asp.net anyway. Odd one.

None of these make sense. Just spun up a Server 2016 VM Core and the installation of ADFS went smoothly on it without any errors. So there doesn't seem to be any specific requirements for it to work on Core.

https://docs.microsoft.com/en-us/windows-server/administration/server-core/server-core-roles-and-services This link says Identity is included in Windows Server Core 2016

The answer is B. You need to install a new server with GUI. 1. So you need GUI "On Server Core installations, the optional Identity Federation Support role service for the AD RMS server role is not supported. This is because Identity Federation Support relies on a role service of the AD FS Server role, the Claims-aware Agent, which is disabled on Server Core installations." https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831554(v=ws.11) 2. But you can`t install GUI on WS2016 core: Unlike some previous releases of Windows Server, you cannot convert between Server Core and Server with Desktop Experience after installation. For example, if you install Server Core and later decide to user Server with Desktop Experience, you should do a fresh installation (and vice versa). https://cloudblogs.microsoft.com/windowsserver/2017/04/05/switching-between-windows-server-2016-server-core-and-desktop-experience/

c is correct. server core 2016 have .net 4.5 installed https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements

This is what I found on MSDN. Windows Server 2016 (all editions) includes the .NET Framework 4.6.2 as an OS component, and it is installed by default except in the Server Core configuration. Ref: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/f3e6a54a-a7a8-441f-8942-2e31db3c62a4/net-framework-versions-on-windows-server-2016-standard?forum=netfxsetup#:~:text=Windows%20Server%202016%20(all%20editions,It%20also%20includes%20the%20. The answer should be "A" for Server core.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/f3e6a54a-a7a8-441f-8942-2e31db3c62a4/net-framework-versions-on-windows-server-2016-standard?forum=netfxsetup#:~:text=Windows%20Server%202016%20(all%20editions,It%20also%20includes%20the%20. The answer should be "A" for Server Core.

This is what I found on MSDN. Windows Server 2016 (all editions) includes the .NET Framework 4.6.2 as an OS component, and it is installed by default except in the Server Core configuration. Ref: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/f3e6a54a-a7a8-441f-8942-2e31db3c62a4/net-framework-versions-on-windows-server-2016-standard?forum=netfxsetup#:~:text=Windows%20Server%202016%20(all%20editions,It%20also%20includes%20the%20.

C. Run the Add-AdfsClient cmdlet.

As far as i remember, Desktop experience can no longer be Installed after the core option has been installed. That ended with 2012 R2. And the first thing I would do is not .NET Framework. C is correct

This is wrong in its entirety. Identity Support ROLE is an option to do forest and domain trusting via AD RMS. It has nothing to do with ADFS. Furthermore, Server core supports AD RMS since Server 2012... .NET is not a required feature for RMS as far as I know. Throw this question out.

Maybe someone can assist. In an attempt to remove A: installing NET-Framework-45-ASPNET out of the selection, I attempted to look up the requirements for ADFS. https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/overview/ad-fs-requirements It does not specify and i'm unable to determine if it's actually required. The scenario states it is already running RMS. If they both share the same framework requirements, then A has already been completed. Additionally going on what Jingoism listed. https://docs.microsoft.com/en-us/windows-server/administration/server-core/server-core-roles-and-services It shows that ADFS is capable of running on Server Core 2016. The cmdlet is possible to run. However we configure it after installing ADFS isn't what the question was asking. I believe B is the correct answer.

Identity Federation Support is a role service of active directory rights management server. i ran a 2016 datacenter vm installed the ADRMS role using Install-windowsfeature -name ADRMS then installed the identity federation role service using Install-windowsfeature -name ADRMS-identity the command ran and installed both features. no errors ran the get-windowsfeature cmdlet and the identity federation support was successfully installed. ADFS is not needed for the identity federation support role service.

the correct answer is A because the question is what you need to do first before install the AD FS. you need to install the .netframework4.5 first (What should you do first?)

I found this: https://docs.microsoft.com/en-us/windows-server/administration/server-core/server-core-roles-and-services And here you can see that ADFS is an optional feature in core 2016 (but isn't installed by default) So can you install ADFS by the command add-adfsclient? Well, microsoft say: https://docs.microsoft.com/en-us/powershell/module/adfs/add-adfsclient?view=win10-ps The Add-AdfsClient cmdlet registers an OAuth client with Active Directory Federation Services (AD FS). In order to allow access from OAuth clients to resources secured by AD FS, you need to register the OAuth client with AD FS by using this cmdlet. When you register an OAuth 2.0 client with AD FS, you must specify a client identifier and a redirection URI, as well as a friendly name and description, for the OAuth client. When an OAuth client requests access to a resource using the OAuth 2.0 protocol, the client must specify a client identifier and redirection URI to AD FS, in accordance with RFC 6749. AD FS will not allow access to a resource to clients that specify a client identifier or redirection URI that are not registered with AD FS.

I found this page which relates to Server 2012 Core. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831554(v%3Dws.11) It says you can't install the optional role on Core because Identity Federation Support relies on a role service of the AD FS Server role, the Claims-aware Agent, which is disabled on Server Core installations. So assuming this functionality hasn't been added in 2016 I would say the answer is B.

I believe the ANSWER IS B. https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/hh831554(v%3Dws.11) About 3/4 of the way down this page it explicitly states that this feature is unavailable in Core because it relies on the Claims-aware agent that is unavailable in Core installations.