Deploying to your Windows server hosted with [CyberShieldRDP](https://cybershieldrdp.com/) is very simple with DeployHQ. CyberShieldRDP provides Windows VPS and RDP servers. To deploy via DeployHQ, you'll need to enable OpenSSH Server on your Windows instance.

Firstly, you'll need to set up your DeployHQ project, then connect to your CyberShieldRDP server.

## Setting up your project

Head to the **Projects** screen in DeployHQ, then click the **New Project** button to get started.

You'll be prompted to enter a name for your project, then select where your repository is hosted.

{screenshot: 9}

Next, click **Create project** and you'll be taken to a screen where you can log in with your repository hosting account to authorise access and then choose your repository.

* [Adding a Bitbucket repository](Article: #17)
* [Adding a Codebase repository](Article: #19)
* [Adding a GitHub repository](Article: #21)
* [Adding a GitLab repository](Article: #23)
* [Adding a repository manually](Article: #25)

## Setting up CyberShieldRDP

Once you've configured your repository, you'll need to connect to your CyberShieldRDP Windows server. Since DeployHQ connects via SSH/SFTP, you'll first need to enable **OpenSSH Server** on your Windows instance.

### Enabling OpenSSH Server

Connect to your server via RDP, then open PowerShell as Administrator and run:

```powershell
Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0
Start-Service sshd
Set-Service -Name sshd -StartupType Automatic
```

This installs and starts the OpenSSH server, and sets it to start automatically on boot. You may also need to allow port 22 through the Windows Firewall:

```powershell
New-NetFirewallRule -Name "OpenSSH-Server" -DisplayName "OpenSSH Server (sshd)" -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22
```

For more detail, see our guide on [OpenSSH on Windows](https://www.deployhq.com/blog/case-study-accelerating-windows-server-deployments-with-deployhq).

### Adding the server in DeployHQ

Head to **Servers & Groups**, and click the **New Server** button at the top of the screen. If you've just added your repository, you will have been taken to this page automatically.

Start by entering a name, and choosing SSH/SFTP as the protocol:

{screenshot: 557}

Enter your CyberShieldRDP server's **IP address** as the hostname, your Windows **username** (usually `Administrator`), your password, and leave the port blank to use the default (22).

{screenshot: 594}

For the **deployment path**, the standard IIS web root is `C:\inetpub\wwwroot`. If you're deploying a different type of application, enter the appropriate Windows path.

Within **Deployment options**, you can choose to automatically deploy your server and, if you're only deploying files from a certain directory in your repository, enter a **Deployment subdirectory**.

{screenshot: 423}

Click **Create Server** to finish, then you can proceed to start your first deployment.

## Run your first deployment

By default, DeployHQ will upload the whole repository to your server on the first deployment, because there is no previously deployed commit to compare to.

If your files are already on your CyberShieldRDP server and up to date with the latest commit, you can follow this guide to skip that first deployment:

* [Don't deploy your whole repository on the first deployment](Article: #129)

Otherwise, just follow this guide to start your first deployment, then after the first deployment, only files that have changed will be uploaded in future.

* [Running your first deployment](Article: #43)

That's it! You've now set up and run your first deployment to your CyberShieldRDP server and your future changes will be uploaded for you automatically, or at the simple click of a button.

## Further reading

DeployHQ has a number of very useful features to help with your deployments in general that you might wish to find out more about:

* Compiling assets and javascript with the [Build pipeline](Article: #301)
* Running commands on your server with [SSH commands](Article: #57)
* Stop certain files from being uploaded in deployments using [Excluded files](https://www.deployhq.com/support/excluded-files)
* Keep important files safely away from your repository using [Config files](Article: #47)
* Keep your team in the loop and run other useful tasks during a deployment with our [Integrations](Article: #327)