@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.

It may be possible that your browser extensions are blocking the script. so check it or disable all the browser extension once.

@lubo Carefully read through this to understand why this happens and how to solve it: https://forums.fogproject.org/topic/9850/freenas-ftp-command-question

[MOD Note] Forking topic since the issue doesn’t directly relate to this tutorial.

@george1421 If there is an easier way to do that, then I am all ears. I like the FOG interface though. Makes it easy. In your original method you posted does that require a hard drive to to be present or is it building the OS to init.gz in ram?

@quazz oh, you meant them? well i never used them really, sorry not to recognise them by name 😞

I did get uefi net booting with secure boot enabled working. I updated the tutorial here [ https://forums.fogproject.org/topic/11194/poc-using-fog-as-a-netboot-server/2 ] with the guidance.

Just realized I don’t have any spare machines that use the USB adapter on hand to test. Guess I’m gonna put a pause on this until the next batch of machines come in.

@unknownhost99 i just want to let everybody now that the server functions properly know thanks to everyone who replied, it was a great help and i love the service you supply keep going at it!

@susdtech said in New to Fog:

Do you need to pxe boot a desks top in order to capture or image a computer?

Yes. If that’s not possible for you, clonezilla would suite you better than FOG. FOG’s designed to remotely image thousands of systems and then configure all of those systems for you automatically. Clonezilla is doesn’t do that because it doesn’t scale, but Clonezilla is awesome at simply taking and putting images via USB.

Also, Is the client needed as well to complete this process?

No. But once you learn the power of the client, you’ll wonder how you managed to live without it.

I have tried installing the client on a Windows 10 VM and get the following error. “Unable to install CA certificate”
thanks for any help you can offer.

Try disabling antivirus. Also ensure you’re putting in the right fog IP address, and that the host is not pending in Host Management.

@avicitiffany You have the wrong tool. The FOG Project is used for copying windows images to computers. I has nothing to do with graphic arts.

@loosus456 Without directly knowing your setup I might be a little off the track with my guesses but here it goes, see what it’s worth for:

You need some kind of EFI boot manager (entry) to boot Windows. This is what Boot Camp usually does for you and it can be done using rEFInd for example as well. This boot entry is partly stored in NVRAM (not on disk) an therefore will persist even if you delete the macOS partition. But that doesn’t mean that you don’t need that. I think there is a chance you can do what you want because FOG comes with rEFInd on board that can start Windows straight from PXE booting. PXE to the FOG menu and default exit style rEFInd should do the trick. That gets me to your second question.

You can use USB keys to boot up into the FOG menu - this is not essentially PXE booted but it’s still partly network booting after the initial boot from USB. But you can also fully PXE most Macs! Take a look at our wiki article on this. One simple method I like is blessing the Mac so it does load iPXE straight from the FOG TFTP server without you having to setup DHCP properly. But in your case I don’t think that’s a good option because once macOS is gone it’ll be very hard to change the blessing later on. So you can either go the “Using stones…” method or set the Macs to netboot before deleting macOS - the later has a similar issue to the “Using stones” method because you can’t easily change the bootup setting if macOS is not installed anymore.

I don’t know of any tool that can set boot configuration in NVRAM on Macs other than macOS itself. Possibly tools exist but I don’t know of any. Maybe it can be done using a macOS boot USB key? Give it a go and let us know!

Special note: There is one particular ethernet card in some Macs that do have an issue with iPXE on macOS Sierra and newer - see here! I am working on this but I can’t say when I’ll get that fixed. But it’s only that one particular NIC as far as we know - Broadcom 57765. Take a look at the device manager (About my Mac) to see if you have that NIC in your Macs.

@kktwenty101 said in upgrading to 1.4.x - fog client version?:

building a brand new FOG server to supplement the old one.

You can follow along with this article: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

yes it can do what you want. FOG stores all of its data in an easy to read database. We looked at automating FOG from another of our applications in the past (but didn’t bother going forward as it didn’t actually save us much admin). For FOG tasks (scheduled, instant, delayed etc), simply insert something into the fog.scheduledTasks database for a scheduled task etc (the fog.taskTypes gives you an indication of what you can do). The backup process kicks in from the pxe by default in FOG. You can set a task to reboot the PC too in FOG if you wish.

Obviously it is a DISK BACKUP not an incremental backup. Expect the backups to take many minutes if you run high compression. Even low compression is a heavy task.

It will be a network backup, local backups (to USB etc) will not be possible unless you configure multiple storage nodes per PC (not practical).

@george1421 said in Win 10 image:

@jackiejack You can, but they are mostly wrong for your current setup.

No what I mean is for the SIM part. Can I follow it? Or this one:
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/settings-for-automating-oobe
Or this one
http://searchenterprisedesktop.techtarget.com/tip/Create-a-hands-free-Windows-10-install-image-for-the-OOBE

See what particular scares me is section 25 v 2 b vi of https://forums.fogproject.org/assets/uploads/files/1469134024622-fog-universal-image-setup-win-7.pdf?v=78s341l4bha

she says

It seems odd to add this twice, but otherwise after sysprep it will still
prompt for an initial local account name. It may be possible to remove
the OOBE section, but I haven’t experimented with it.

Since I wanted a fully automated install of win 10 (with 2 admin accounts) should I follow this windows 7 guide? Or use the other links?

Or create the local admin accounts in audit mode first (not in SIM) then SkipUserOOBE but they say that is deprecated.