Last active [hidden]
The free space error was fixed in a later version. Upgrade to 1.3.3.
For the cluster, are you using a service account on the secondary? I ask because it looks like you are using the clonedeploy user which is an admin account.
Looks like a bug, the setting isn't being saved. You can manually set this in the image profile->pxe boot options->kernel arguments
Yes, if it's on demand, they are under admin settings->logs->on demand
if it's registered it's under computers->search->view->logs
Looks like you are trying to import an iso. That's not how CloneDeploy works. CloneDeploy only uploads images from other computers.
Was this a clean Windows 7 install?
This is not currently a feature, I can try to add it in the next release.
I understand what you are doing, the way you are doing it is the only option. Using the id that is assigned is the only way right now, like I said, I'll add this feature to the next update.
If your interested in the explanation. The BCD is stored in the first partition, it marks where the windows files are in the second partition. It does this by recording the starting sector of the second partition inside the BCD. Your first partition is unusally large. Typically it is less than 500Mb. CloneDeploy marks any partition less than 5GB as a fixed partition, meaning it will not resize it on the destination. Since your first partition was > than 5GB, it was flagged as resizable, when you deployed to a different sized hard drive, it changed the size of the first partition, meaning the start of the second partition also changed, and now the BCD is pointing to the wrong location. Manually marking this as fixed size partition, ensures that the second partition starts at the same place. CloneDeploy does have the ability to fix the BCD, in the image profile deploy options, checking update BCD should be another way to fix the issue.
Check modify the image schema