How to set up a distributed domain on windows?

Question

1C

Colleagues, good evening everyone.
Tell me how to do it correctly and reliably.
Now there is a domain on windows 2003 + exchange 2003 + 1c 8.2 + file server.
The task is to transfer the mail server + 1s to the cloud on VPS. In the office on the server, leave everything white and fluffy (about 500 GB of documents and PDF).
I ask you to outline the infrastructure and working solutions in general terms if anyone uses this.

Answer 1

To be honest, it's a strange statement of the problem. it will be easier to buy your new server and hire another specialist to maintain it. 1c in the cloud will cost you about half a year = a good new server. Unless, of course, you have a couple of boons in the program, then maybe the server is not needed))))
As I understand it, today you have nothing else on the server except for 1s, mail and file trash. The task is to leave only garbage on the server, right?)))

Answer 2

So, if I understood everything correctly from the meager introductory, you either need to make a remote infrastructure yourself (choose a DC, order a server (s) there, and iron ones are better, not virtual ones, if we are talking about 1C), then build a tunnel in the network of this DC (GRE + IPSec or OpenVPN) and replicate your domain there, transfer 1C and mail. Moreover, if you now have exchange on its own (not in the domain), but you want to add it to the domain, then import old mail into it, if possible, it is very painful, because domain accounts in exchange will be different from those currently available.
The second option is to take cloud servers in Azure for your tasks. But this scenario is poorly customizable. Despite the fact that your domain is old, already 2003, there is no such thing in Azure, probably.