Posts made by LPS

Hi all,

I just ppgraded from 1.5.9 to 1.5.10.1622 and now i cant multicast I get invalid login after i enter the session name, it never even asks for a login. Thoughts?

@george1421 Ok so next question, is there any place in the config to auto join a session i can add and change for larger deployments so i dont need to type the session name, I already eliminated the password prompt for now through the gui.

@george1421 ok so i took that rendezvous address back out and then ran it and now it works! I also updated the kernel on the server to the newest one so not sure if that had anything to do with it. Thanks!

@george1421 what i have in the rendezvous address is the server ip address which in this case is 10.200.100.185. Now if i specify 1 computer in the task setup to run as a test it should go correct? Also its not even registering my client if i view the task, even though the client is connected and at the blue partclone screen waiting for the image to be served. I cant figure out what is wrong here.

@george1421 So i have a /20 network, server is 100.185 computer was 104.xx because my subnet runs from 96.xx.xx to 111.xx.xx. Are you saying that the computer and server need to be in the same block of 255 ips?

@george1421 Ok so everything is on the local network now and im still getting the hangup on the partclone screen once its booted in. Thoughts?

@george1421 Ok I will install a local copy of fog on my current subnet, but like i said before, i had it configured that way originally and it still did the same thing. I will report back once i have it completed and try it out.

@george1421 The server resides over a vpn but the storage node is on the same network and subnet. Ive had it thought where the server was on the same subnet with the same results.

Hi all,

I am having trouble multicasting an image, I have looked through the forums and tried some previous advice like setting the rendezvous address and turning off IGMP snooping on my network, neither have worked. I can boot into the multicast, but it gets stop on the blue partclone screen and never serves the image. Thoughts?

Ok so as I posted there is a work around and I suspected something in iPXE but I wanted to be sure I wasn’t being a bonehead here. Thanks!

Hi all,

We just received our new ProBook 450 laptops. The situation is this, I am able to register a laptop and tell it which image to use and that deploys without issue. Whenever I try to just boot an unregistered client and go to the deploy image menu it goes to the login screen, flashes and then bounces me out to a sub menu where I can test compatibility, reboot, etc. Any thoughts? This is only happening on this model computer and like I said I can deploy if I register every client and schedule the task. Other computer models like last years ProBook 450 continue to allow me to select an image to deploy. Is there a log file somewhere I can look at and maybe its throwing an error? Im running it on Debian.

@george1421 Ah ok so if im imaging without registering then location doesnt really do what i need in this case. Thanks though.

@george1421 Ok ive got location plugin installed, does this allow me to configure subnets and which storage they should be pulling from? I watched the tutorial and cant figure out how it determines which to pull from.

@george1421 Where do I get the location plugin from, I cant find out where to install it from anywhere.

I have the following setup:

Site 1:

Fog server with storage node

Site 2:

Storage node only

What I want to do is be able to image using the local storage node for each site and i cant figure out where this info goes and what the process is. Then based on which location, run a powershell script after the fact once the machine boots back up. Is this possible?

I would like to update this thread, we found that the problem was with the DHCP Lease for some reason. We cleared the lease and now it is booting normally. It was very odd that this was an issue because we pulled another of the same machine from the box and it worked without any problems.

@sebastian-roth Ok so i compiled a new version of ipxe.efi and now I can boot the machines however I am still getting the loading bzimage…[connecting] and then it fails. Any thoughts on this?

@george1421 OK So I was able to fully boot and execute actions without issue using a different older model HP. This was using the ipxe.efi file. The newest out of the box HP is the one that throws this error using ipxe.efi. “No configuration methods succeeded”. Then it lets you drop to an ipxe shell.

Hi all,

I have been successfully using Fog for a few years now with legacy boot options. Our new devices do not allow legacy anymore so I have to use EFI boot. I have followed the wiki and tried two different DHCP server types, windows and PFsense and both give the same problem unless I use snponly.efi boot file. If I use snponly boot file I get to the fog menu almost instantly but it freezes up on any task, I cant register because I get a connect error or it gets to a certain percent and then just sits there. Any thoughts on this. Ive been at it for days and have searched these forums and the broader internet and cant find a fix. I just installed a new fog server today so I am on the current version 1.5.9. The device im currently working with is an HP ProBook 250 G8.