http://bobhenderson.org/pdq-deploy-fog-imaging-happiness-take-2/

Create that in inventory, and after the machines join the domain from the Fog Client, it’ll find em in the collection and deploy! It’s that easy!

@redbob said in Task taking too long time to begin after FOG Menu:

r8169

120 seconds sounds like a timeout (wait) for the initialization of the card.

Would anyone happen to have any info on the open source software “Jane” that Wayne Workman mentioned? Any help would greatly be appreciated.

FYI, while deploying / capturing you are forced to disable secure boot because the kernels are not signed, after deployment / capturing you can enable secure boot if you like (uefi only).

Regards X23

@stucraster You can ignore it or make changes to it. I don’t know if sysprep will disable the admin account or not. But the unattend.xml and setupcomplete.cmd files are the way to tweak the final OS to have the features you need. These files would be dropped into place just before you run sysprep. Actually when I build my reference image, I have a batch script that copies the files into the right location and then calls sysprep to ensure everything is in the right spot each time I rebuild the reference image.

@wayne-workman

Everything now works perfectly. As always you are the best.

@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()