# Windows 2012 R2 Guide

### Introduction

Microsoft has deprecated Windows 2012 R2 however it is still widely in use in legacy environments and in some environments it is not possible to use a virtual machine to act as a jump host to transfer the data with Movebot.

In this guide - we will cover how you can setup and run the Movebot windows agent in this type of environment. 

{% hint style="warning" %}
Running a migration directly on Windows 2012 R2 is not recommended as it requires using a legacy version of the Movebot/Couchdrop windows agent that is not as robust as more recent versions and may be unreliable. If possible - we recommend using a virtual machine to connect via SMB/CIFS to the legacy server instead. 
{% endhint %}

### Requirements

To get started - you will need:

* Administrator access to the server
* A RDP session or physical access to the server
* Basic knowledge of server administration
* The windows agent - <https://couchdrop-package-repo.s3.us-west-1.amazonaws.com/couchdropcloudconnector/1.0.43/couchdrop-cloud-connector-installer.msi>
* The storage authentication token from Movebot

### Installation Steps

To install and start the agent

1. Install the package downloaded above
2. Configure the agent manually
3. Start the installed process. The front end for the agent will fail to load properly.
4. Test the connection in Movebot

### Configuring the agent manually

The agent uses a configuration file stored in the filesystem. When running the agent on windows 2012 - the GUI front end does not work so you will need to configure the process manually.&#x20;

This is relatively easy:

1. Open the configuration file with notepad - creating it if it does not already exist.&#x20;

```
 C:\Users\%username%\AppData\Local\CouchdropCloudConnector\configuration.conf
```

2. Copy the JSON configuration below - with a valid storage\_id

```json
{"storage_id":"KEY_FROM_MOVEBOT_FRONTEND"}
```

3. Save the configuration file and start the Movebot agent again.