System Requirement
*System Requirement*
Requirement of Server System
Support Windows 8.1、 Windows 10、 Windows Server 2003、Windows Server 2008/R2、 Windows Server 2012、Windows Server 2016 and Ubuntu server amd64 version. Windows Server 2008/ R2、 Windows Server 2012 or Windows Server 2016 recommended.
All disk partitions should be formatted as NTFS. When format disks, set "Allocation unit size" as "Default" for Windows system disk, and set "Allocation unit size" as "64K" for other disks.
Requirement of Network
You can use the built-in DHCP and TFTP functionality of cloud desktop, or use a third-party DHCP and TFTP server plus iShareDisk PXE boot files. Support 100MB - 1GB network, 1GBPS network recommended when diskless boot, please use VHD raw boot in 100MBPS network.
Requirement of Client System:
Windows XP, Windows Vista, Windows 7, Windows 8.1, Windows 10, Windows Server 2003, Windows Server 2008/R2, Windows Server 2012, Windows Server 2016、Centos and Ubuntu etc.
The Windows system drive should be formatted as NTFS and set "Allocation unit size" as "Default".
Requirement of Client Hardware
UEFI or legacy BIOS
Diskless boot require support PXE 2.x network card, or V2.33 above for ROM in Realtek network card.
VHD raw boot require local disk, mSATA, SATA3, PCI-E SSD recommended.
Recommended Hardware Configuration of Server at Diskless boot:
| Scale | Configuration |
|---|---|
| 25 Clients | CPU: 2.0G RAM: 8G System Image Disk: SATA-21 250G an image file (SC 512M) compares well with SSD Game Disk: SATA-2 500G2 (Software or hardware raid as required) Write-back Disk of the 1st Client: SATA-2*1 250G Average (one write-back disk for every 35 clients) Main board: Support RAID or HCI Network Card: 1000Mb Ethernet, If possible, please use SSD hard disk as buffer and SAS the write-back disk. |
| 50 Clients | CPU: 2.8G RAM: 16G System Image compares well with SSD Game Disk: SATA-2 500G (Software or hardware raid as required) 80G,3rd SSD Generation: 80G, 3rd generation Write-back Disk of the 1st Client: SATA-2 250G Write-back Disk of the 2nd Client: SATA-2 250G Average (one write-back disk for every 35 clients) Main board: Support RAID or AHCI Network Card: 2 multi-IP or single IP static link aggregation (distribution) If possible, please use SAS as game disk and SAS the write-back disk. |
| 100 Clients | CPU: 2.8 GRAM: 32G System Image Disk: 1 SATA-2 an image file (SC 512M) compares well with SSD Game Disk: SATA-2 500G*3 (Software or hardware raid as required) SSD Disk: 80G 3rd Generation Write-back Disk of the 1st Client: SATA-2 250G Write-back Disk of the 2nd Client: SATA-2 250G Write-back Disk of the 3rd Client: SATA-2 250G Average (one write-back disk for every 35 clients) Main board: Support RAID or AHCI Network Card: Intel 1000Mb Ethernet, 2-3 multiple IP or single IP static link aggregation (distribution) If possible, please use SAS as the game disk and SSD or SAS the write-back disk. |
| > 100 Clients | Multiple servers is recommended to for load balance. |
Port opening requirements
Local policy security: Required open ports (if you need to enable firewall, you can add the server-side exe file to the exception or add the following ports as allowed)
| Forward | Port | Protocol | Service | Required | Remarks |
|---|---|---|---|---|---|
| Server | 67 | UDP | DHCP service, assign IP addresses to clients | Yes | Otherwise client PXE boot will fail or local DHCP cannot get IP address |
| Server | 69 | UDP | TFTP service, provide boot files for client PXE boot | Yes | Otherwise client PXE boot will fail |
| Server | 3260 | TCP | iSCSI service, provide disk space to clients | Yes | Otherwise client PXE boot will fail |
| Server | 3265 | TCP | Management service, provide traditional GUI management functions | No | Only if launching traditional GUI management locally |
| Server | 3266 | TCP | Connection service, receive client connection requests | Yes | Otherwise clients cannot connect to server |
| Server | 9000 | TCP | WEB service, provide browser management functions | No | Only if using browser management locally |
| Server | 9443 | TCP | WEB service, provide HTTPS browser management functions | No | Only if using browser management locally |
| Server | 8001 | TCP | WEB service, provide center server browser management functions | No | Only if using browser management locally |
| Server | 8443 | TCP | WEB service, provide center server HTTPS browser management functions | No | Only if using browser management locally |
| Server | 5500 | TCP | VNC service, receive client reverse VNC connection requests | Yes | If clients and server are across VLANs, not in the same LAN |
| Client | 3267 | TCP | P2P service, provide file transfer between clients | Yes | If client P2P transfer is needed, and not needed if in the same LAN |
| Client | 5900 | TCP | VNC service, receive server VNC connection requests or initiate reverse VNC connections to port 5500 on server. In cross VLAN environments, must ensure server can ping client. Network firewall must open 5900 or 5500 port. | Yes | If VNC is needed, and not needed if in the same LAN |