Updated the info in Remediation and added tabs

Author: SnehaSudhirG

articles/migrate/troubleshoot-appliance.md

@@ -6,7 +6,7 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: troubleshooting
 ms.service: azure-migrate
-ms.date: 09/23/2021
+ms.date: 01/23/2024
 ms.custom: engagement-fy23
 ---
 
@@ -211,7 +211,7 @@ The validation of a physical server fails on the appliance with the error messag
 
 ### Remediation
 
-**Linux servers:**
+#### [Linux servers](#tab/linux)
 
 Connect to the target server that's failing validation. Run the following commands to see if it returns the BIOS GUID of the server:
 
@@ -224,7 +224,11 @@ You can also run the commands from the command prompt on the appliance server by
 ssh <username>@<servername>
 ````
 
-**Windows servers:**
+Few Linux machines like Oracle/CentOS have a configuration value that requires **tty** option to be enabled by default which in turn causes an error. In such cases, you can disable this setting by adding **a!** character in the */etc/sudoers* file. You can also add the following at the end of */etc/sudoers/ file to ensure that no other configuration in this file can override the following:
+- Defaults    !visiblepw 
+- Defaults    !requiretty 
+
+#### [Windows servers](#tab/windows)
 
 Run the following code in PowerShell from the appliance server for the target server that's failing validation to see if it returns the BIOS GUID of the server:
 
@@ -255,6 +259,8 @@ $HostIntance | fl *
 
 When you run the preceding code, you need to provide the hostname of the target server. It can be IP address/FQDN/hostname. After that, you're prompted to provide the credentials to connect to the server.
 
+---
+
 ## "No suitable authentication method found" error occurs for the server during validation
 
 You get the error "No suitable authentication method found" when you try to validate a Linux server through the physical appliance.