Last active [hidden]
I can give you access to the wiki if you would like. Or if you just want to post some type of guide here, I'll add to the wiki. Also you mentioned issues with the queue being full, you can adjust the number in the distribution points.
It is in the database, you could use the api to delete the computers or the easiest way would probably be just to modify the core scripts to prompt for a computer name even when registration is disabled.
Switching to / from clobber mode only changes the boot menu, nothing else. You be able to just recreate the default boot menu when clobber is turned off by clicking create boot files in the admin settings boot menu. Are you using proxy dhcp?
To your point about the documentation. Yes, much more documentation is needed. Since I am sole developer it is difficult to find time. Usually adding features / fixing bugs, wins out over adding documentation, although it something I definitely want to get finished.
Shrinking the volumes is what makes it possible to smaller drives. If you have enabled don't shrink volumes then that is your problem. You mentioned you cannot expand shrunk volumes, do you have a log from this?
When setting the computer name from on demand, it automatically registers the computer under that name. From then on it always uses that name, you need to either change it in the gui or delete it. There is an option to disable registration, but the problem is that you won't be prompted for a computer name. I'll need to add another option in a future release to disable registration but still prompt for a computer name.
I'm not sure that I'm following you. The log doesn't change the behavior of anything. It's just historical data.
That is grub which is the correct menu. Not much that can be done, for some reason it's just not compatible with secure boot on this machine. Only 2 options.
1.) disable secure boot, image, enable secure boot
2.) use the the winpe imaging environment
When you boot the client usb, what does the boot menu look like. Can you attach a pic? There are two different menus, one for efi and one for legacy. Just want to make sure the correct one is loading.
Are you getting the grub menu or the syslinux menu?
The issue is that you have two efi boot entries pointing to the same partition. One for Windows and one for Ubuntu. CloneDeploy expects only 1 efi boot entry per partition. This is something that could be added in a later release but currently it won't work. It is possible that we could manually modify the image schema and remove the windows efi entry. If you are uploading dual boot images often, it wouldn't be ideal