Yet this morning I restarted it and everything is fine. So I’m really confused. Let me try capturing an image again…
EDIT:
I was able to get it working and I searched the apache logs and found an error on on a fogmanagement file which someone else had a topic on and had to remove a & symbol. Everything seems to be good and the image was captured. Thank you.
@george1421 said in ISO PXE Booting:
@alansopro I remember this software now. You use this iso to download and create your boot image. The older ones had everything already on the iso. Since this 620 is 10 years old we might look at an old iso image. When I last upgrade a 710 that’s what I ended up doing, but still using the USB boot method, then in the update gui picking usb0: as the file path.
So getting this ISO to net boot is not the answer, but getting the product this iso creates to net boot is. Again a lot of this is from my crusty memory so take it all with suspicion, I do.
Yup…It’s a 10 year old brand new server. Just pulled it out of the Dell box! Lol
I do agree though it’s much easier to update my R740s.
@george1421 said in ISO PXE Booting:
@alansopro Ah I remember this iso. I ended up using a 8GB flash drive to upgrade the server. If I remember right There was an FTP option built into the software as well as a SMB network share.
So if I can get it to netboot the maybe the other methods will work. Some of these were hard coded to look at the DVD drive.
I’m downloading the ISO right now.
Yeah, unfortunately USBs aren’t really a thing here.
Dell shutdown the FTP option they switch to HTTPS/Mirror sites and in order to get the server to do that you need to update the Lifecycle Controller.
I didn’t try the SMB share though. I actually have it updating now through the ‘Virtual DVD’ method but I had to find Java 7 in order to get the virtual console to work properly.
Again, once updated HTML5 will be available.
They should make a way of upgrading to that point and then finish upgrading other ways.
I have multiple R620s though and I will eventually need to do this to all of them and want to make it easy on myself.
The ISO is on Dell’s website.
That is a direct link. It is slightly larger than 2.7GB I believe.
Hello,
So this is an odd one but I didn’t feel some of the other topics related to it.
I’m trying to use the Dell Platform Specific Bootable ISOs and have them boot from FOG.
It’s a Linux OS but configured to auto install firmware updates for servers.
My question is how can I add this to the menu as a ‘raw’ ISO to boot too? Is this even possible with FOG?
@Sebastian-Roth there isn’t anything in the logs. I even cleared both and kept trying but the logs never changed. The access log shows the 500 Server error but nothing in the error logs.
Hello,
I wasn’t sure if this is the right area to get help. I used the LDAP plugin when on the older 1.5.7 version of FOG and it was working.
I just upgraded to 1.5.8 and now when logging in it redirects to a page with a 500 server error. It doesn’t matter what login it is it redirects to a 500 server error.
I can login with the root fog account but the LDAP that I had previously setup no longer functions. Has anyone encountered this?
@Tom-Elliott said in FOG Image Tasking "Force Task":
Force task to start is more intended for deploy tasks.
I’m not quite sure why it would clear the storage node when you click force to start though.
Tom,
I did recently try to force the task on a deployment and it did the same thing. It cleared the storage node and threw a bunch of errors. I had to cancel the job and redo it without the ‘Force Task’ so I think there is a bug with that function. Not that I need it but just thought I’d report back with my findings and let you guys take it from there.
Thank you.
I was thinking that was what it was only intended for deploying but wasn’t entirely sure.
If it could be possible to fix in a future release that would be awesome. Sometimes you click it unintentionally without realizing it and then the cloning process just starts throwing errors and it’s hard to remember what it is sometimes. 
Hello,
Versions of software…
FOG: 1.5.7
OS: Centos 7.7 / Latest Updates
I’m not sure if this is a bug within FOG or if it was resolved in FOG 1.5.8. I haven’t had the time to upgrade FOG yet but will once done imaging multiple systems.
When tasking a system to ‘capture’ an image I would go to the tasks and select the lightening bolt otherwise known as ‘Force task to start’. When doing so it clears out the ‘Storage Node’ from ‘MAINSTORAGE’ to blank. When done imaging the host spams a message no storage node and returns a “/bin/upload” error.
Is this a bug yet I’m not sure why I’m using the ‘Force to start’ lightening bolt to begin with when the task initially starts, it was just out of habit.
If this isn’t supposed to be used for this what is the purpose of that? Is it a wake on LAN function?
Thanks.
Yet this morning I restarted it and everything is fine. So I’m really confused. Let me try capturing an image again…
EDIT:
I was able to get it working and I searched the apache logs and found an error on on a fogmanagement file which someone else had a topic on and had to remove a & symbol. Everything seems to be good and the image was captured. Thank you.