UAEN

cd ~servicesserver-deployment.md

Server deployment and setup

I’ll bring up a server for your task: a terminal server for the office, virtual machines, a VPN for remote work, backups. From bare hardware to every employee’s workstation, fully remotely. What you get is a working system and a guide, not a set of settings only the person who made them understands.

For
offices, companies with remote staff
Format
remote, no site visits
Under the hood
Windows Server, Hyper-V, RDS, WireGuard, PowerShell
ls ./cases/

When you need it

The office works in one program, and people need to connect from home, other locations or thin clients.

The old server is outdated, or you’re moving from your own hardware to a rented server.

There seem to be backups, but nobody has checked whether you can actually restore from them.

What I do

  • Choosing and preparing the server: RAID, Hyper-V virtualisation.
  • Terminal server (RDS): workstations for all staff, licences.
  • WireGuard VPN: a personal key for every employee, separate access for the admin.
  • Firewall: the server is invisible from outside, zero open ports.
  • Printing over remote desktop with no drivers on the server.
  • Backups: the whole server nightly, files three times a day, with a tested restore.
  • Monitoring: server status in one click and alerts on changes.

How the deployment goes

  • First a plan agreed with you. Nothing is done without a request.
  • Every change is a PowerShell script, with a snapshot of the state before it and a separate rollback script.
  • Before handover I check from the outside: a port scan and a test restore from a backup.
  • You get a guide: how to add an employee, where to see the status, what to do in case of failure.

Examples from my projects

cat ./remote-office.mdA remote office for 19 workstations

In about a week, fully remotely, I brought up a new terminal server for an office: 19 people work through their own VPN, the server is invisible from outside, and nightly copies come with a tested restore.

read the development story →

How the work goes

  1. 01
    Brief

    We dig into the task and agree on what counts as “done”.

  2. 02
    Prototype

    I show a mockup or a demo on a test bench before the main code.

  3. 03
    Build

    In small stages. A backup before every change, a rollback for each.

  4. 04
    Testing

    First on a copy of your environment, then on the live one.

  5. 05
    Handover

    A guide, I explain how to use it, and I stay in touch.

Questions

Can everything be done remotely?

Yes. The “Remote office” case was done fully remotely, without a single site visit: from the first server login to printing receipts.

Which server should I rent?

It depends on the number of people and programs. At the brief we’ll estimate the load and choose a configuration.

What about Windows and RDS licences?

I’ll tell you exactly which ones you need for your headcount. If the provider allows it, licences can be paid monthly rather than up front.

Who will look after the server after launch?

I can take it on for support, or hand it over to your admin with a guide.

How much does it cost and how long will it take?

It depends on the task. After the brief I give you the scope, timeline and price. Before the main build I show a prototype or a plan, so you can see what you will get.