Suggestion please
-
@george1421 Hi guys,
I cannot test the wired using the 192.168.x.x because it is controlled by the IT department and the DHCP and DNS is working under another subnet.
I have to configure FOG as the DHCP server and so start again from scratch. -
Hi @george1421,
it looks like FOG has issues with the ‘Microsoft Reserved’ windows partition.
I can image the EFI partition, I am trying now to capture just the main one, but it is very slow apparently 1h 20m left (12GB - 115MB/min) using partimage instead of partclone (I have selected it in the image configuration, but the tool actually is partclone).If this duration is due to the wifi transfer/speed, I will go back to the wired scenario.
[wired] In order to capture one and massively deploy to multiple devices (without managing the devices in FOG), what’s the best workflow in your opinion?I’ll keep you posted.
Lucio -
@ziolucione I was thinking that since you can’t image with the ethernet adapter using the same setup I should rebuild the inits with the older partclone tool. Again to only change one thing at a time.
As for your speed of 115MB/min that translates over to 15Mb/s. If I had to guess you are using 802.11b (11Mb/s) or 802.11g (54Mb/s) wireless network link. If I had to pick one or the other I would say 802.11b. So your numbers are reasonable for wifi. Its not fog, the device, or partclone/partimage at fault here its your network link speed that is the bottleneck.
In order to capture one and massively deploy to multiple devices (without managing the devices in FOG), what’s the best workflow in your opinion?
Assuming you still want to go with the usb boot method, once we have a captured image I’ve prepared a template on the usb flash drive. Its number 5 in the grub menu. Right now it has data I borrowed from @Junkhacker 's post on how to call an image directly from the iPXE menu. I translated it to grub format. So my idea is once you have captured the reference image, we will go and update that #5 menu to call for that image directly without needing the target computer to be registered in FOG. But that part will only work after we have captured your reference image.
-
Hi @george1421 I have the reference image now.
Can you help me to create this entry in the FOS system so I can push the image directly from there (without going into FOG I believe), and also, I should have 3 different images to deploy. How can I create another menu entry in FOS?
Thank you for your help.
Regards.
L. -
@ziolucione Ok this part has a few steps but is not hard. What you need to do as a test is to take a registered computer and setup a debug deploy of the image you are interested in quick deploying. (it would probably be faster to use a wired connection for this, but what ever works). When you are dropped to the FOS Linux command prompt key in the following
cat /proc/cmdline
That will print out the kernel parameters used to call that image.Now when I created the grub menu for that wireless usb boot I created a menu entry 5, that is the template you need to populate with the values collected from the
cat cmdline
command. You will need image name, image type from your debug deploy image into that option 5 in the grub menu. You can make more grub menu entries by just copy and pasting the section 5 menu entry. The order the menu items are in the grub menu is the order they will be displayed when the system usb boots.I can give you a hint if you want to edit the grub menu on a windows computer, use notepad++ and not windows notepad. Windows notepad adds in windows specific characters that sometimes confuses linux applications.
-
I thought of a bit of an easier way to explain the field mapping between the kernel parameters (
cat /proc/cmdline
) and the grub menu. Here is a graphic that explains how to map the values between the two different booting methods.