Ccboot Image Link May 2026

On the CCBoot server, image links are not always traditional filesystem symlinks. Instead, they are entries stored in the CCBoot database (ccboot.mdb or SQL) and reflected in the Client configuration tab. The actual disk images (.vmdk, .vhdx, or raw) reside in a folder like:

C:\CCBoot\Images\

Each client’s link specifies:

In the image properties:

| Error Message | Likely Cause | Fix | |---------------|--------------|-----| | Cannot find image file | Wrong path or missing file | Verify path in Image Properties. Check file permissions. | | Access denied to image link | Share permissions issue | Grant Everyone or Domain Computers Read/Execute on the share. | | Image link corrupted | VHD/VHDX file damaged | Run chkdsk on the image file. Restore from backup. | | Write cache link failed | Cache folder missing or full | Create the cache folder. Enable NTFS quotas or free space. | | Client boots wrong image | Incorrect client-image mapping | Check client's MAC address binding in CCBoot database. | ccboot image link

The most critical aspect of an Image Link is how it handles write operations. On the CCBoot server, image links are not

Instead, CCBoot uses a Write-Back mechanism. Each client’s link specifies: In the image properties:

When a client using an Image Link restarts, the "Write-Back" data is discarded. The system reverts instantly to the pristine state defined by the Master Image. This is why diskless systems are virus-proof and maintenance-free—every reboot is a fresh install.