@tom-elliott Anything is possible where I work. : )

I will see if that could be the issue and let you know.

@sebastian-roth said in Snapins - ISO File:

response within a week. So I guess the OP is happy w

Yes this issue has been solved. Thanks !

@george1421 yes

@aziraphale I have to ask you do you use the linux user account fog for system maintenance AND you change the password on that account? If so that linux user account is an internal system account used and managed by FOG. We find that sometimes people will change the password on this account and then capture fails. There is a process to fix this condition if that is what happened.

@amir3161 Are you still interested in this? I’ve lost track of this issue. Or maybe you figured it out yourself?

@Lebowski Did you upgrade to 1.4.4? Does it still throw the error?

@Jphipps Sorry this got somehow lost. Is this still an issue or did you get this solved on your own?

I am marking this solved now as there hasn’t been any response and my guts say that this is not a general issue. Not with FOG and not in iPXE. Possibly this is a very specific hardware related issue but we won’t be able to fix this as there is not much information that we could work on.

@entr0py Tom was saying that there was an issue with resizing in 1.4.4, would you try out upgrading to the latest RC9 version and see if this is solved.

@bigjim Could this be an issue with fast shutdown being enabled in Windows?

@sgwk Sorry, couldn’t find the time and resources to try this out. Anyone having this setup at hand out there?

@msi said in Remove and stop FOG to act as a DHCP server:

[root@localhost dnsmasq-2.76]# sudo make install
/bin/sh: cc: command not found
/bin/sh: cc: command not found
Package dbus-1 was not found in the pkg-config search path.

I am not sure about the dnsmasq stuff but usually there is the magic three steps when compiling software on linux: ./configure, make and make install. Not for dnsmasq?

@msi Did you install dnsmasq as rpm now. Shall we mark this solved?

@natsufiree Please let us know about the current state of this! Will mark this solved fairly soon as George’s suggestions should put you on the right track.

@kvrprasad Any news on this issue?

@CoxM Please post the log as requested or we will close this.

@zingaro Please let us know if you could follow the description in the other post and got it setup on your system as well or if you need any more help with this.

@ENorum Did you give George’s suggestion a try. Please let us know if you could make this work or if you need further assistance with it.

So I am marking this solved now. Feel free to open a new post in case you run into another issue.

@markus1204 With FOG there are 2 parts to the images. The first part is the raw data files stored in /images/<image_name> (this is what you have today). The second part is the meta data that is stored in the data base (what you are missing). If you know the settings you can manually recreate the meta data by filling in the proper settings to point to the raw physical files you have in /images/<image_name> directory.

@CBO Just in case you are still interested in this. I just pushed changes to the current working branch (see here and here) to make the installer do a better job. Upgrade to the very latest and give it a go if you like.

PS: Sorry for taking so long to get back onto this.