Thanks Fernando
I was able to download FOG using the link you provided

I don’t know what happened but now it’s just capturing used space.

Captura de tela de 2019-05-17 10-01-04.png Captura de tela de 2019-05-17 10-42-28.png

Thanks for that link. I’ll peruse it as well. At least Fog is old faithful and got my test computer up and running when USB/DVD both failed me miserably!

@george1421 That makes sense . Thanks very much sir!

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

Windows is a unique critter, but its possible if you create a winpe environment and then start the windows installer from a windows network share.

It seems like you have an nvme raid0, some linux based imaging solutions have problems with that.
As you say you must change from raid to sata to capture/deploy, clonezilla partclone make that suggestion.

I can see the pc that you link, so i cant help you with bios.

The computer must have an option to change it. Search a few more.

@Fernando-Gietz
Thanks.
You can set status to solved

@Sebastian-Roth Yeah, it was honestly my fault. Normally I’d capture and deploy immediately after to test, but these past few weeks have been ridiculously insane for me and my machine to image allocations haven’t been as up to date as they normally would’ve been.

I noticed this happened once before with a Windows image, but it was related to the dirty bit and another issue I found here. All in all I wanted to at least report and give this a go, I apologize for taking your time but as always appreciate the help. If this does happen again, I’ll be sure to give those kernels a go and report back here the results.

Configure the snapin to be replicated on the locations nodes, configure FOG to get the snapin from the location, be sure to be configured in general, as default and on the client settings.

Be sure that the snapin is replicated on the server you need and try it.

maybe you need to change, on the Snapin Pack Arguments the &quot ; by "

@Sebastian-Roth It works! Thank you for your help.

Starting deploying and image and ended up not having enough hard disk space (oops) but its all working correctly now. Learnt quite a bit from this experience as well. Thanks again

@Junkhacker

Thank you for the assistance. This issue was resolved. I’m not sure how to mark this as resolved though.

@george1421 said in Recreate Fog account:

exit;

george1421,

That worked, back in business.
Thank you very much for the assist.

@Sebastian-Roth
Ok thanks.
Waiting, workaround for us is to use SUN, MON, TUE, WED, THU, FRI, SAT instead of number for Shutdown and Reboot

Resyncing the fog service account password fixed my problem. Thanks, george1421!

@khalid said in unable to install with snapin:

this is an .exe file that runs perfectly on my local machine with just a simple … next next

You need to make this a so called silent install that can run without user interaction!

Here find some hints on the command line options you can use: https://installer.netbeans.org/docs/cli_options.html and http://wiki.netbeans.org/NetBeansInstallerTipsAndTricks#Simple_silent_installation_with_customization

Might be easier at this point to just do a complete re-install of the machine. I’m not sure why the partition table looks the way it does, but starting from scratch is sometimes the easiest bet.

This time I’ll start in the VM environment.

@lucas942 said in Nas node storage : permission denied:

I just got to find a directory in / images on the NAS 14gb its name is: e86a64cbxxxx and this corresponds to the MAC address of my PC.
So I rename this folder “Standard”?
Because the name of my image is “Standard”

You have a few things that are wrong.

The image file should be first captured into the /images/dev/<mac_address> folder. After the image is fully uploaded to the /images/dev/<mac_address> folder the target computer logs into the FOG server (nas in your case) via FTP and issues a move command to move all of the files in /images/dev/<mac_address> to /images/<image_name>.

The screen shot of the error you see about ftp_put tells me that in the storage node configuration there is 2 fields Management Username and Management Password. The values in those fields must match the user you created on the NAS device.

@george1421
New revelations have been made. As I said I now replicated the whole setup on a local isolated network (with exception of the apparmor modifications, not necessary on a bare-metal installation).

I have my witness-computer connected to both networks with 2 seperate NICs. Only one is active at a time. In both setups I first started wireshark on the witness computer and booted a notebook into pxe.

Main network: No packets or barely some DHCP-ACKs (that were not from the booting laptop). Isolated local network: Discover -> Offer -> Request -> ACK. Laptop got an IP from the router and loaded the appropriate bootrom from the fogserver and booted from it.

Conclusion: Since the witnessing of the DHCP-packets have nothing to do with fog itself it is safe to say that there is some sort of broadcoastfiltering of the DHCP-relevant ports. The (almost) exact same installation worked in an isolated network but not on the main network.

Thank you so much, I finally know the exact cause of the problem and am able to proceed. I now have to write up a request if the networking team would be so kind to allow the broadcoasting of those port-packets to a single static IP that I own (I really hope they’ll allow that. Now that I think of it this makes total sense. If people are able to plug in their own devices into the network that behave like a DHCP-Server and then handle the IPs before the main DHCP does you are in a golden MITM-position and can intercept with the network-packets to your desire). But as far as fog goes, this is nothing from its side.

So I think I can say this is solved for the cause of “troubleshooting”. Even if my journey is not exactly at its end yet. Thanks again!

@Sebastian-Roth Thank you very much. We had an outage last week so I didn’t have time to follow up. I just upgraded to latest dev-branch and things are working now. Advanced menu is working as it was before. Thanks everyone involved!

It seems like for the most part this worked. Thanks for your help @madeyem ! I suppose this is solved now.