Technical Specs & Resource Requirements
Operating Systems Supported
- Windows Server 2012
- All Windows Server 2008 & (R2)
- Windows Server 2003 SP2
- Windows Small Business Server 2003
- Supports native 64 bit mode on Windows 64 bit Operating Systems
- Supports both 32 and 64 bit Windows, but not Itanium editions.
Disk Subsystems Supported
- Primary Partitions
- Extended Partitions
- Logical Drives
- Volume Sets
- RAID Arrays (hardware and software)
- Mirrored Disks
- Mounted Volumes (letter-less drives)
- Maximum supported volume size: unlimited
Diskeeper Server Edition runs on Windows Server 2003 Web, Windows Server 2003 Standard
(x86/ x64), Windows Server 2003 Enterprise (x86/x64), Windows 2003 Datacenter Server,
Windows 2003 with Server Appliance Kit, Windows Server 2008 R2 Standard, Windows
Server 2008 R2 Enterprise (x86/x64), Windows Server 2008 Datacenter, Windows HPC
Server 2008 and Windows Small Business Server 2011 all editions and all Windows
Server 2012 editions (including compatible CPUs from other manufacturers).
The disk space requirements for Diskeeper depend on several factors. The Diskeeper
installation package is about 60 MB. After the installation is complete, Diskeeper
occupies about 45 MB of disk space.
Additional Software Requirements
Diskeeper Server requires .NET 4. If .Net 4 is not installed on your system, Diskeeper
will attempt to download and install it for you. A reboot may be required due to
the .Net installation.
A Note About Firewalls
As a normal part of its operation, the Diskeeper Service (DkService.exe)
acts as a Windows service on your system. If you are running a hardware or software
firewall, you may see messages indicating Diskeeper Service is trying to act as
a Windows service. These messages are expected; you can safely allow these events.
This functionality is designed to allow for support for network operations (e.g.
Remote Control) via Diskeeper Administrator.
You may also be notified that Diskeeper is trying to access the Internet. It is
important to note that Diskeeper does not access the Internet (except when you specifically
use the Check for Updates feature or you opt in to send performance data for analysis),
but it does use Windows mechanisms that may trigger these alerts from your firewall.
Again, these messages are expected and you can safely allow the events. If networkability
or automatic update checking is not required, you can safely disable this.
Stop fragmentation-based lags and crashes on Windows server systems in their tracks
– even when demand is at its absolute highest! Lower your operating costs and increase
your server performance with Diskeeper Server edition.