Skip to content

Commit 5651a07

Browse files
Merge pull request #263211 from SnehaSudhirG/15Jan-migrate-TSG
Updated the info in Remediation and added tabs
2 parents f292d76 + 759efbd commit 5651a07

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

articles/migrate/troubleshoot-appliance.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: vibansa
66
ms.manager: abhemraj
77
ms.topic: troubleshooting
88
ms.service: azure-migrate
9-
ms.date: 09/23/2021
9+
ms.date: 01/23/2024
1010
ms.custom: engagement-fy23
1111
---
1212

@@ -211,7 +211,7 @@ The validation of a physical server fails on the appliance with the error messag
211211

212212
### Remediation
213213

214-
**Linux servers:**
214+
#### [Linux servers](#tab/linux)
215215

216216
Connect to the target server that's failing validation. Run the following commands to see if it returns the BIOS GUID of the server:
217217

@@ -224,7 +224,11 @@ You can also run the commands from the command prompt on the appliance server by
224224
ssh <username>@<servername>
225225
````
226226

227-
**Windows servers:**
227+
Few Linux machines like Oracle/CentOS have a configuration value that requires **tty** option to be enabled by default which can cause 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 the file can override this:
228+
- Defaults !visiblepw
229+
- Defaults !requiretty
230+
231+
#### [Windows servers](#tab/windows)
228232

229233
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:
230234

@@ -255,6 +259,8 @@ $HostIntance | fl *
255259

256260
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.
257261

262+
---
263+
258264
## "No suitable authentication method found" error occurs for the server during validation
259265

260266
You get the error "No suitable authentication method found" when you try to validate a Linux server through the physical appliance.

0 commit comments

Comments
 (0)