How to Install FTP Server on Windows RDP 2012

If you are working on Windows Server 2012 via RDP, you will probably need to move files more easily at some point, especially when the file size is large or you want to give specific access to users. This is where setting up an FTP Server in a basic way really comes in handy. I have set up FTP on 2012 servers several times for various FTP projects; once for automatic backups, once for delivering files to a client, and even for transferring files between two servers. My experience has been that if it is installed and configured correctly and cleanly from the start, you will encounter fewer Permission or security problems later. In this guide, we will not only talk about a simple installation, I will also add some tips that will be useful to you in practice.

Installing FTP FTP Server on RDP 2012

Step 1: Open Server Manager

Click on Server Manager from the taskbar. This is the panel where most of the Role and Feature settings are managed.

Step 2: Add a New Role

On the Dashboard page, click Add Roles and Features.

A wizard will open that will walk you through the process.

Step 3: Select the installation type

In the Installation Type section, select the option:

Role-based or feature-based installation

and click Next.

Short description: Roles are basic capabilities like IIS, and Features are their additional capabilities.

Step 4: Select Server

On the next page, the current server is selected by default. If you only have this server, click Next without changing it.

Step 5: Enable FTP Server

On the Server Roles tab:

• 1- Expand the Web Server (IIS) option.
• 2- Expand its subcategory.
• 3- Check the Enable FTP Server option.

In this section, two sub-options are usually enabled (FTP Service and FTP Extensibility). Leave them enabled by default. After selecting, click Next.

Step 6: Select Additional Features

On the Features page, you can enable additional features for IIS. If you are unsure, keep the default settings.

Useful Tip: You can add new features later from this same Wizard. So you don’t have to select everything now.

Click Next.

Step 7: Verify and Install

On the final page, a summary of the settings will be displayed. Double-check that the FTP Server is checked.

Then click Install.

A progress bar will be displayed and when complete, a message will appear stating that the installation was successful.

The installation is complete.

Beyond Installation: Initial FTP Configuration

Setting up FTP is only halfway there. If you stop here, you don’t have FTP enabled. Now you need to create an FTP Site.

Create an FTP Site

• In Server Manager, click Tools.
• Log in to IIS Manager.
• Right-click the server name.
• Select Add FTP Site.

Enter a name for the site and specify the path to the folder where the files will be located.

Personal experience: It is better to create the FTP folder on a drive other than the system drive (C). This is both better in terms of security, and the server will not be affected if the C drive becomes full.

Setting Up Binding and SSL

Next, you need to specify the IP and Port (usually Port 21). If you don’t have SSL, you can choose No SSL for now. However, if FTP is going to be open to the Internet, I recommend that you enable FTPS later.

Authentication and Authorization Settings

Here you specify who has access:

• Anonymous (for public access)
• Basic (for logging in with Windows username and password)

I usually choose Basic Authentication and create a separate user for FTP. This increases security.

Important Security Tips (Very Important in RDP)

If you enable FTP on a server you manage via RDP, take these few tips seriously:

1- Be sure to open port 21 in the Firewall as controlled.

2- Do not enable Anonymous access for no reason.

3- Create a restricted user specifically for FTP.

4- If the server is on the Internet, implement FTPS or at least IP restriction.

In one of the projects, a large number of unwanted files were uploaded to the server due to Anonymous being enabled. From that experience, I learned that FTP security is no joke, look for more tips on our website.

Testing FTP Connection

After setup, you can test with software like FileZilla or even via a browser:

ftp://your-server-ip

If the login page opens and you can log in, it means the settings are correct.

When is FTP a good option?

Although there are more modern methods like SFTP or cloud transfer, FTP is still useful in many scenarios:

• Transferring large files
• Automatic backups
• Sharing files between servers
• Delivering a project to a client

It’s just important to know when to use it and to be secure.

Conclusion

Setting up an FTP server on Windows Server 2012 is not a complicated task, but the difference between a simple installation and a professional setup is in the details, enabling the appropriate role in IIS is only the first step; creating the FTP site, managing access, properly configuring folders, and maintaining security are the things that really matter, in my experience, if you define the correct structure for users and folders from the beginning and keep access limited, you will not have any problems later in terms of both performance and security, FTP can be a simple but powerful tool on your server, provided it is set up carefully and with awareness.