Last active 6 weeks ago
Is it possible from the boot menu to go to a other deployment platform? Such as Windows Deployment Server or Cobbler?
Hello, thanks for the reply. Yes it is indeed a EFI. I use now CloneDeploy Proxy DHCP en it is working fine because this is working with EFI. Is there also a possibility that we not use EFI? and use our own Proxy?
I tried a little futher and i think the M.2 disk is not a problem. The problem seems to be with the MBR or GPT setting. I made a new UPLOAD from a macine with MBR partition and a working Windows 10. Now i tried to put that image on the same system with the same 4tb disk. It seems that CloneDeploy can not repair a header or something because that is the message i get. I send the new LOG files so maybe you can see what is wrong.
I think CloneDeploy has a problem with the used 256 M.2 SSD disk. If i make an image off a HP Z440 workstation with one SATA disk there is no problem distributing it on the same system but here the bios has a previous version. Maybe i need to change some bios settings, i dont know.
Correct the logs are different but from the same computer
On the computer we make legacy enable. The computer we make the image and take a same computer to deploy it.
Here the LOGS. I have version 1.3.5
I have to manage to do a recovery on Windows 10 and see that the M.2 disk is UNKNOW. So CloneDeploy put the Image on the second HD i think. So the problem looks issue with M.2 HD. Please help!
Could ther be a problem with the new Windows 10 release? On the release 1709 we never had this problem, now we have Windows 10 release 1803