@Gabor said in Distributed computing:

just installed FOG for imaging computers

Ok I was under the impression that you installed FOG for netbooting. So then if you have FOG installed for imaging then you can continue to use it for both imaging and netbooting since everything you need is included with FOG for imaging as well as netbooting.

If you want to run off the shelf OS by netbooting I have a tutorial on that and how to integrate with FOG here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

The buildroot approach is a bit more complicated but you an end up with a really fast and tight system. To build a custom linux OS using buildroot you will need to use a linux computer and to download the buildroot dev environment from here: https://buildroot.org/ I suggest that you watch a few youtube videos on buildroot to see if its right for you.

If you want to start by building FOS Linux init.xz image you can start with the data on the github site: https://github.com/FOGProject/fos/tree/master/Buildroot The github repo won’t mean anything to you unless you understand a little bit about buildroot. But with the board/FOG/FOS file path, those files will be copied to the target disk image without changes. The files in that path are placed in the init.xz initfs. Really the files in this path make the image FOS. The packages directory is for custom applications you want complied and installed in the target init.xz file. Again watch a few youtube videos to understand what buildroot is and what it does to decide if you want to go down this path.

@Sebastian-Roth Here’s the output…I will try re-imaging with non-resizable

2431b554-1bb4-45a3-99ca-733ce5639589-image.png

@Sebastian-Roth this is my lab. I have this server as a Samba DC as well

I think they just return the exitcode of whatever it is you’re trying to snapin.

Xen defaults to BIOS though in 8+ you can switch to EFI and I’m pretty sure new versions of ESXi default to EFI. Can you confirm which you have on each?

@robertkwild said in creating an image container for windows server 2012 r2:

so for normal cloning i can use “single disk resizable”?

Please read this: https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Images

If you don’t need to deploy to a smaller size disk you might consider using this image type as it’s less likely to cause an issue and image size on the server is still as small as with resizable image type.

@lacazet2k said in Laptops for home , advice ??:

will they still be able to pull an image while out of the local network

The short answer is NO. They must be connected to a network where pxe booting is enabled as well as be in full communication with the FOG server. FOG doesn’t support one-off imaging off site.

The short answer is Yes, to deploy a Wimboot image.

https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images/13

The scripting you asked about is beyond the scope of FOG, because FOG doesn’t care about the target image.

I personally wouldn’t go about deploying an image the way you have defined it with a script, but it is surely possible to do it that way.

In the end to your question, can FOG deploy a WinPE environment, Yes.

For your switches, make sure that igmp snooping is enabled. Also remember that the slowest device in your multicast group sets the pace of the multicast stream. If you are imaging 9 i7s with nvme drives and 1 pentium 4 with a sata hdd the multicast group will operate at the speed the pentium 4 system can digest the data. Or if you have 9 machines on a 1GbE network and one machine on a 100Mb/s link, the speed of the multicast stream will be restricted to the 100Mb/s link.

60mb/s is not a value that FOG would offer. If that is measured bandwidth speed, ok. But FOG’s partclone measures in Dataflow over a minute. So what speed does partclone say during the multicast stream.

I might try a portion of what you proposed for a test, but instead of disconnecting that imaging switch from the rest of the network, leave it connected. The switch should keep all multicast traffic on that switch as long as there are no subscribers anywhere else the network.

A on a healthy 1GbE network you should get about 6.1GB/m transfer rates. For a multicast on that same network you should get between 4.0-5.5GB/min. On my network I routinely get 13GB/min+ unicast image to modern hardware from a virtual machine FOG server. Just to set some expectations.

@AlexPDX Those topics might help you:
https://forums.fogproject.org/post/125438
https://forums.fogproject.org/topic/13486/fog-1-5-6-pushbullet-plugin-not-functioning (not a bug but a network issue)

@Reuban1219 said in Running Fog Server To Image Different Devices Without Internet (Using Switch):

I downloaded the MSI installer in my windows XP …

I am not exactly sure the fog-client was used on XP much. That was before I joined into working on the fog-client. Though I would think it should work.

But, it keeps giving error of installation ending prematurely.

Can you be more specific on what step it ends and what the error message is? If you don’t get an error back you should use logging as suggested by George. Open a cmd as Admin and run:

msiexec /i FOGService.msi /quiet USETRAY="1" HTTPS="0" WEBADDRESS="x.x.x.x" WEBROOT="/fog" ROOTLOG="1" /L*V c:\windows\temp\foginstalllog.txt

Put in the FOG server IP or hostname instead of x.x.x.x. Upload that log file to a file share and post a link here.

Thank you. I understand the complexity issue and removing the DB manually is easy enough.

@george1421 thank you, i try to do this.
Really thank you!!!

Thankyou Fernando!

@Sebastian-Roth

Yes, sir! My apologies for not doing this sooner.

https://forums.fogproject.org/topic/14116/development-fog-not-capturing-image-partclone-update

@Sebastian-Roth @pete Tested a host with debug tasking. With the -A ""
argument it works fine, without it Cannot view from browser

When confirming your task you are presented three options for scheduling: Instant, Delayed, and Schedule Cron-style. It sounds like you want the last option.

@george1421

FOG onto Ubuntu running as a VM.

posting an update that it worked in the end. (somehow the VM i created as test used another SCSI adaptor and it didn’t play well)

The settings that are default for a Win10 x64 still needed secure boot to be turned off.

For those who might venture, here’s my settings for my clients.
c6256d12-e5ba-4d91-b883-b1e54550e56a-image.png
ed58e765-7d34-451a-a128-f5a13a30a316-image.png

Time for some NAC + Jumpcloud + Chocolatey fun

Also done in 1.5.x dev-branch…