So this can get marked as resolved. Everything worked as expected except when you update the nodes the GUI did not show the new version until after we updated the Master. All the issues we had with 1.5.4 were resolved with 1.5.6. Very happy with this update.

GUI is super fast!
The freezing on formating MBR/GPT on start of imaging is back to only a few seconds. Replication seems to be acting normal again.

@Sebastian-Roth Yes I had already had it disabled.

I tested that node and it still deploys image so my guess is its a glitch in the GUI until we update the master node.

@Sebastian-Roth @Tom-Elliott We planed a maintenance window tomorrow morning to update our FOG. We were going to update storage nodes today but when we update the nodes from 1.5.4 to 1.5.6 in the FOG GUI we no longer see them connected. 072Cache was updated to 1.5.6 and we updated the username in GUI to fogproject and verified the password. Is this normal until we update the master node to 1.5.6?

@Sebastian-Roth Thank you for that we will do that when updating to 1.5.6, but for future upgrades is it best practice to update nodes then update master? If we miss a node (we have 12-15) will that break the master node in any way? Also if we update nodes and then don’t update the master will that break things? What happens if we update the master but not the nodes. Say we go to 1.5.63 then 1.5.7 comes out. If we don’t go back and then update all of them right way that ok but I would assume you would want them to be updated eventually correct?

CentOS Linux 7.5.1804
FOG 1.5.4

Sorry if this is a dumb question but was not able to find the answer to this in the wiki or in the forum.

What steps needs to be taken to update our current FOG installation from 1.5.4 to 1.5.6 other than taking a snapshot before running new installer?

All our FOG Storage nodes are currently on 1.5.4. Do we update nodes first? Does it matter? If Storage nodes need to be updated first but we missed one and it comes on after we updated our master fog to 1.5.6 will things break?

@george1421 For anyone following this post for Precision 3530.

• It does have a internal NIC.
• It does have Legacy Boot BUT NOT for Internal HD. Thus you must deploy a UEFI image to this model.
• In my case I have only been using BIOS and I now need to create a new Golden Image for UEFI.

Thank you all for the help

@george1421 It has a NIC but it does not allow Legacy Boot to internal HD. FOG images it but it wont boot to HD. We have not done anything to FOG to get it to be able to image UEFI.

Centos
FOG 1.5.4

@george1421 No but to be clear I have the 3530 which you mentioned in a post here. Do you want me to create a new post for it?

@george1421 I have no clue what that is.