RU11 finally brought support to parity. In earlier 3.x versions, you had to jump through hoops to capture a GPT disk. Now, the “Ghost Boot Disk” wizard properly creates WinPE 10/11 media that boots UEFI and captures/restores GPT partitions without losing the EFI system partition. It works, but it’s not elegant. You still see raw sector counts in the logs – a comfort to veterans, a horror to newbies.
No subscription for endpoints – you pay once per tech per year. That’s a win. Ghost Solution Suite 3.3 RU11 is like a diesel pickup truck from 2008. It’s loud, ugly, smelly, and the infotainment system is a joke. But when you need to haul 50 identical computer images through a stormy network with flaky PXE and exotic RAID controllers, it will start every single time and finish before the modern tools have finished downloading a cloud WinPE image.
You manage legacy hardware (BIOS), you need offline imaging without a network boot server, or you have a heterogeneous driver nightmare. ghost solution suite 3.3 ru11
The license server is still a separate install, and it’s temperamental. You must open ports 3115, 3116, and 1127 in your firewall. If you forget, GSS will silently fail to deploy. RU11 fixed some license checkout bugs from RU9, but it’s still not plug-and-play. Core Imaging Capabilities: Where It Shines GSS 3.3’s heart is still the .GHO (and .V2I) image format. In an age of WIM and VHDX, why use Ghost? Because it’s fast . A multicast deployment of a 20GB Windows 10 LTSC image to 50 identical Dell OptiPlexes ran at 2.4 GB/min over gigabit. That’s competitive with MDT and significantly faster than Clonezilla on heterogeneous hardware.
Let’s be honest: When you hear “Norton Ghost,” most younger IT pros think of a floppy disk from 2002. But Ghost Solution Suite (GSS) 3.3 RU11 is a different beast entirely. This is not the consumer “Ghost 15” disaster. This is the enterprise deployment workhorse that never really died—it just got a fresh bandolier of ammunition. RU11 finally brought support to parity
If you’re still on 2.x or an earlier 3.x, upgrade for the UEFI and WinPE 11 fixes. But don’t expect a renaissance. This is a mature, terminal product – and for its niche, it’s still the king of the morgue.
After installing RU11, immediately disable the “Auto-update boot disk” feature. It will try to rebuild WinPE every time you open the console. Do it manually once a quarter instead. Reviewed on: A Dell PowerEdge T640 running Windows Server 2022, managing ~800 Windows 10/11 clients across 12 subnets. Tested RU11 for 90 days in production. It works, but it’s not elegant
RU11 runs happily on Windows Server 2019/2022, and even on a lightweight Windows 10/11 admin workstation. The database backend is still Firebird (embedded) or SQL Server. I recommend SQL – Firebird chokes with over 500 clients.
You’re all-in on Microsoft Endpoint Manager (Intune/SCCM), you only deploy modern Linux, or you require a web-based dashboard.
Rating: 4.2/5 Best for: Legacy hardware support, PXE-free environments, and sysadmins who need absolute control without cloud dependencies. Worst for: Anyone expecting a modern, sleek, UI-driven, UEFI-first deployment tool.
I’ve been using GSS since version 2.5, and RU11 feels like the final, polished farewell to a classic architecture before Broadcom inevitably sunsets it. Here’s the long, unfiltered truth. Installation is refreshingly traditional. No cloud accounts, no Microsoft Store app, no 4GB RAM-hungry web console. You get a proper MSI that installs the Console, the Deployment Server, and the AIO (All-in-One) boot disk creator.