Discovery of UNIX based server failed during classification when invoking uname SSH commandIssue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Discovery of UNIX based server fails during classification when invoking uname SSH command. Symptoms include seeing one of the following string in the ECC queue during classification phase: ===Service-Now EOO Marker=== ===Service-Now Exit Status Prefix=== ===Service-Now Exit Status Suffix=== ===Service-Now_Password_Prompt=== Release Instances upgraded from prior to Geneva Cause J2SSH is used on the mid server. In order for mid server to connect to target servers, it needs a ssh client. In Helsinki and older releases, there are two ssh clients in mid sever, J2SSH and SNC_SSH. J2SSH is not supported since Geneva. New instances should use SNC_SSH. Resolution Enable the ServiceNowSSH Client by adding the following mid server property: mid.ssh.use_snctrue Additional Information MID Server parameters