1. First, install Diskeeper Administrator edition. If you do not already have Diskeeper Administrator, you can download fully functional 45-day trialware from http://www.condusiv.com/downloads/ and use the software –during the trial period – to quickly and easily deploy Diskeeper across your network. If you have more than 10-20 machines to which you plan to install software, Diskeeper Administrator will save you significant time.
2. After installing Diskeeper Administrator, return to the Diskeeper installation package file(s) you downloaded and double-click the VLLanguageDiskeeperVersionProductEditionName.exe file (this is a self-extracting file).
   This will extract the Diskeeper software into the current folder, and if supported by the Diskeeper edition you are installing, subfolders will also be created and labeled X86 (for Diskeeper running on Windows 64-bit operating systems). When the extraction process is complete, you will see something similar to this:
   
   The extraction process also extracts an Autorun.exe program which can be ignored. (It is only used for local system installations).
3. After the files have been extracted, the installation will automatically start. When you are prompted to click NEXT to install, do not continue the process. Instead, select the option to cancel the installation (unless you want to also uninstall the software on the local system).
4. To install Diskeeper with Diskeeper Administrator, you also need product license files corresponding to the Diskeeper edition(s) you are installing. License files (License.dal) can be downloaded from the same web location where you downloaded the Diskeeper software.
   
   Select the Admin License link and when prompted, browse to the folder where you downloaded the Diskeeper installation package.
   NOTE: You will need a separate License.dal file for each Diskeeper edition you are installing. These individual License.dal files must be saved in separate locations.
5. Launch Diskeeper Administrator and run the Add License Files wizard.
   
6. Browse to the License.dal file for each Diskeeper edition you plan to deploy. (These license files will be located in the folders you specified when you downloaded them). The new License.dal file will update Diskeeper Administrator to the appropriate number of licenses for each edition, allowing you to then deploy Diskeeper across your network.
   NOTE: to be able to browse to a folder on a remote machine, ensure the folder on the remote machine with the Diskeeper license and installation files is “shared”.
7. Once your license files have been added to the Diskeeper Administrator database, run the Install wizard.
   
8. Upon reaching the screen included below, select the Diskeeper edition at the top and then select the BROWSE button near the bottom of the page. Use the pop-up window to locate and import the Setup.exe files for both 64-bit and 32-bit (respectively kept within the X64 and X86 folders received in Step 2).
   
9. Once those files are imported, you’ll be ready to proceed with your push-installations now and for the future. There is no need to select either of the imported packages for your push installs. Feel free to select a mixture of 32 and 64 bit machines to push to and Diskeeper Administrator will deliver the appropriate package for each machine pushed to. The only thing to delineate about the pushes is that you do not mix “Editions” (eg. don’t push Diskeeper Professional to a Windows Server machine).

1. Open up Diskeeper Administrator.
2. Click on the Manage Computers and Software menu and select Manage Software Licensing.
   
3. Click on the License in the bottom frame to highlight it.
4. Then click on the ACTION menu and select "Apply Selected License."
   
5. Select the systems that are showing up as trialware and apply the license, or you can simply select
   

Yes, it certain can. As database files can become fragmented in the same fashion that all other files can become fragmented, the result can increase the I/O’s necessary to access these files. Compound that with the frequent use that databases go through and the problem can be very evident. Diskeeper works just fine with a variety of databases, small and large, ranging from SQL, Exchange, SMS, Sybase, Oracle, Informix, etc.

Diskeeper is not however a solution for the “internal fragmentation” that a database may suffer. Such “internal fragmentation” may still require a reindex (found within the database management itself).

• Server error or file not found error:

Sometimes, if the link gets wrapped onto two lines in your email then the whole link does not get used. If this appears to be the case, try copying the first line of the address and pasting it into the address bar of your web browser and then copying and pasting the second line into your browser (at the end of what you already pasted).

Diskeeper has no special “bad block” handling logic.

Diskeeper uses the Windows MoveFile.API to read from and write to all clusters on a volume. The Windows Operating System however, can detect that an I/O was attempted to a bad cluster and can then return an error to Diskeeper. The Windows Operating System will then mark the volume as “dirty” and require that CHKDSK run to clean it up.

Wherever CHKDSK is defined on a volume, Diskeeper will not run until that is cleared up.

Updated User Interface - Fresh new user interface with an easy simplified navigation that allows users to see what is happening at a glance, but still provides drill–down architecture of information for those that want it.

Disk Health Monitoring - Monitors SMART disk data; checks for other critical file system problems; warns of critical problems or an imminent disk failure; generates alerts by e-mail for 24/7 monitoring.

System Monitoring – Collect statistical data about system I/O usage, disk state, Diskeeper effectiveness, etc.; sends data for analysis; provides summary of the statistical data gathered for system performance monitoring purposes.

HyperBoot™ – HyperBoot technology improves boot times.

CogniSAN™ – Detects external resource usage within a shared storage system, such as a SAN, and allows for transparent optimization to minimize resource contention without intruding in any way into SAN–layer operations.

I-FAAST® 2.0 - Honors file exclusion which improves compatibility with third party applications while allowing finer adjustment by the sys admin in specialized situations.

HyperFast® 2.0 – Organizes user data using SSD and TRIM to improve performance. Included standard with all Diskeeper 12 editions.

Space Reclamation Engine (for Server editions) – The new Space Reclamation engine is designed to zero out blocks of unused space on SANs and thin-provisioned volumes in virtual environments so that the controller or hypervisor will reclaim the blocks and free them up, giving you more available space for your virtual machines.

IntelliWrite is the ground breaking technology that prevents the majority of fragmentation from ever occurring, dramatically improving Windows system performance.

A small percentage of fragmentation is not preventable and will be eliminated by Automatic Defragmentation. The combination of IntelliWrite and Automatic Defragmentation will keep your system running at optimum performance in the most effective and efficient way possible.

Prevention of fragmentation with IntelliWrite has been found to be more efficient than other defragmentation methods. IntelliWrite reduces the need for disk head movement and results in a reduction of system resource usage and power consumption.

Note: IntelliWrite requires more than 2 GB of free space to run.

• Home
• Professional
• Server

Open the Volume Properties task group and select the IntelliWrite option to navigate directly to the IntelliWrite properties page.

In the Computer pane, select the volumes you want to address and toggle the checkbox to the desired setting. Click OK to save your changes and close the Volume Properties console, or click Apply to save your changes and keep the Volume Properties console open.

This section of the Dashboard tab explains that IntelliWrite increases system performance by preventing fragmentation before it happens.

IntelliWrite System Statistics for All Volumes Since the Previous Day

This section of the Dashboard Tab includes statistical information regarding fragmentation prevented by IntelliWrite, fragmentation eliminated by Automatic Defragmentation, and a sum of the two numbers since the previous day.

It is important to note that the amount of fragmentation prevented is an estimation determined by a large number of factors and extensive testing. The IntelliWrite graphs are designed to approximate fragments prevented across a wide range of applications and must incorporate various types of file writes and modifications into a singular display. In some cases the charts may over-estimate and in other cases, underestimate. For example, on SQL Server® the graphs may overestimate about 10% of the fragmentation prevented, on Microsoft® Office documents it may underestimate the number of fragments prevented by 80%. What is important is that with IntelliWrite enabled, fragmentation is being handled, before it happens. The end result of having Diskeeper with IntelliWrite and Automatic Defragmentation working is a system running at peak performance in the most efficient way possible (without fragmentation).

The statement: “Proactive prevention is the most energy efficient method to eliminate increased storage power consumption caused by fragmentation,” points out that when IntelliWrite is handling your system’s fragmentation, it is reducing the amount of disk head movement previously needed to accomplish defragmentation and therefore is reducing Diskeeper's total system resource footprint.

System Fragmentation Prevention Graph

This section of the Dashboard tab shows system fragmentation prevented by IntelliWrite in real-time. In the graph, fragmentation prevented every second, within the last minute, for your entire system, is displayed in green. The scale on the left side of the graph pertains to the number of fragments that have been prevented and the scale along the top of the graph pertains to the seconds in the last minute.

Statistical Information for Selected Volume(s) Since the Previous Day

This section of the Dashboard tab shows statistical information for selected volume(s) since the previous day. The columns of the table include the name of the selected volume(s), whether or not IntelliWrite and Automatic Defragmentation are enabled, the number of fragments prevented, the number of fragments eliminated and file read/write time % improvement.

1) Does the volume in question have more than 2GB of free space? If not, then free up some disk space on that volume and wait for an hour. IntelliWrite® needs more than 2GB of free space in order for it to be enabled on the volume; Diskeeper checks the free space status hourly and enables or disables IntelliWrite accordingly.

2) Verify that IntelliWrite is enabled on the volume by checking the status of IntelliWrite in the Computer Pane. If it is not enabled, then enable it.

The following error messages can occur if the Diskeeper® service is not installed properly or is not running:

Please take the following steps to resolve the issue:

1. Reboot the system, wait for the system to fully boot up and then try to open the Diskeeper program.
2. Check the system volume (usually your C: volume) to ensure there is at least 5% free space; some services that Diskeeper depends on can get interrupted if the free space is too low on the system volume.
3. Uninstall Diskeeper, reboot the system and re-install Diskeeper. (You can re-download your Diskeeper software from your Condusiv Account – go to www.condusiv.com to login.)
4. Verify that the Windows Event Log service is running.
5. Some antivirus products, firewalls or security products that detect spyware can prevent the Diskeeper service from running. Please register Diskeeper on the safe list for these products if they are installed on your system.
6. If the above steps failed to resolve the problem, please submit a Technical Support Request.

Sometimes an error can occur during installation leaving you with a partly installed product which then causes subsequent installation attempts to fail as well.

This can also happen when uninstalling a product.

Fortunately, Microsoft has created a Fix it utility that you can run to clean up installations.

Please visit the following website to learn more about the Microsoft Installation Fix it utility.

http://support.microsoft.com/mats/Program_Install_and_Uninstall

Run this program to resolve problems that prevent Diskeeper® or Undelete® software from being completely uninstalled.

Once this is done, you should be able to install your purchased software without any issues.

For download links to your purchased software, please visit http://my.condusiv.com and login using the email address that you provided when you purchased your software.