To disable device authentication, the same cmdlet was used to set the value to $false.
Device Authentication controls in AD FS 2016
The only type of device authentication supported in 2012 R2 was clientTLS. In AD FS 2016, in addition to clientTLS there are two new types of device authentication for modern devices authentication. These are:
PKeyAuth
PRT
To control the new behavior, the DeviceAuthenticationEnabled property is used in combination with a new property called DeviceAuthenticationMethod.
The device authentication method determines the type of device authentication that will be done: PRT, PKeyAuth, clientTLS, or some combination.
It has the following values:
SignedToken: PRT only
PKeyAuth: PRT + PKeyAuth
ClientTLS: PRT + clientTLS
All: All of the above
As you can see, PRT is part of all device authentication methods, making it in effect the default method that is always enabled when DeviceAuthenticationEnabled is set to $true.
Example:
To configure the method(s), use the DeviceAuthenticationEnabled cmdlet as above, along with new property:
Enabling device authentication (setting DeviceAuthenticationEnabled to $true) means the DeviceAuthenticationMethod is implicitly set to SignedToken, which equates to PRT.
PS:\>Set-AdfsGlobalAuthenticationPolicy –DeviceAuthenticationMethod All
Note
The default device authentication method is SignedToken. Other values are PKeyAuth,ClientTLS, and All.
The meanings of the DeviceAuthenticationMethod values have changed slightly since AD FS 2016 was released. See the table below for the meaning of each value, depending on the update level: