Topics created by bardicverse

The developers just commented in another thread that 4.7.1 has been re-engineered to support FOG 1.2.0 for those that can’t migrate to 1.3.0 right now. You won’t get support for Win10, gpt disk format, NVMe disks, or the 1000s of improvements in 1.3.0 over 1.2.0, but you will get the latest sata and nic support with 4.7.1

You can access these kernels here:
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32

They go into the /var/www/html/fog/service/ipxe directory.

So, I found a very odd but simple solution. Apparently hitting the Enter key on the keyboard advanced it to the next screen, and started uploading. Odd, but it worked.

I would try by removing the current information on the disk and making sure a partition exists, follow the directions listed here please: [url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]

yup tried that too, doesnt fix the issue. The problem is the workflow - client computer set to upload a new image - folder is created under /images/dev, then is transported to its final spot /images/(image name) . This normally works flawlessly. Yet, it seems that because “root” is the owner of the temporary folder, it wont allow “fog” to copy it and then remove it from its temporary spot. Since this process in fog is consecutive and unattended, there’s no time to pause and chmod or chown the folder.

Basically I need to make “fog” be the users who creates the temporary image folder. Yet, right now, its “root” who has that honor. I need to figure out where I can assign “fog” for the folder creation process.

In the /tftpboot/fog/kernel folder resides the default kernel, it is called bzImage, this is the kernel the fog boot menu uses as I think that is hard coded in fog. If you cannot get your computers to register you will need to replace the current bzImage kernel, which according to Google is kernel version 3.2.4, with a kernel that allows you to complete the registration process. In order for your new kernel to work for the registration process it will have to be named bzImage.
So you will need to replace the default kernel with the kernel that works.
My suggestion is to use the GUI interface and find the kernel you need and download and install from there. Its the quickest and easiest way for me to do it.

if you map a network drive under audit mode it will be part of the default profile aslong as you specify in your unattend.xml to copyprofile. Every profile change you make will be captured in audit mode, i think the idea of audit mode is so that nothing machine specific is copied over which and makes it easier to handle licensing and to skip oobe and have un-needed personalisation.

There is a great section in the user guide about uploading your first image.