Updated TTY PTY support in Windows OpenSSH (markdown)

TTY-PTY-support-in-Windows-OpenSSH.md

@@ -22,7 +22,7 @@ If you are using the openssh client,
 
      If you want support for the VT100+ sequences then please upgrade to windows 10+ OS or use the third party tools like putty, Cygwin, etc.
 
-## For UNIX users   
+## Windows SSH Client to UNIX SSH server  
 If you want to use vi / top / man, etc commands while connecting from windows client to Linux server then please follow these steps   
 
 1) Upgrade to windows 10+ OS.   
@@ -34,10 +34,48 @@ If you want to use vi / top / man, etc commands while connecting from windows cl
 3) Set the Screenbuffer width, window size width to >= 90.   
 ![image](https://cloud.githubusercontent.com/assets/23668037/23882328/11ed4116-081d-11e7-87e0-757680ea3a74.png)
 
-4) Set the environment variable (TERM) to xterm. Before/After logging into the SSH server.   
+4) Set the environment variable (TERM) to xterm. Before logging into the SSH server.   
     c:\test\> set TERM=xterm   
     c:\test\> set TERM (This should show the term set to xterm)  
 
+## UNIX SSH Client to WINDOWS SSH server  
+1) Set the environment variable (TERM) to xterm. Before logging into the SSH server.
+    c:\test\> set TERM=xterm   
+    c:\test\> set TERM (This should show the term set to xterm)
+
+## WINDOWS SSH Client to WINDOWS SSH server  
+1) Set the non-legacy console mode in the console properties,   
+   Make sure you **uncheck** the "use legacy console"   
+![image](https://cloud.githubusercontent.com/assets/23668037/23882278/cc062726-081c-11e7-8e4c-792da6af23b9.png)    
+
+2) Set the Screenbuffer width, window size width to >= 90.   
+![image](https://cloud.githubusercontent.com/assets/23668037/23882328/11ed4116-081d-11e7-87e0-757680ea3a74.png)
+
+3) If your windows client machine is **windows 10 or above ** and if you have any issues,   
+
+   a) set the environment variable SSH_TERM_CONHOST_PARSER to 0    
+           c:\test\> set SSH_TERM_CONHOST_PARSER=0    
+           c:\test\> set SSH_TERM_CONHOST_PARSER (This should show "0")    
+
+   b) exit the current ssh session (if any)     
+
+   c) start a new ssh session.    
+
+   d) if you are NOT able to reproduce then it is the windows 10 console issue. Please let us know by filing an issue, so that we will update the known issues. FYI, the fix should come from the windows 10 console team but not from the SSH team.    
+
+   e) if you are able to reproduce then file an issue.    
+
+
+## Known windows 10 console issues (These will be fixed by the windows console team)
+### When connected to unix ssh server   
+a) vi command, the up/down/left/right arrow keys are not working. Please use h,j,k,l as an alternative.    
+b) vim command, intermittently the file is opened in the Replace mode.     
+c) top command, clears the previous screen contents.    
+
+### When connected to windows ssh server and using powershell    
+a) while executing an unknown command (abcdef) in the powershell, the last line ( + FullyQualifiedErrorId : CommandNotFoundException) is not displayed on the console
+
+
 ## Testing  
 We have tested different scenarios,   
 1) Windows client (cmd.exe / powershell) to windows server   
@@ -50,12 +88,3 @@ While making any terminal code changes, please make sure below manual test cases
 2) The backspace, delete, home, end functions keys should work properly.
 3) "cls" should clear only the visible window (windows 10+ OS) / should clear entire buffer (prior versions of windows 10 OS).
 4) When connected to unix ssh server, the basic commands like vi, top, man, clear, etc should work properly.    
-
-## Known windows 10 console issues (These will be fixed by the windows console team)
-### When connected to unix ssh server   
-a) vi command, the up/down/left/right arrow keys are not working. Please use h,j,k,l as an alternative.    
-b) vim command, intermittently the file is opened in the Replace mode.     
-c) top command, clears the previous screen contents.    
-
-### When connected to windows ssh server and using powershell    
-a) while executing an unknown command (abcdef) in the powershell, the last line ( + FullyQualifiedErrorId : CommandNotFoundException) is not displayed on the console