Differences
This shows you the differences between the selected revisions of the page.
| 2014-09-04 | 2014-09-05 | ||
| no summary (martin) | finalizing windows inatance section (martin) | ||
| Line 31: | Line 31: | ||
| * On your instance dashboard on [[http://manage.windowsazure.com/|Azure Management Portal]] click on //Connect// on the bottom bar. | * On your instance dashboard on [[http://manage.windowsazure.com/|Azure Management Portal]] click on //Connect// on the bottom bar. | ||
| * "Open" the ''.rdp'' file and connect to the server. | * "Open" the ''.rdp'' file and connect to the server. | ||
| - | * Once connected to the server, in //Server Manager// go to //Manage > Add Roles and Features//. | + | * Once connected to the server, follow guide to [[guide_windows_ftps_server|installing secure FTP Server on Windows using IIS]]. When installing, bear in mind: |
| - | * In the //Add Roles and Features// wizard: | + | * Microsoft Azure Windows servers come with [[guide_windows_ftps_server#certificate|self-signed certificate]], so you do not need to create one. |
| - | * On //Installation Type// step, select //Role-based and Feature-based installation//. | + | * Microsoft Azure Windows servers are behind a firewall, so you need to [[guide_windows_ftps_server#firewall|configure FTP server accordingly]]. |
| - | * On //Server Roles// step, select //Web Server (IIS)//. | + | * Provision endpoint for FTP control connection: |
| - | * On //Web Server Roles (IIS) > Role Services// page, select //FTP Server// (unselect //Web Server//, if you do not need it). | + | * On //Endpoints// tab of your instance page on Azure Management Portal, click //Add// on bottom bar. |
| - | * Confirm by clicking //Install// and wait for installation to finish. | + | * On //Add an endpoint to a virtual machine// step, select //Add a stand-alone endpoint//. |
| - | * Open //Internet Information Services (IIS) Manager// | + | * Proceed to //Specify the details of the endpoint// step and select //FTP// in //Name// box. |
| - | * Go to //Sites// node. | + | ···* Complete the wizard and wait for the endpoint to be configured. |
| - | * Depending on your needs, either select //Add FTP Site// or //Add FTP Publishing// for your web site. | + | * Provision endpoints for FTP data connections according to the range you specified when [[guide_windows_ftps_server#firewall|setting up the FTP server]]: |
| - | * On the wizard you should enable //Basic// authentication, select //Require SSL// and select pre-generated SSL certificate (or request a new one). | + | * For a narrow range, provision the ports one-by-one on //Endpoints// tab of your instance page. For each port of the range, add a "standalone-alone" port with the same private and public port and a unique name (e.g. "FTP-data-5000"). |
| - | * On your site node, select //FTP Firewall support//. Enter //Data Channel Port Range//, e.g. 5000-5100. With narrow range, you will be able to provision endpoint in Azure Management Portal. With wide rage, you will have to automate this with PowerShell. In //External IP Address of Firewall//, enter //Public virtual IP (VIP) address// from the instance dashboard. | + | * For a wide range, you should better automate the task using PowerShell ''[[http://msdn.microsoft.com/en-us/library/jj152886.aspx|Add-AzureEndpoint]]'' cmdlet. |
| - | * Provision endpoint for FTP data channels according to the range you specified in previous step: | + | |
| - | * For narrow range, provision the ports one-by-one on //Endpoints// tab of your instance page on Azure Management Portal. For each port of the range, add "standalone-alone" port with the same private and public port and unique name (e.g. "FTP-data-5000"). Keep //TCP// protocol and other options to thei default (unchecked) values. | + | |
| - | * For wide range, you should better automate the task using PowerShell ''[[http://msdn.microsoft.com/en-us/library/jj152886.aspx|Add-AzureEndpoint]]'' cmdlet. | + | |
| - | For more details, see [[http://blogs.msdn.com/b/wats/archive/2013/12/13/setting-up-a-passive-ftp-server-in-windows-azure-vm.aspx|Setting up a Passive FTP Server in Windows Azure VM]]. Though note that contrary to what this guide shows, we do recommend you to require SSL connections and disallow anonymous authentication. | + | To connect to the instance with FTPS, start WinSCP. [[ui_login|Login dialog]] will appear. On the dialog: |
| - | TODO | + | * Make sure //New site// node is selected. |
| + | * On the //New site// node, select //FTP// protocol and //TLS Explicit encryption//. | ||
| + | * In //Host name// box enter a host name of your instance in format ''instance.cloudapp.net''. You will find it in //DNS Name// section on //Quick glance// sidebar of your instance dashboard on [[http://manage.windowsazure.com/|Azure Management Portal]]. | ||
| + | * Enter username and password of an account you want to connect with. Use the account you have specified when creating the instance or any other account you have created on the instance. | ||
| + | * Save your site settings using the //Save// button. | ||
| + | * Login using the //Login// button. | ||
| + | * If you are using [[guide_windows_ftps_server#certificate|self-signed certificate]], you will be prompted to [[ftps#certificate|accept it]]. | ||
| ===== Connecting to a Web Site with FTPS ===== | ===== Connecting to a Web Site with FTPS ===== | ||