@tom-elliott said in fog.man.reg in 1.5.0. RC9:

http://${web}… to just ${web}…

Well I feel dumb. Missed one. Confirmed and that works. Thank you once again.

@george1421 What is this project called? Do you see any difference between the df -h output? Mind posting a picture of the output when booting the patched FOS?

the restart did it for me:

[09-14-17 8:44:09 pm] * Starting FOG Multicast Manager Service
[09-14-17 8:44:14 pm] * Checking for new tasks every 10 seconds.
[09-14-17 8:44:14 pm] * Starting service loop.
[09-14-17 8:44:14 pm] * No tasks found!
[09-14-17 8:44:24 pm] * No tasks found!
[09-14-17 8:44:34 pm] * No tasks found!

@sebastian-roth

I’m confused regarding what the author is attempting to do with FOG. I believe he’s trying to install XP from a Windows XP CD ISO file using FOG. He doesn’t appear to be uploading a hard drive to FOG from a PC on which XP was installed and Sysprep’d.

Once upon a time, before FOG, I used PXE to load an ISO into RAM that could be any ISO - like the Windows XP ISO file. I also used a customized BartPE image to copy / clone to the local HD a sysprep’d xp disk image of various sorts, using the Microsoft IP stack and SMB.

Looking at the root=/dev/ram0 parameter is very reminiscent of that approach, where the ISO is copied to RAM over TFTP or HTTP and then booted. If so, one would end up having to do a manual install, if the ISO is the Microsoft CD, or an unattended install if the ISO had been altered accordingly. I did this w/o FOG, using PXECLIENT, etc. and with FOG v.32 by editing the FOG Menu and adding the items to load the ISO. I was also able to compress the ISO using an SDI format that come from XPEmbedded.

With this approach, there would be no capture step, and FOG would just be used as a boot loader to get the ISO up and running.

Or am I missing something?

Jim

Please make a new thread with an appropriate title for the fog issue.

@jgallo only in that case that I’m aware of. I don’t know what the problem is though I suspect it’s because firewalls are blocking access to port 21.

@tom-elliott yep its working thanks for all your help guys

Hello,
I deleted the record and then I updated “crn-cr02-19” with fog’s graphic interface
It’s OK
Thanks a lot !

@george1421 Thanks. I’ll try the upgrade and see if that fixes it.

@sebastian-roth

As recommended, I did upgrade to RC-9, and yes the issue has been resolved. Thanks all! Please mark this as solved!

@sebastian-roth @george1421

Sorry for the late response on this guys.

The issue with this turned out to be with the OEM recovery partition that came with our dell machines. For whatever reason fog didn’t like it. Removing this partition fixed the issue and we now have the new fog server, and all the new hardware synchronizing and imaging correctly.

Thank you guys again for all your assistance in this thread (and the others). This forum has been extremely helpful

@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.