@entr0py said in Error Restoring Images - Clients having identity crisis:

Upgrading to the latest git version solved my image resizing problems but now I’m having another issue.

Can you please be more specific to which version you upgraded. Latest git can mean different things. Is it dev-branch or working. As well post the version numbers you see in the blue cloud on the web UI.

When you schedule a tast for a client you don’t do multicast for all 27 labp PCs, right? Scheduling for xxx-002 for example, what do you see in “Active Tasks” on the web UI? Does it say 001 or 002? Something seems odd here.

@wayne-workman

So after some time again message came back even after clearing cache and not rebooting. We had to image a computer and I noticed that when the computer tried to check in after the iPXE files were loading prior to imaging that the error for the computer checking in stated the same message as the storage nodes on the dashboard valid database connection could be made. I will image another computer and screenshot that error.

@jgallo Oh I see now. I needed to modify the fog.postinit file to call patch.fullreg. So now the last line in fog.postinit reads
. ${postinitpath}patch.fullreg With that final modification, my custom registration menu now works! Thank you for all the help, this community has been great and I am really liking FOG.

@x23piracy That image is on 1607.

@jbranka4 Sounds kind of strange that machines with Win 10 did still work but Win 7 ones didn’t. From what I know about this it shouldn’t really matter if it’s Win7 or 10 in that case IF

exit style is configured the same way for all of those machines all are either legacy BIOS or UEFI

I kind of expect to see a difference between those machines beside Win7/10, most probably BIOS vs. UEFI.

@fallingwax said in MAC Address problem. Maybe?:

… machine would not load FOG

What exactly do you mean by that?? Please describe in more detail or post a video or picture of an error you see.

@FallingWax Ok, now I see what’s wrong here. Thanks for reporting this issue. Moved your post to bug reports.

When changing the way FOG exports the DB we obviously missed out on fixing the backup script as well. No one reported yet so we didn’t notice until now.

You can edit that script and exchange line 74 which starts like wget ... with the following call:

wget --no-check-certificate -O O $backupDir/mysql/fog.sql "http://$ipaddress/$webroot/maintenance/backup_db.php" --post-data="type=sql&fogajaxonly=1" 2>>$backupDir/logs/error.log 1>>$backupDir/logs/progress.log 2>&1

This is until we fixed this in the official code… @Tom-Elliott Mind having a look if this call is about right?

And now let’s get back to the initial question…

@Taspharel said:

I can open the page to install the kernel just fine, but clicking on “install” doesnt do anything.

There is no “install” button there. Please take a screenshot of what you see when things go wrong. Just want to make sure we talk about the same thing. Have you tried in Firefox yet? Are you behind a proxy server by any chance?

@Deimos Great to hear you got this solved. As well you are more than welcome to join in and help with all kind of stuff like translations and such. Not sure if you are familiar with how git works and wanna get your hands dirty. If not you might just download the latest german messages.po here, modify and post the changed version in a new thread here in the forums. Thanks in advance!

Kind of funny as I’m from Germany too but I’ve always used FOG in English language… and never found the time to fix the translations.

@jackiejack said in Win 10 image:

or should I post this on a virtualbox forum?

You better do so. Unfortunately I don’t think we are able to properly help you with that. Though there might be people around having had this issue too. Not sure. But you’re definitely better off posting this virtualbox-specific problem in their forums.

@jjcjr Ok just for clarity you are following the instructions from my first post? If so yes you need LOCAL in there or in your my.cnf file you need to set the … <something> path to empty.

@damonledet Are you able to deploy to those machines? This would mean that iPXE is able to hand over to the Linux Kernel…

@Almeida Which version of FOG do you use? And please tell us what Linux system you use in dual boot on the client.

Have you done a full filesystem check on the partition showing that issue?

@wayne-workman Thank and it is working!

@imagingmaster21 As posted in the other thread it appears you are sending the wrong file name to a uefi system. You need to double check your dhcp server configuration to make sure you have the settings correct.

Well I can see from the message, you are trying to boot a uefi system. What exactly do you have configured for dhcp option 67? If its undionly.kpxe then that is your issue. You need to send a uefi boot loader like ipxe.efi.