From e29411e58ff2e27a2904dfd11042f2922b73100e Mon Sep 17 00:00:00 2001
From: Manoj Ampalam <manojampalam@live.com>
Date: Thu, 30 Mar 2017 09:56:20 -0700
Subject: [PATCH] Updated Install Win32 OpenSSH (markdown)

---
 Install-Win32-OpenSSH.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Install-Win32-OpenSSH.md b/Install-Win32-OpenSSH.md
index 0174664..67443a9 100644
--- a/Install-Win32-OpenSSH.md
+++ b/Install-Win32-OpenSSH.md
@@ -4,7 +4,7 @@
 * Extract contents to `C:\Program Files\OpenSSH`
 * Start Powershell as Administrator
      * `cd 'C:\Program Files\OpenSSH'`
-* On Windows 10, in developer mode, a different implementation of SSH exists in-box. Look for TCP port bindings on port 22
+* On Windows 10, in developer mode, a different implementation of SSH exists in-box. Look for TCP port bindings on port 22 and these processes - “SSH Server Broker” and “SSH Server Proxy”
      * `netstat -anop TCP`
      * If you do see 22 occupied, [#610](https://github.com/PowerShell/Win32-OpenSSH/issues/610) has workarounds to deal with port conflict. 
 * Install sshd and ssh-agent services.