Requirements
The server
You can install the server on:
- Windows Server 2019, 2022 or 2025. We suggest Windows Server.
- Windows 11, version 22H2 or newer.
Older versions of Windows may work, but we do not support them.
You need to be an administrator to install it. The server runs as a Windows service called SharpDay Deploy Service.
You do not need to install .NET or anything else first. Everything the server needs comes in the installer.
After you install it, the server waits until an administrator finishes First time setup in the Console. Until then it does not share any folders or answer any PCs.
Important
Do not run Windows Deployment Services (WDS) on the same server. Both use the same network boot ports, so SharpDay Deploy turns WDS off each time it starts, once setup is finished.
To build boot files
To build Windows PE boot files, the server needs the Windows ADK and its Windows PE add-on from Microsoft. Install the same version of both. The About page in the Console shows if they are installed and which version we suggest. You can keep an older version if you need to.
Disk space
Windows images, Linux install files and driver packs take up a lot of space. Plan for this before you install. Setup warns you if the drive you pick for the share folder has less than 20 GB free. See The share folder.
File sharing
PCs read Windows images and drivers from the server over Windows file sharing (SMB). The Windows Server service must be running, and Windows Firewall must allow File and Printer Sharing. See Ports and firewall.
Only if you install Linux
- To send Linux install files over NFS, the server must run Windows Server with the Server for NFS role. Windows 11 can use SMB or HTTP instead.
- To send Linux install files over SMB, the server must not be a domain controller.
What setup checks
The Checks step of First time setup looks at the server and labels each result Ready, Note, Check or Problem. None of them stop you finishing setup, but fix every Problem and Check before you set up PCs.
| Check | What it looks at | If it is not Ready |
|---|---|---|
| Windows ADK | Whether the ADK is installed | Install it. You need it to build boot files and ISOs. |
| Windows PE add-on | Whether the add-on is installed, and is the same version as the ADK | Install it, or install the version that matches your ADK. Builds still run if the versions differ. |
| ADK update | Whether a newer ADK is out | Only a suggestion. You can keep the version you have. |
| Windows Deployment Services | Whether WDS is installed or running | SharpDay Deploy stops WDS for you. To keep things simple, remove the WDS role. |
| File sharing | Whether the Windows Server service is running | Start the Server service in Services. Without it, PCs cannot read images or drivers. |
| Network boot ports | Whether another program already uses UDP 69, UDP 4011, TCP 15155, or both TCP 80 and 8080 | Stop the other program, or move it to other ports. IIS often holds port 80. |
| Network address | Whether the server has an address PCs can reach | Connect the server to the network PCs will use. If it has more than one address, pick one on the Network step. |
| Licence server | Whether the server can reach the licence server on TCP 443 | Check your firewall and web proxy. The server needs it to activate its licence and get updates. See Ports and firewall. |
| Server for NFS | Whether the Server for NFS role is running | Only needed for Linux installs that read files over NFS. |
The Console
The Console runs on Windows. It must be able to reach the server on TCP port 15156.
Each person who uses the Console needs their own sign in. See Ports and firewall for the full list of ports.
The Deployment Node
The Deployment Node is optional. It needs a Windows domain. See Deployment Node.