Last active 2 hours ago
Blast from the past (CrucibleWDS)
Just to show you what I mean.
Thank you, the Latest patch has resolved issue of saving my changes and it sticking as well as the search function.
Getting 10x the upload/download speeds, has patch made any improvements?
I would just like to see the groups machines in in the search list, I used this as a visual aid in CWDS as while we are adding hosts we group them in batches (so anything new wouldn't have a group).
In my search screen which I reach by Groups > Group Name ) Add Members I only see "Name" and "MAC"
I don't set image per host... I set it in the group (that's what I did on CWDS and kept same method).
The # of hosts added was another visual aid so I know I have not missed any devices without going back a few pages and looking at the total from the groups page.
Could you not setup a dual-boot system as you like it and just clone it?
I always resuse same names I just delete from AD first?
My names are based on physical location though.
Final push from myself to move from Crucible to CD and have a few niggles to iron out.
- Search function does not work but I am running Version 1.3.0 and it appears you have addressed this in a patch I read in another thread.
Another is that when adding host, most occasions I check how many are added and they are not there (Maybe its a browser bug as I am using Chrome)
2 features missing which would I found useful (which CWDS had) is that when I have ticked my hosts and click "add selected computers" there was a popup at the top which confirmed "19 hosts added to group" - I would like this to return.
Also when searching for hosts I only get to see in the table - "NAME" - "MAC" and most of the remaining screen space is just blank.
Is it possible/or could it be made possible so that these fields have useful info in when adding hosts (like CWDS it used to show what group the device is already in) so I can easily ID devices that are not in any groups.
If unclear, let me know and I will provide screenshots.
EFI Variables are not supported on this system.
This protective MBR 0xEE partition is oversized - Auto-Repairing.
Should I be worried by this?
Kernel 4.13.2 is set.
I have plugged in a really old keyboard and this seems be work with the newer device.
When trying to take image of a newer model PC which is native Win10 I am having various issues.
I have tried different Kernels and PXE modes but it fluctuates on what issue is.
Either it fails to PXE and I have to change to a x64 kernel (which I have) but when using a kernel that allows PXE I get to the boot menu and the keyboard does not work.
Most of the kit here is Native Windows7 so would prefer to retain computability with both.
It would of likely had a sysprep file built into the image from testing CrucibleWDS about 3/3 and half years ago and I just removed the CrucibleWDS entry.
Thanks for confirming.
Still testing stages but will be making the jump to CD very soon.
CrucibleWDS been heavily used for over 3 years and has been brill, this so far appears faster and although I few tweaks regarding Kernel settings and the above. Works well.
Issue resolved by deleting the whole unattend.xml file.
Is this because in CrucibleWDS (although I never used sysprep) the entry had to be defined within called CrucibleWDS but in CloneDeploy it just needs the file to exist or... has a more generalised linking between the 2 than Crucible had?