CCBoot

User Manual

Youngzsoft 2019

Single Image for Multiple Specs

Create Single Image for Multiple Specs 
2015/12/08 11:55 

The PnP function of CCBoot makes it is possible for you to create a single image for all 
client PCs with various specifications so that they can diskless boot with this single 
image. Suppose you need to implement PnP for 30 client PCs Intel, AMD and with 
different types of Video Card and Sound Card, below are the steps for you.  

Note: From CCBoot v3.0 build 20131023, we add the "Add from INF" function. With this 
new function, as long as one client can diskless boot successfully, you could use the 
CCBoot PNP tool to add NIC drivers (such as Win7 Realtek NIC drivers) from INF on that 
client directly, which is more convenient. For details, please refer to "​Add from INF​". 

1) Install Windows XP or Windows 7 on the client (suppose PC-1) which has the best 
hardware specifications. Please install Windows first on AMD client PC in this way it will 
avoid such problem like BSOD, and it is much stable to merge different drivers into one 
image in this process. 

2) Install NIC driver, chips driver and other low level drivers on PC-1. 

3) Install CCBoot Client on PC-1 and restart it as required. 

4) After rebooted, launch CCBoot Client again, and click "NIC PnP", "Install Known NIC" 
and check "Select All", then upload image from PC-1 to CCBoot server(Figure 1-1). 
  

Figure 1-1 

5) Diskless boot PC-1 by super client and install all the other drivers and software you 
need on it, insert a USB Flash Drive on PC-1, copy "C:\CCBootClient\CCBootpnp.exe" to 
the USB key, shutdown PC-1 then disable super client. Now the master image is created 
successfully(Figure 1-2). 
  

Figure 1-2 

6) Try to diskless boot all client PCs one by one with the master image. If one client PC 
can boot successfully, please go to Step 12. If one client (suppose PC-2) cannot boot 
successfully, normally it stops at the Windows logo then BSOD, it because the master 
image doesn't have the NIC driver of PC-2. So we will use CCBootPnP to collect the NIC 
drive of PC-2 and merge it to the master image. Please follow the steps at below. 

7) HDD Boot PC-2 and install the same Windows edition on it. 

8) Install NIC driver on PC-2. Only need to install NIC driver because we just need to 
collect the NIC driver of PC-2. 

9) Insert this USB key to PC-2. Run "CCBootpnp.exe" and click the "Collect Local NIC" 
button, it will create a folder in this USB Key, named "Drivers", which includes NIC 
driver of PC-2. (If there is 'Drivers' folder already before click "Collect Local NIC", that 
doesn't matter, just leave it there.). 
10) Insert this USB Key on PC-1 and diskless boot PC-1 by super client. Run 
"CCBootpnp.exe" on the USB key and click the "Merge Collected NIC" button. When 
finish, please shut down PC-1, disable super client(Figure 1-4). 

Figure 1-4 

11) Now, you are able to diskless boot PC-2 with the master image successfully. 

12) Diskless boot PC-2 by super client with restored point, install other devices' drivers 
on PC-2 if necessary. After installed or updated the drivers, shutdown PC-2 and disable 
super client. 

13) Do the same as Step 8-12 for other unable diskless boot PCs, and so on and so 
forth. 

14) If all client PCs with different specifications have successfully diskless boot by using 
one image, you need to merge the image in order not to degrade the image 
performance. Please refer to “​How to Merge Image​”. 
 

We have created a video - "​Single Image for Multiple Specifications​" on Youtube. 

   
Add New Machine into Boot Image 
2016/05/25 22:02 

An internet Cafe may have many computers that can boot from a single image, but 
when new computers are added, it may fail to boot from the image.Hence, we have 
“CCBootPNP” tool to help you add NIC driver of new computer to the image so it can be 
booted from the single image. 

Note: From CCBoot v3.0 build 20131023, we add the "Add from INF" function.With this 
new function, as long as one client can diskless boot successfully, you could use the 
CCBoot PNP tool to add NIC drivers (such as Win7 Realtek NIC drivers) from INF on that 
client directly, which is more convenient. For details, please refer to "​Add from INF​". 

Many new PC have new NIC and will not boot from image since the image does not 
have a driver for the new PC NIC’s. So, we just add the NIC drivers and the computers 
can boot from the image. 

1) First back up your master image so that you can restore it back if the procedure 
fails, on the new computer install the “CCBoot Client Application” 

2) Grab a "USB memory stick" and plug it into your old computer and copy 
“CCBootPNP.exe” file from the “CCBoot Client” installation directory to the USB memory 
stick. 
  

  

Figure 1‑1 

3) Attach a hard disk in the new PC and install Windows system. 

4) Make sure that you install the latest driver of NIC for the computer. 

5) Now, plug the previous "USB memory stick" to the computer and run the 
"CCBootPnP.exe" file inside the USB memory stick, in the pop-up dialog box click the 
"Collect Local NIC"button. 
  

  

Figure 1‑2 

6) In the"CCBootPnP" pop-up dialog box, click the "Yes" button and on the next pop 
up click “OK” button. Inside your "USB memory stick"you will see a file folder name 
"Drivers" that is the registry NIC driver package of your new computer that is collected 
by "CCBootPnP".Remove the USB memory stick from the new PC (Figure 1‑3). 

  

Figure 1‑3 
7) In your CCBoot server"Client Manager" select one of your old client computers, 
double-click to open the client properties to choose "Enable Super Client". 

8) Once the old PC with image is booted, insert your "USB memory Stick" and then 
run the"CCBootPnP.exe", click the "Merge collected NIC" button. 

  

Figure 1‑4 

9) In the"CCBootPnP" pop-up dialog box, click the "Yes" and then on next pop up click 
“OK” button. 

 
 Figure 1-5 

10) After that shutdown the computer, go back to CCBoot server and then choose 
"Disable Super Client". 

Now we can diskless boot the new PC with the old image in which we just merged the 
NIC drivers. If all goes well then the new PC should diskless boot .Once it finishes 
booting, then “Disable Super Client” and then save the image. 

Similarly, repeat this process to any new PC that is not booting from old image. 

The above method is also suitable for operation on a virtual machine(for detailed 
please refer to "Create CCBoot Image using VMWARE").All Internet Cafe technical staff 
can also do this, by going to some Internet Cafe and collecting the NIC drivers using 
"CCBootPnP" and merge them to create a "Super Image" (single image package) that 
can diskless boot different types of computer specification with different types of NIC. 

 
Installing PNP Driver for New Hardware 
2017/03/16 17:20 

Problem: 

It has no problem to diskless boot clients which have different hardware specifications 

with a single Windows 7 image, but it will pop up the message of "Installing PNP Driver 

for New Hardware" on one of the hardware specifications' clients. This happens when 

you have USB devices plugged into different ports than the client PC from which you 

made the image from. 

Solution: 

Windows 7 has a good compatibility with other devices, so there is no need to do 

Multiple Hardware Profile​. To avoid the message of "Installing PNP Driver for New 

Hardware" popping up again next time, you can follow the following instructions. 

1) Diskless boot one of the client PCs (which has "Installing PNP Driver for New 

Hardware" problem) with super client. 

2) Install the relevant device drivers. 

3) When finished, shutdown the client PC, and disable super client on the server. 

Note: If you have more than one PC that show the drive installation then you have to 

repeat the above steps for each of the clients. 

Note: In some cases, the hardware drivers may conflict with each other. 

That is, after enabling super client to update the drivers of one of the hardware 

specifications, the drivers of other hardware specifications will have problem or show 

not installed. 

Mostly, this problem happens to graphic card driver, for this we recommend you use 

Hardware Profiles​ for the clients. 

Thanks for Thomas Yuen reporting this problem. 

 
Intel Graphics Card Conflict 
2015/08/27 22:53 

Suppose that the Intel graphics card type on your clients are different (PC01 is Intel A, 
PC02 is Intel B), when you install or update the graphics card driver on PC01, PC02 gets 
blue screen, and these two types of Intel graphics card always conflict.  

This is because Intel A and Intel B are both from Intel, their "*.sys" and service name 
are the same, when you install or update Intel A, it will overwrite the "*.sys" and ".inf" 
files of Intel B. We revised one of the Intel graphics card driver, modified its ".inf " file 
and renamed its "*.sys" file name to prevent Intel A and Intel B conflict. Now, you can 
download the revised Intel VGA driver from 
http://www.ccboot.com/download/intel-vga-2exx-fix.zip​, 
http://www.ccboot.com/download/intel-vga-01xx-fixa.zip​ and 
http://www.ccboot.com/download/intel-vga-015x-fixb.zip 

Note: If your Intel graphics card type is not included in our fixed divers, you can modify 
the ".sys" and ".inf" files yourself according to the following steps.  

We take VEN_8086&DEV_0102 and VEN_8086&DEV_0152 for example. You can 

download them from ​http://www.lacroixrouge-brest.fr/pci_ven_8086&dev_0102.rar​ and 
http://www.lacroixrouge-brest.fr/pci_ven_8086&dev_0152.rar​. 

1) Extract "pci_ven_8086&dev_0102.rar" file, open the extracted folder, and find the 
".inf" file (Figure 1-1). (Note: Normally, we just need to modify the lower version 
graphics card's ".sys" and ".inf" files.) 
  

Figure 1-1 

2) Open the ".inf" file with Notepad, find texts which end with ".sys" (there are three 
".sys" texts, they are, "igdkmd64.sys", "ServiceBinary = %12%\igdkmd64.sys" and 
"igdkmd64.sys") (Figure 1-2). 
  

Figure 1-2 

3) Modify these three ".sys" texts. For example, add "_fix" before ".sys" (Figure 1-3; 
Figure 1-4; Figure 1-5). Then save this ".inf" file. 
  

Figure 1-3 
  

Figure 1-4 
  

Figure 1- 5 

4) Find "igdkmd64.sys" in the extracted folder, and rename it as "igdkmd64_fix.sys" 

(Figure 1-6). 
  

Figure 1-6 

5) Open ".inf" file again, find "AddService" (there are four "AddService"), and add "_fix" 
after "AddService = igfx" (Figure 1-7). Finally, save the ".inf" file. 
  

Figure 1-7 

6) On the "Device Manager", install the new revised graphics card driver. 

Notes: If you have 3 types vga drivers conflict with each other, you can modify the first 
vga drivers as "_fix", and modify the second vga drivers as "_fixa". 

Thanks for Gaétan TALOUARN reporting this problem. 

How to use new multi hardware profile function 
2016/10/17 23:51 

It is really difficult when you have multiple images for your computers at your cafe. 
However, with Windows XP, you could use “Hardware Profile” function to make a single 
image for multiple specification computer. 

So, we are now introducing an updated “Hardware Profile” function to address this on 
CCBoot Build 20160727, this methods supports Windows 7 and above Operating 
systems.  

This method is for situations where installing graphics driver for one client overwrites 
the driver of the other, and it shows installing drivers in first client when booted. 

Creating hardware profiles 

1. Open “CCBoot UI” and click on ‘Tools->Hardware Profile” (Figure 1). 

 
  

Figure 1 

2. Type the name of profile and description in “Profile” and “Desc” (Figure 2). 

Here we take examples of GT 780Ti card and newer GT 980 graphics card. 

 
  

Figure 2 

3. Repeat step 2 and add another profile for second card (Figure 3). 

 
  

Figure 3 

4. Now, you have two profiles for your two cards (Figure 4). 

 
  

Figure 4 

5. Now, open client details and click the “Hardware Profile” drop down, choose the 
profile corresponding to this client (Figure 5).  

 
  

Figure 5 

6. Once, profile is chosen, click “OK” to save the settings (Figure 6). 

 
  

Figure 6 

   
Enabling superclient mode. 

7. Right click the same client and choose “Enable Superclient” (Figure 7). 

Figure 7 

8. Tick the image check box and click “OK” (Figure 8). 

 
  

Figure 8 

9. Now, your client is in superclient mode, represented by the red color of the client 
icon (Figure 9). 

 
  

Figure 9 

10. Boot your client and install the graphics and other drivers specific to this client pc 
specification. 

11. Once done, turn off the client pc. 

   
Disabling superclient and saving image 

12. On the server, right click the client pc and choose “Disable Super Client” (Figure 10). 

Figure 10 

13. It will ask you if you want to update the image, choose “Yes” (Figure 11). 

Figure 11 
14. Now, it will ask you if you want to create a recovery point for the image, choose 
“Yes” (Figure 12). 

Figure 12 

15. On the “CCBoot Recovery Properties” dialog box, enter the description for the 
recovery point and click “OK” (Figure 13). 

Figure 13 

16. It will start the image update process (Figure 14). 

  

Figure 14 

17. Once the image update is completed, click “OK” on the pop up prompt to close it.  

18. On another client with different hardware specification, double click and open 
“Client Details” and click “Hardware Profile” drop down like in step 5 (Figure 15). 

 
  

Figure 15 

19. Once, hardware profile is selected, click “OK” to save the client settings (Figure 16). 

 
  

Figure 16 

20. Repeat step 7 through 17 for this client. In short, make the client a Super Client, 
install drivers, turn it off, disable the Super Client mode and then save the image. 
21. Once you have done this, now boot both client PC. You will now see that both PCs 
boot without any installing driver notification (Windows 7) or getting devices ready 
(Windows 8 and above). 

Note : Please keep in mind that since hardware profile stores drivers in separate folder 
for each profile the boot time for different specs clients will be different and not always 
the same. 

Some may take longer than normal image to boot. 

Note : If after using hardware profile you are experiencing Blue screen issue and driver 
installing again and again, then we recommend in using separate images for the 
clients. Also, if you are using Windows 7, then please consider upgrading to Windows 
10 as it has better hardware support for new boards and computer specs then on 
Windows 7. 

   
 

Solve "Getting Devices Ready" on Windows 10 

2016/09/10 16:09 

In the clients which have different hardware specifications, it will pop up the 
message of "Installing PNP Driver for New Hardware" or show "Getting Devices 
Ready" screen during boot.  

Normally, when your client pc shows "Installing drivers" (windows 7) or "Getting 

Devices Ready" (window 10), It does not affect diskless boot of the client.  

Windows 7 and above have good compatibility with different hardware. To stop 
getting "Installing PNP Driver for New Hardware" or "Getting Devices Ready" in 
clients, you can follow the following instructions. 

1) Superclient the PC that is showing the driver installation pop up or screen. 

2) Boot the superclient PC and install relevant drivers for the client hardware. 

3) Once done, shutdown the client PC. 

4) Disable superclient and save the image. 

5) Now, boot other clients as well and check if any client show the same "Installing 
drivers" again. 

6) If any client show "Installing Driver" or "Getting Devices Ready", then repeat step 
1 - 5. 

7) Once you have finished doing step 1-6, but you still get the "Getting Devices 
Ready" or "Installing Drivers" then you need to use H
​ ardware Profiles​ to resolve 
this. 

 
   
Note:  

Hardware profile work differently compared to simple superclient and install driver.  

There are cases, the hardware drivers may be conflicting with each other, for 
example, the driver filename is same.  

That is, after enabling super client to update the drivers of one of the clients, the 
drivers of other clients will have conflicts. Mostly, this problem happens to graphic 
card driver, when this happens, we recommend you try and use ​Hardware Profiles​. 

Note:

If you are experiencing increased reads and writes after using hardware profile then
please make sure you ​enable client cache​. Once enabled, you will see less write back
to the server.