@bongasicdn7 @Developers Please look at this patch and see if it can be integrated into 1.5.0 code base. We have had others request the ability to multicast on multihomed hosts.

Problem solved. It was only the lack of the Client FOG installation on the machine. As soon as I installed it, the machines came up with their names. Many thanks for the help, friends.

In as simple terms as possible, no. We’ve found that the Goldilocks for compression is probably 5 or 6. This gives a semi balanced data across network and writing data to the hdd. The network throughout should be faster at max compression, but writing to disk takes a bit longer as it needs to decompress. Little/no compression is hell on network, but fast to write to disk as no/minimal decompression must happen.

Oh, good point. We do tests on it. As testing i did reset, not cold start. Will check and report.

@Tfoote01 Great to hear you got this solved yourself. Thanks for sharing!

@JackieJack all the computers would download the 8GB and run it locally

i really would like to hear wayne speaking 🙂

@Tom-Elliott Okie-tay! Closing ticket, marking solved. Thanks Tom!

@flipwalker consistently isn’t generally an issue when you’re using fog. once you know it works with your specific model of computer (which is most of them), it just works.

@edition What’s the end goal you want to accomplish with fog in this scenario? If it’s just hostnames - and you’re already kicking around the idea of a user identifying themselves as mandatory - make setting the hostname mandatory too and be done with it.

@hchchchc The FOG appliance is not supported by The FOG Project. That vm was created by a forum member.

With that said, the Distribution OS on the FOG Appliance should release a kernel update to address. I can say for at least centos and Linux Mint, there were kernel updates over the weekend.

@Cap_Jak It’s back online, thanks for letting us know.

So it looks like the API works great for what I need. But how do I mark as solved? I can’t find anything that lets me change this status 😞

My code from the api is something similar to:

$fogApiToken = 'mf...A=' $fogUserToken = '5Mz...NDY=' $fogServer = "IP ADDRESS GOES HERE" $headers = @{}; $headers.Add('fog-api-token', $fogApiToken); $headers.Add('fog-user-token', $fogUserToken); $BaseUri = "http://$fogServer/fog" $HostURL = $baseUri +"/host/" $HostResult = Invoke-RestMethod -Uri $HostURL -Method GET -Headers $headers -ContentType "application/json" $ThisHost = $HostResult.hosts | ? name -eq $ENV:COMPUTERNAME $PrimaryUser = $ThisHost.Inventory.PrimaryUser.Trim()

@imagingmaster21 said in Renaming Images:

Also any best practices with this?

Best practices is to name it right the first time 😉
You can change the name in the GUI no problem, but don’t mess with the path unless you actually change the path on the disk too.

@george1421 said in 6- to 12-port switch recommendations?:

you might want to consider a multicast stream

George is right. I had this in the back of my mind, but just wanted to address the switch question. Multicast should be used here no matter what switch you buy.

@wattfun said in N00b_Here: Plz help! New Setup for a company imaging solution:

I have downloaded Centos 7 (not sure how to partition correctly) and Ubuntu 16.04

The default partitioning of Cent OS and Ubuntu are not ideal for FOG. Both crash when the root partition fills. There’s video in our CentOS 7 tutorial showing you how to partition it: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
For ubuntu, we have a video on Debian that applies to Ubuntu too. This video goes into great detail about Linux partitioning, and was created for newbies like yourself: https://wiki.fogproject.org/wiki/index.php?title=Debian_8 You can learn a ton about Linux partitioning by watching that.

@wayne-workman lol it shutdown 😄

To shutdown a computer remotely (immediately) in FOG management web gui:

Go to hosts, list all hosts, click on host, choose Power Management from list on left hand side, and choose shutdown immediately (add option).

Seems now all goes as wanted. THX a lot for help (can i mark my topic as solved somehow? in old forum i knew the way for it i guess, but not now)

First let me say I have no clue about crypto currency. But after reading this thread and having a general understanding of the setup here is what I would do.

Use buildroot to create a custom linux kernel, much like FOG’s FOS operating system. If one was ingenious, they could reverse engineer FOS and then possibly load the program needed for the crypto mining into the init.zx and also reconfigure the master fog script in FOS to call the crypto mining program. FOS boots and runs out of memory, no hard drive is needed.

Now the cleaner way would be to use buildroot to create your own custom linux OS with all of the required applications. Once you have your bzImage and init.zx you can launch with FOG by creating a custom iPXE menu.

You could use some of the concepts here:
https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

and here:
https://forums.fogproject.org/topic/11194/poc-using-fog-as-a-netboot-server

with the custom linux OS.

Or you could either create or use an existing live OS and pxe boot it using FOG.

There are a number of ways to get a live boot linux OS running on a diskless workstation.