problème d'enregistrement d'un pc latitude sur fog
-
@george1421 Now that you mention it, we tried with two pc’s and the mac address on fog was the same. It probably gets the mac address from the usb adapter. Do you have a solution for this?
We use dell latitude 5320.
Thanks
-
@abde See if the dells have an option for Network adapter mac address pass through. For the 5420s we always image them using a WD15 or WD19 dock, but the mac addresses are always unique to the computer not the dock. I don’t know what magic Dell done, but that process has always worked so I never had to deal with this problem.
-
@george1421 I changed the mac address of the registration to that of the PC. For the moment the capture is done. But we do all the tests and we come back to you
Thanks a lot
-
@george1421
hello,I have a problem when i boot with my laptop in pxe.
I send you a picture with the error message
Do you have an idea of the problem
-
@abde Yes I do know this problem.
-
@abde Search the web or the forums for “unclean filesystem” or “dirty bit” and I am sure you will figure things out.
-
@george1421 Hello George.
Hello George,we had different problem (see attachment)
the first image was fixed by putting the fastboot (2nd image) in minimal for the capture and for the deployment.
3rd image during the deployment we have an error message but the deployment still works.
4th image at the time of starting the pc after deployment, one has systematically this error message.
Can you help us.
thank you
1er https://ibb.co/64HzCjs
2e https://ibb.co/5cwDhnW
3e https://ibb.co/sHvxt0z
4e https://ibb.co/rQPSQDp -
@george1421 In addition, the C-type adapter is not recognized for the pxe. Only in usb.
-
@abde said in problème d'enregistrement d'un pc latitude sur fog:
In addition, the C-type adapter is not recognized for the pxe. Only in usb.
We are starting to switch into areas that are not within scope of your subject line. The moderators like to keep it to one problem per thread so when/if someone is looking for the exact problem you have in the future they don’t get confused because there are 5 different and unrelated issues in the same thread. “New problem == new thread”
UEFI firmware is much like an OS in that it will only support known hardware. To support usb-c pxe booting you need to use a network adapter that is supported by the hardware manufacturer. This is a function of uefi and the hardware. You could boot from a usb flash drive into iPXE, if iPXE and FOS Linux supports that usb-c network adapter then you can image with FOG.
The unclean disk image is because you did not power off windows correctly for imaging. This is a “feature” of windows and not a bug in FOG. If you want to know more about this issue then google “Windows dirty bit”
You have 3 options here.
- Use sysprep to power off the computer.
- use the following command to power off the computer.
shutdown -s -t 0 - Turn off windows fast boot.
The windows restarted expectidly is one of a number of things.
- The most common is that you have the FOG Client installed and you did not disable the service before image capture. You would then turn the fog client back on in the setupcomplete.cmd batch file or via the unattend.xml file. ref:
https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep - You have a windows driver that expectantly rebooted during WinSetup/OOBE
-
@george1421 je comprend , je ferai un autre post pour les prochaines question.
Nous avons réussi a faire l’image et retirer les message d’erreur (c’était un problème de sysprep) et la non présence de l’agent fog sur le poste.Merci beaucoup de votre aide et je penserai à crée des topic pour les différents problème rencontrer afin d’aider la communauté.
-
@abde No problem. I am happy to answer your questions, we just need to follow the guidance of the developers to keep one problem one thread policy.
