@ITCC Please update to RC’s if you can?

I don’t know what’s causing it to create “false” entries in the database, though I cannot get it to replicate the problem in the current code I’m working with.

@plegrand I just stumbled upon the FOG_ENFORCE_HOST_CHANGES setting in the FOG web UI and remembered your post:

This setting only operates with the new client. Default value is 1 which allows the new client to enforce name changing on every cycle it checks in, so any change on FOG will take place on the next cycle. If unset (value 0) it will only perform hostname change and/or AD Joining on host restart.

You might want to give this a try to get rid of the messages.

@Sebastian-Roth
@Tom-Elliott

I just updated to RC4… I’ll keep you all posted! Thanks!

@Sebastian-Roth fixed.

@Sebastian-Roth I would say yes, The network wasn’t down at all. I was able to ping and checked the Linux firewall to be sure it was disabled.

It started doing it again this morning. But everything works. So I will chalk it up to have a system that has been updated more times than I would like to think about unless you guys want to look into it further.

@george1421 The Teammate software installed correctly on a virgin build of 1703 without an application (minus the ones that come with 1703 ) I’m not sure what else I can say to help your setup, it works for me.

0_1501006641808_1703_Install.png

@coh_is That is great to hear you have it working.

For the record this wasn’t a FOG issue, but an environmental/infrastructure one.

Upgrading the kernel seems to have fixed the problem!

@george1421 Yes, upgrade successful. Please feel free to mark it as solved.

Tom has a good point here. I’ve struggled with launching powershell from the FOG Service with the correct privilege level to prevent UAC pop ups you never see. Disabling UAC on a PC and retrying the snapin will can be a good testing step. Windows 7 and Windows 10 treat UAC differently, or so it seems. To get around UAC in Win7. Seach for elevate.cmd and elevate.vbs that came out with Server 2008/Vista. I’ve found that this can successfully elevate a PS script in Win7. I’m still working on Win10.

if you’re actually getting powershell to start your script, you can also pipe the output to a file using the out-file cmdlet:

powershell.exe -Executionpolicy Bypass -noprofile -file myscript.ps1 | out-file full [full path to some text file]

Jim

You can get the inits here, without upgrading to 1.5.0RC series. Here is the wget command to use from the FOG server’s linux console.

wget https://fogproject.org/inits/init.xz wget https://fogproject.org/inits/init_32.xz

These files go in /var/www/html/fog/service/ipxe. Make sure you backup the current files before you update them with these.

With these new inits there is no need to use the postinit patch method I described below.

I don’t know what’s causing the “trailing” tasks yet, though I hope to find it soon. It seems to be a very specific set of circumstances that causes it, though I don’t know what that set of circumstances actually is.

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