@george1421 Sorry George, I was just reading the other thread in regards to refind not working too so I can see how they could be muddled up.
Yes this is the default setting, however refind just doesn’t go past Initializing.
I did some Dynabooks last week (dreadful machines) and refind worked just fine and dandy with those, but that was using unicast. Not sure if that’s related or not but wanted to give the full picture.
I’ve just done another 24 machines using Multicast which worked beautifully with the deployment, done in under 4 mins! These did not rejoin the session after completion, however then I hit another small issue as rEFInd would not proceed any further than initializing.
If I removed the network cable and rebooted, they went into Windows perfectly.
I also tried with SANBOOT but then the FOG client would countdown from 10 and just loop to itself (go back to 10).
Not sure if this is related. These machines were HP 430 G7’s so will be on the same BIOS as the 440’s.
The next bunch of machines I have to do are not using Bit Locker, so I will see how I get on with those.
@george1421 I’ve set the remaining 8 going now, but I omitted the WOL part and started them manually. See if it makes any difference.
I never said before that this was a RAW image as the drive was encrypted with Bit Locker. I noticed an error on the end of the deployment on the hosts and then the reboot.
The tasks still show spinning and the hosts have all gone back to the deployment screen amd sitting there waiting for it to begin.
Logs show that the Multicast has finished, but I believe it’s this error that is stopping it progressing any further.
Just so you have the entire picture.
Hosts are HP440 Probook G7 machines. I go into BIOS to start with and make the following changes:
I have another 8 of these machines to do, so I will try a couple with various settings to see if I can stop the occurrence, or if it does it regardless.
I’ll let you know how I get on.
@george1421 The multicast logs showed that the job was complete, so the machines sit there waiting for it to start - they are on the same screen as when they are waiting for all machines to be ready prior to a job starting.
“Multicast is a great bandwidth saver but it also relies on the networking infrastructure to be setup well. Also if you use multicasting ensure you have igmp snooping enabled for the VLAN where you need to multicast on.”
This is an entirely segregated network using unmanaged switches. The PC we use for controlling FOG has 2 NIC’s to access the corporate network and FOG.
Just got another pallet load of machines to do, so I’ll let you know how I get on with these.
@george1421 Hi George
Yes you explained it correctly, and yes the task appears to be still running when this occurs. I cancel the task and then reboot the machines and find the image has been deployed fine.
I don’t have any machines on the bench at the moment, but when I do I will take some screenshots.
@george1421 Yes it does, it sits with the wheel spinning but no progress. The screen on the host looks like it’s waiting for other hosts to join the session before it can start.
Hello folks
I got multicast working it would seem, it certainly reduces the bandwidth used comparatively to unicast when doing a large chunk of machines.
However, after the image has deployed, the machines are booting up again and going back to the multicast screen and waiting for the image. In tasks, the hosts all show with the task queued icon spinning round but no progress bar.
If I shut a host down and boot to the local disk, the image has deployed fine but it doesn’t seem to update in FOG?
Also, the host information doesn’t update in FOG, showing the date the image was deployed.
I start the task by quick registering the hosts and adding them to a group. Once the hosts are powered off i start the task clicking the multicast icon next to the group and waking them all from LAN. This fires them up perfectly fine and they begin but after the finish, they reboot and go back into multicast mode where they are waiting for the cast to begin; which of course it doesn’t as it’s finished.
Ubuntu 20.04 VM with FOG 1.5.9
@Sebastian-Roth Thank you, I did forget about using Multicast. I’m running a job now using it and it’s immensely improved bandwidth utilisation!
@george1421 Thanks, I’ll put another network card in for the setup. That should sort it.
We are running FOG from a segregated network which doesn’t exclusively have access to the internet. We are doing it this way for now until I get the Cisco kit in to create the VLAN and allow me to split it off that way.
However, going to add a storage node into the mix to allow for increased throughput when deploying, and I hit a problem with the installer. It needs to be online for updates, but then if it can’t contact the database during the install; it seems to fail.
If it does fail and aborts as it cannot contact the database; what are the steps needed to continue the install? I’ve added the storage node to FOG but I don’t think it’s working, I can’t see any folders under /var/www/html for images etc.
Never mind, found the option in settings. Now working fine and just have to change the boot device before letting the client do it’s thing.
Hello all
I’ve got a lot of machines to image, and FOG has made this exceptionally easier by far, so firstly thank you for the amazing bit of software. However I would like to make the process more efficient rather than me deploying the image on each client which is the process I’ve been doing up to press. (Machines had to go out so didn’t have time to investigate further until now).
I’ve enabled the quickreg autopop and tied it in with the correct image, however I still need to be at the machine in order to select from the boot menu.
Is there an option or a way I can set this to automatically Quick Reg upon boot and then deploy the image or join multicast?
Thanks in advance all.
This also worked for me, but with a Dynabook A40 laptop.
Thank you.