Last active last week
Disable shrink did not helped. But My colleague build the PC source using CentOS self-partitionning then modify it. And the issue was there.
I rebuild the Centos by myself, did the partitioning by myself too.... And everything is OK!
I don't know if the problem comes from the way the partitioning is done by the installation CD or because my colleague let the installation process do it and then modify it, but CloneDeploy is not part of the problem. Good news!!
Sorry. Here are 2 fresh logs.
One from source computer, other from Destination. Same image.
Here are the two logs. The deploy seems to have error related to EBR but honestly I don't know why and what to do.
Many thanks by advance for your help.
Hi, We had a very similar problem with Centos7.
We tried to upload it several times (even changing FS in ext4) but nothing worked.
The best result we had :
Seems to start but finished with an error message abut Dracut.
The worst result : Image refuse to deploy.
I'll try to upload my logs this week.
I think I checked nearly all logs but I did not found a log for the group multicast session but only for each client.
I'm wondering if a log telling if the session went till the end, if a client left etc. exists.
Basically I install remotely 300 PCs each week, and checking each pc one by one would be hard to do.
Thanks by advance if anyone has information about that.
Hi Yes it is
You have create your image and image profile on server before upload it,
Please check this post :
I'm using CloneDeploy on Ubuntu 16.0.3 without any problem.
What kind of error do you have? (messages, screenshots)
thanks for the explanation. When we create our template this partition is effectively less than 1Go.
But when we then deploy them with ghost, our default is to resize partition automatically, that's why when we switch from ghost to clonedeploy we have these kind of things.
Hi, I can answers the first question :
-Admin Settings > Security > On Demand : Enabled -Admin Settings > Security > On Demand Require Login : No -Admin Settings > Security >Add Computer Requires Login: No if you don't want to login when register a new PC -Admin Settings > Security > Universal Token : Generate -Admin Settings > Security > Update Security Settings -Admin Settings > Boot Menu > Create Boot File -Admin Settings > Boot Menu > Editor : Check your boot menu have USER_TOKEN="your generated token", else put it manually and save changes