Thank You Sebastian. I was on version 1.3.0 for fog service. I updated it to 1.4.0 and everything is back to normal.

@zclift15 Just for clarity one downed node caused all replication to fail?

@george1421 said in Failed ipxe/boot.php because of different IP:

you will probably want to install dnsmasq on the fog server

That’s how the MakeFogMobile scripts work, they use dnsmasq. This is because the intention is mobility.

Joseska,

I suggest a snapin would be a better place to add the computer to a group in LDAP. Assuming the computer is a Windows computer and you want to add that computer to the Samba emulation of Active Directory and assuming Samba emulates AD such that Windows PCs can find the Samba system(s) like they would a real Microsoft Domain Controller, a CMD command would do the trick. I’ve used commands like this below to put domain groups into local computer groups. This command, run as a snapin on a PC in a domain, will add a domain group to a local computer group - giving users in the domain group rights on the PC:

net localgroup administrators DomainName\DomainGroupName

I also believe you can add an AD computer object to a domain group with the same command. It’s abnormal to place a computer object in a domain, but I’ve used this approach to allow services on a specific PC to access network resources without having to place an AD account on a service. The down side of doing this is that all services on that computer have the same access rights, not just the service you intend to have those rights.

I believe this command will add a computer to an AD group:

net group DomainGroupName computername$ /add /domain

I don’t know if your LDAP/SAMBA/AD supports Group Policy Objects, but actions that need to be taken on machines just after they join a domain (so they work correctly for future users) are typically done in Startup Scripts inside a GPO applied to the OU to which the Machines are joined.

Hope this helps.

Jim

@Sebastian-Roth I changed the FOG server over to 255.255.240.0, the old subnet was from before vlans were implemented it just got passed over 😛

Try swapping out the hard drive on a/these target computer with a new one or at least one that is known to be good.

From a practical point that computer is about 7 years old and its conceivable that the hard drive has issues.

@SquidgyHobo where the wiki shows git checkout dev-branch you would do git checkout working.

Master branch is current stable version 1.4.4
Dev-branch is latest trunk, sometimes it’s the same as master but typically containing rc versions.
Working branch is where I’m almost always “working” on the latest stuff whatever that might entail.

@keith75140 You might want to read through this article: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

@george1421 This fixed my problem, thank you!

Thank You! You are the best!

@george1421 I copied what your pasted and changed the permissions. Maybe it was the permissions to fog:root that did it?

@msaglioc99 Reading through the PDF I found this link:
http://support.bluebeam.com/articles/enterprise-installation/

On the right side another PDF is linked called Enterprise Installation Guide. Check this out. On page number 9 (12 in the PDF) you find information on the MSI command line switches.

@UWPVIOLATOR You can make the call with curl or powershell. If you go the curl route, there is an executable for windows called curl.exe that will do need or you can call it from a linux command prompt.

@Wayne-Workman has some very fine examples of curl calls in this thread: https://forums.fogproject.org/topic/9779/can-i-use-some-kind-of-script-to-create-image-and-ghost-my-lab-machines

The problem is solved, My colleague used some system hardening from a procedure file and we didnt know exactly which was it, when we reverted the edits every thing worked, the edit was in registry.
Thanks for your support

I just read another post regarding this same issue. I will follow that posts under the bug forums.

RUnning the install to “working” resolved my issue. Thanks for the help!

@Sebastian-Roth I kind of got pulled in a few different directions.

But the concept is to use grub to make an ipxe call. From grub we would use the menu that would look a bit like this

menuentry 'Quick Image' { set root='hd0,msdos1' linux16 /boot/ipxe.krn initrd16 /boot/qimage-initrd }

Then the qimage-initrd would contain something like

#ipxe param mac0 ${net0/mac} param arch ${arch} param username fog param password password param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :bootme chain -ar http://<fog_server_ip>/fog/service/ipxe/boot.php##params

Understand this is still a concept, but all of the bits look like they fit together nicely. That should provide the quick image menu for unregistered hosts.

@Tom-Elliott said in Install Google Earth:

n you be more specific as to what worked? So anybody else looking at this knows what to do? (Sorry to sound rude, but as a limited community it helps everybody out much more having

@x23piracy method of installing google chrome via snapins and using the settings he posted successfully did a silent install of Google Chrome on a machine I deployed to.

@nitelife Thanks for pictures. Turns out I was on the wrong track. I thought you might still have a special partition layout that is causing this. But looks like you got that fixed already. At least we got that ruled out.

What I am wondering about is why that boot partition (?) is 2 GB?! Have you messed with the boot partition and/or BCD?

Which OS type is configured for that image in the FOG web GUI by the way? Possibly not Win7 which would explain the problem?!

As well, would you please take a picture of the error screen so we see exactly what you see (the error code is definitely wrong).

@MotherFogger Interesting to hear that it’s all working fine when you stay within the ESX VM environment. As well the NFS config (exports) looks good to me.

What’s in between the client and the FOG server? Some kind of router / level 3-7 switch that might interfere here? Yes, please take another packet dump with the new syntax. Maybe the packet dump file will grow a little bigger then but it’s definitely worth it. In case it grows to 5 MB and more you might upload the file somewhere and send me the link via mail.