Topics created by Alan Lim

HP desktop are a pain in the …

we had similar issues and the current solution we use is to deploy the FOG updates but keep refind to v0.11.0.

@george1421 Thank you for the information. I have managed to migrate/images, /snapin and the database to another new FOG server. Some steps needed to be done such as replacing the original IP with new IP. Because I intended not to use the original IP for the new FOG server as a backup plan. If anythings goes wrong with the new FOG server and I can revert to the original FOG server. 🙂

@Alan-Lim Just deploy the snapin task

@Alan-Lim @jfernandz The message Starting sshd: touch: cannot touch '/var/lock/sshd' : No such file or directory is normal with the buildroot version currently used for the FOS inits. While it’s not nice it’s not causing any kind of issue and can be ignored.

The mount error seen after that is probably caused due to a router or firewall now allowing all the traffic needed to mount an NFS share.

@george1421 Thank you for the guide link. The FOG is able to mount the external NFS as a storage node. However, there were errors that appeared after the end of the cloning. It doesn’t seem stable to me. Also, understand that the storage node might break if the FOG version is upgraded to the next version.
Therefore, at this moment, I have set up a physical machine instead of a VM to eliminate the issues.

@alan-lim

This is really just a starting point. You should adjust the instructions based on the mount point for your NetApp storage.