Merge your image links in Image Manager. Ensure your images are stored on a high-speed NVMe SSD, never a traditional HDD. 3. "TFTP Open Timeout" Error
The Image Link is a pointer system. You create one "Master Image" (the "Super Client" image) containing all your games and software. Then, you create Image Links for every other client PC. An Image Link does not copy the data of the Master Image; it simply points to it.
Enter a descriptive name for the recovery point (e.g., Windows_Update_June2026 ).
You can also create VHD (Virtual Hard Disk) images directly on the CCBoot server using the Disk Manager. This involves:
To update software or drivers on the image, right-click a client in the server and select Enable Super Client ccboot image link
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Need specialized hardware for CcBoot? Visit our partner page for recommended 10GbE NICs and enterprise NVMe drives that minimize image link latency.
| Error Message | Cause | Fix | | :--- | :--- | :--- | | | The physical .img file was moved, renamed, or deleted. | Go to Image Management > Properties and update the path. Restore from backup if missing. | | "Access denied to image" | NTFS permissions on the server folder are corrupted. | Right-click the CCBOOT folder > Properties > Security > Grant Everyone or Network Service full control. | | "CRC mismatch" | The image link is pointing to a corrupt sector. | Run CHKDSK on the server drive. Use CcBoot’s "Check Image" tool. | | "No super client found" | You tried to update an image without setting a super client. | In the console, right-click the client MAC > Set as Super Client. Reboot the client. | | "TFTP timeout" | The network path to the image file is too slow or blocked. | Ensure UDP ports 67, 69, and 4011 are open. Move image to a faster local drive. |
When updating images, follow this safe workflow: Merge your image links in Image Manager
CCBoot is a premier diskless boot solution that allows multiple computers to boot from a single operating system image over a local network. A critical phase in setting up this architecture is the process. Mastering this technique ensures seamless client boot-ups, reduced server load, and simplified network management. Understanding CCBoot Image Linking
Even with a perfect setup, Image Links can present issues. Here are the most common problems and their solutions:
CCBoot enables diskless booting through optimized "Super Image" VHD files for Windows, with pre-configured images available for download and a process for creating custom images. The workflow includes installing a master image, using the CCBoot client for upload, and configuring the server to manage client PXE booting. For a comprehensive guide and direct links, visit the CCBoot Super Image Wiki . Create boot image | CCBoot Cloud Wiki
The "Enable Save Map" function was not activated before booting the client, or the write-back disk on the server is completely full. "TFTP Open Timeout" Error The Image Link is
CCBoot provides visual warnings when an image disk is “full or going to be full” by appearing red in the disk list. Set up monitoring alerts to ensure you receive notifications before disks become completely full, as this will prevent all clients linked to images on that disk from booting.
A (also known as a differencing disk) is a virtual disk that stores only the changes made to a parent disk (the main image). This creates a hierarchical image link where the child disk “links” to and depends upon its parent image. This technique is extremely valuable for:
The client was switched to an image link that lacks the critical network interface card (NIC) drivers or storage controllers for that specific motherboard.
In technical terms, CCBoot supports VMDK (VMWare Disk Format), physical drive, and volume drive as boot image sources. All boot images uploaded from clients are saved with VMWare disk format (.vmdk) by default. The system also supports VHD (Virtual Hard Disk) format, making it highly flexible for various deployment scenarios. The “link” exists in multiple layers: the file path reference in the Image Manager, the client assignment settings, and the iSCSI target configuration that ultimately delivers the disk blocks to the client.