InvisiTasking —InvisiTasking is the foundation for Diskeeper to eliminate fragmentation in real time without affecting system resources or intruding on system demands.
Real-time defragmentation automatically handles fragmentation as it occurs, providing maximum system performance at all times!
Complete file and free space defragmentation defragmentation in the most extreme of conditions— even if your systems have only a one or two percent of free space left available or a file in millions of fragments, Diskeeper 2008 can restore lost performance and save the applications reliant on those files from major reliability failures.
"Defragmentation Intelligence" enhancements — Diskeeper’s logic controller, which detects various volume and system conditions and chooses the most effective algorithm, has been re-designed to deliver performance benefits faster and more efficiently.
Frag Shield 2.0 —boosts reliability and availability by automatically preventing crash-inducing fragmentation of critical system files.
Volume Shadow Copy Service (VSS) Compatibility mode —only Diskeeper 2008’s new VSS-compatible mode affords you the ability to leverage the data protection of VSS and the performance and reliability of automatic defragmentation.
I-FAAST 2.0 (Intelligent File Access Acceleration Sequencing Technology) automatically boosts access speeds for the most commonly used files.
Native 64 bit operating systems support.
BOOT-TIME MODE safely performs Microsoft®-recommended defragmentation of critical system files.
Network Management Support — control Diskeeper settings and functionality via Diskeeper Administrator edition or Group Policy.
Hardware Support:
Diskeeper runs on the Intel x86 platforms (including compatible CPUs from other manufacturers).
Functional limits:
Maximum supported volume size: 2TB
Disk Subsystem Supported:
Primary Partitions
Extended Partitions
Logical Drives
Volume Sets
RAID Arrays (hardware and software)
Mirrored Disks
Mounted Volumes (letter-less drives)
Operating System Support
- Windows Server 2003 Web
- Windows Server 2003 Standard
- Windows Server 2003 Standard x64
- Windows Server 2003 Enterprise
- Windows Small Business Server 2003
- Windows Storage Server 2003
- Windows Server 2003 w/ S.A.K.
- Windows 2000 Server
- Windows 2000 Advanced Server
- Windows 2000 w/ Server Appliance Kit
Supported File Systems
Microsoft NTFS (New Technology File System)
FAT16 (File Allocation Table)
FAT32 file system formats.
Resource Requirements
The disk space requirements for Diskeeper depend on several factors. On Windows Server 2003 and Windows 2000 Server systems, Diskeeper will need about 11 MB. Allow about 10 MB of extra free space for temporary files during the installation. If Internet Explorer® is not present on your computer, some other needed files (hhupd.exe, 50comupd.exe, and wintdist.exe) may be added. Further, your system may require a new or updated version of the Microsoft Management Console (MMC), which is less than 6 MB.
Additional Software Requirements</>
Diskeeper relies on the Microsoft Management Console (MMC). The MMC provides a single point of control for system utilities such as Diskeeper. The MMC is used as a central location for a variety of Microsoft and third party administrative tools. The MMC is included in Microsoft Windows 2000 and newer Windows operating systems.
A Note About Firewalls
As a normal part of its operation, the Diskeeper Service (DkService.exe) acts as a server 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 server. 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), 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.