Discovery on a Linux server does not populate the Serial NumberIssue Discovery on a Linux server does not populate the Serial Number.ReleaseManagement, Instrumentation, and Discovery (MID) Server/instance where the SNC Secure Shell (SSH) client is disabled.CauseJ2SSH client was enabled. MID Server can run SSH commands using either the J2SSH client or the proprietary ServiceNow SNCSSH client. When you upgrade from Dublin or earlier, the MID Server property that controls the SSH client selection is not active in your upgraded instance, and the MID Server will use the J2SSH client by default.ResolutionEnable SNCSSH client by setting mid.ssh.use_snc to true on the MID server used for discovery. Navigate to the MID server used for discoveryAdd "mid.ssh.use_snc" and set value to "True" under configuration parametersRestart MID ServerRun discovery on the Linux server, post which the serial number would be populated