I created a new group and it worked.
Can be marked solved.

Thank you

@FaP Clone this repository to somewhere on your server (I always recommend /root/git😞 https://github.com/FOGProject/fog-community-scripts

There’s a tool in there called updateIP. First, you adjust your IP address for your OS as needed, then you would run this script which would update all the IPs in FOG and also update DHCP configuration if you have that enabled on your fog server too.

Do let me know how it goes.

George helped me figure out what I was doing wrong. But what you posted Tom is very valuable.

@Wayne-Workman My point isn’t about people’s “mentalities” just rather the direct facts.

People who are working to create a postdownloadscript that would like logging to be included in some form should be thinking of these things. They’re ultimately in full control of the process, which would also include logging/reporting if that’s what they so need.

While you’re correct that snapins and snapinpacks have the “logging” built in, that’s not to say a postdownload script cannot. The idea of postdownload scripts is to give the person creating it FULL control. What you do with it is completely up to YOU. How you approach logging is up to you. What that script will do is up to, you guessed it, YOU.

Just because it’s not something others may be thinking about does not mean it’s a failure in the “system” itself.

@Tom-Elliott Awesome, thanks!

@x23piracy yes, I had the exact same problem with mysql passwords. How I fixed it? I don’t know exactly. I went round in so many circles, I stopped taking notes. Then it worked.

I kept resetting the mysql password at every step if the way. I didn’t use a blank password. Hope that helps.

I was hoping to get to the stage, where I could script the whole build process, and then make that public.

@Tom-Elliott said in FOS checkin time:

The fact that you had a capture going (writing), and 6 deploy’s going (6 different reads) was a portion of what the load by the server is being caused from.

That wasn’t the case yesterday.

Yesterday, no captures were going. 3 computers were imaging, 12 were waiting in queue to image. The 3 were imaging from a remote server, not even the main server. And the main server’s CPU was maxed out.

@Wayne-Workman I know where you’re headed, and I do understand. But I really think we’re “stuck” because it’s waiting for confirmation or input.

Programs typically don’t get stuck in that sense.

@Wayne-Workman the group idea is currently, the host name that matches that of a group name will apply that matching host settings to any host that gets added.

The last group a host is inserted into (the latest group you added a host to) would define the host to have that new groups settings.

It’s basically your addition. Currently it only does this adding when and if a hostname matches the group name.

@Wayne-Workman

Well said! That’s a great point!!

there’s now yet another folder within all the installer for ipxe binaries. squeaky wheel, grease, something blah glah

I have no idea where to put this in the wiki.

It could be but it would require list of Macs to names and that the names in the filter match what our storage is.

Hi, thank’s a lot for your answers !

@george1421 Wouldn’t Know How To check if it’s in the repo, but I can give it a shot almost home.

@lukebarone Great to hear that you intend to participate in this! You can do it either way. I am pretty sure both ways should give us the same results but I’d recommend using the FOG debug mode as you are using the very same tools as would be used in the initrd later on anyway.

Schedule a task for those clients you want to check. Does not really matter if it’s an upload or deploy task. But just before you create the task check “Run as debug task”. The PC will boot up as normal into the FOG system but then drop you to a shell. The you can just run the command and post results here. Please make sure to double check when typing the results. Thanks!

@kwetiaw The professional version allows for network deployment, they also offer a msi repackager for the professional version. http://support.horizondatasys.com/Knowledgebase/Article/View/97/0/rollback-rx-deployment-guide

@jdd49 said in File Formats - HFS & XFS:

XFS
Does not have the ability to shrink period. It can only grow. The only possible solution is to do a file backup using something like xfsdump, then recreate the filesystem. Or make the smallest partition possible when you first install, then grow after imaging.

Thanks for the info, I guess it’s the best way to go for XFS (for now).

The snapin issue is known about, it’s fixed in RC-9 already.

For now, hosts need images assigned in order to deploy snapins via groups.

And, you can clear host settings via groups already. It’s exactly the same as clearing them on the individual host - but with groups.