Posts made by Taspharel

Hi.

I am stuck with an error on one of our clients.

FOG Version: 1.5.5.3
Running on Centos

Deployment works on all clients that I’ve tried it with in the last couple days, nothing has changed that I know of.

I get the error message:
PXE T01 File not found
PXE E3B …

And the client switches to normal HDD Boot.

When I check with Wireshark: The Client requests everything correctly - resulting in undionly.kpxe being requested.
But then Wireshark shows me an error: Error Code, Code: Not defined, Message: TFTP Aborted

I have no idea whats happening.
Undionly.kpxe is in the tftpboot folder on the FOG Server, the DHCP Settings on our Windows server seem to resolve correctly …

Does anybody have an idea what steps I can take next to troubleshoot?

Thanks for the support.

Hei

As Sebastian stated, for a domain join to function the Host will have to have the client running.

Information here https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

And for further questions, have a look around the wiki first, it will answer many questions. Anything not listed there people on the forum will be able to help you with. The Developers are VERY active and great

Then its not pending

What happens when you LAN Boot from the machine? Can you log on and register it?

@maouu

Can you find the host (Mac Adress: 3C:D9:2B:53:53:BA) in your Pending Hosts list (Under Hosts -> Left side)?
When you PXE Boot the Host via your LAN, can you do a registration from there?

Hi.

You could try resetting the encryption keys.

That option should be available in the Host Details in your FOG Web-UI.

Not sure if it directly relates to this, but I think what that button does is to make FOG “forget” who is registered to a certain mac / hostname and when the host then contacts the server the next time FOG accepts that connection and establishes a trust relationship … or something like that

Hej

The settings are rather clear. All you need is to set the FOG Active Directory Settings to the correct OU and use the correct User and Password combination.

The Wiki has an article on this, if that doesnt help feel free to ask more

https://wiki.fogproject.org/wiki/index.php?title=Active_Directory_-_FOG_Setting

@butch2861 said in Windows 1809 Ent. Error after Upload to FOG:

@Sebastian-Roth After you run sysprep on a pc and upload the Image to the Fog Server the next thing that happens is the pc reboots and then the Fog Server loads the image just uploaded BACK to the pc you uploaded it from; almost like testing the uploaded image to the pc it came from as a test that it works.

Hi there

I was wondering, does the pc with the “golden” image restart and install correctly if you dont capture and deploy it?

Cause if it doesn’t that might mean that FOG is not involved in the problem at all - the error message I have had as well at some points, not sure what caused them then.

@nguyenanhquy
Hi

There is quite a few ressources explaining how to set up a FOG server .

Once you have managed to do that - taking care of possible DNS challenges - you can go forward and either make a live-boot image available or go the way of building your own image and then making that available to your computers in the network. This could probably be done in a “live” way as well.

As Sebastian said this scenario is not what FOG was built for, but it is rather easily imagineable to build something along those lines.
Maybe somebody else has already set up something like this, but the best way will probably be to read the wiki links and tackle it yourself.

The developers here are extremely friendly and helpful, but its always easier to help with specific problems and steps than answer a sprawling: Tell me how to set up FOG and do X or Y.

Get your feet wet, dive in and everybody will be happy to help if you get stuck

Thank you so much, with the new / old inits the capture process ran successfully. Am trying to deploy now and see if everythin works out.

Thanks for your help
Sébastien

Thanks, will try this on monday.

Great help as always!!

Ah well. Downgraded the Kernel to the Kernel mentioned here https://forums.fogproject.org/topic/12181/rcu_sched-self-detected-stall-on-cpu-when-capture/7 and here: https://forums.fogproject.org/topic/12929/error-rcu_sched-self-detected-stall-on-cpu-on-legacy-bios-capture-job/16

I got the same problem mentioned in the second link:

FATAL: kernel too old
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00

I tried rebooting the server, no game.

Now I am not sure I understand the information in the second link correctly. I am on the dev-branch and updated today. Is there something I have to do with my FOG version - besides the kernel version downgrades?

cough
shuffle
squirm

N…o?

Thanks.

Hei there.

I was wondering if somebody can give me a hint on what is happening.
While trying to image a Windows VM, I get the following Error message:

INFO: rcu_sched self-detected stall on CPU ... (206461 ticks this GP) idle=14a/1/4611686018427387906 softirq=53141/53141 fqs=51421
(t=273012 jiffies g=22900 c=22899 q=1093)

This repeats with increasing numbers at the different spots (ticks, idle, t, jiffies etc.)

What can I do? Will try to restart the capture task and see what happens.

Currently running FOG version: 1.5.2.10 on Centos7

Just saw I’m a few version steps behind, will also try an update. But would be interested to know what the message tells me?

Do you use setupcomplete for your image?

Then adding this might work:

sc stop “WSearch”
sc config “WSearch” start= disabled

Would deactivate Indexing by disabling the Search Service. Havent tried it though.

Does Ubuntu include yum?

I suppose you would have to use apt-get instead of yum, dont know enough about Linux myself though to say if the package names etc. would be the same for every distributions repositories …

Hej.

Just thought about this a little.

The Quickregistration can have its values set. So you would have the values auto-added once Quickregistration is selected.

In order to Quickregister automatically you would have to set Quick Registration as the default menu item that is selected when the FOG Menu Times out. Also you would have to set the Quick Registration Option in the iPXE Menu to only show on unregistered hosts.

In order to auto-login to the fog menu you would probably have to follow the guide that was posted recently, allowing for you to save the password and username when a host boots from network. You should be able to find that on the forums somewhere, dont have the link handy. (it might be here: https://forums.fogproject.org/topic/4433/is-it-possible-to-remove-the-fog-quick-image-password/30)

But: All Computers would have to be set to automatically boot from the network first, so possibly (if not already set up) you would have to go to every single computer nontheless to change the BIOS Settings.

The order then would be:

• Computer starts
• Computer autoboots to Network
• Login is automated
• The ipxemenu shortly displays and times out
• The Default Item from the ipxe menu is selected and executed
• Quickregistration auto fills the fields and inventories the computer
• The computer reboots
• On next reboot the computer is no longer unregistered and thus the Quick-Registration on the ipxe Menu wouldnt show … not sure how FOG handles this and if there is kind of a hierarchy to the “default items”, but i suppose it would then just sit at the menu until you enter something?

This is not tested, just me thinking through the options I found in the FOG settings.

Hi iekozz.

There is an article here: https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq that describes how to use FOG if you cannot modify any settings on your internal systems.

It also includes information regarding UEFI which is supported by FOG.

Regarding the images: It is possible to make generic images for FOG. The simplest way is to make a windows image, then generalize it in audit mode. There is guides for this but in my experience its something you have to work through in order to get it to work the way you want it to. But there is quite a few good starting points, some of them on these forums as well.

If you copy all necessary drivers to the windows driver folder, the setup will extract only the necessary ones. This comes at the price of image size. There is also a way to store drivers on the fog server and extract the ones you need with a postinstall script. This is probably much better to do, but involves some extra work that I never came around to doing.

Hi Ahmed.

There is already some information in this thread here:

https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

Maybe that will get you started.

@nextechinc said in Booting System Rescue CD 5.2.2:

cpuid --ext 29 && set arch 64 || set arch 32
set path /netboot/systemrescuecd
set nfs_path /var/www/netboot/systemrescuecd
kernel http://${fog-ip}${path}/isolinux/rescue${arch} docache setkmap=us
initrd http://${fog-ip}${path}/isolinux/initram.igz
imgargs rescue${arch} initrd=initram.igz netboot=http://${fog-ip}${path}/sysrcd.dat setkmap=us dostartx
boot

Thank you so so much. I was struggling to get the SystemRescueCD to work at all, now it works

I think I used some tutorial on here or wiki somewhere and my paths were different, I had to use

path /srcd

And had to change the paths in kernel and initrd to

kernel http://${fog-ip}${path}/rescue${arch} docache setkmap=de

and

initrd http://${fog-ip}${path}/initram.igz

As well as imgargs to:

imgargs rescue${arch} initrd=initram.igz netboot=http://${fog-ip}${path}/sysrcd.dat setkmap=de dostartx

This may be my specific setup being somehow messed up, but in case somebody else has the same setup as I do …

Not necessarily the same problem, but I had to work around a certificate error by adding this to my setupcomplete.cmd file that is run after Windows Installs:

certutil -delstore "Root" "FOG Server CA"
certutil -delstore "Root" "FOG Project"
certutil -addstore "Root" "%windir%\System32\Sysprep\fog.ca.cer"
certutil -addstore "Root" "%windir%\System32\Sysprep\ca.cert.der"

And of course add the certificate files to the folder referenced above.