Posts made by george1421

@awellis can you drop the firewall all together until you can get multicasting working? If you need the firewall per company policy we can reverse engineer what ports are being used.
systemctl stop firewalld

@awellis said in FOG Multicast Not working:

whereas the initial firewall setup

Will you explain this statement? What firewall?

@uwpviolator Putting a 5 or 10 second sleep would not hurt. That would give the drivers a chance to init before you make pass Next.

As for self installers, I would tag them onto the end of the setupcomplete.cmd file. Just make sure you are sure of the silent install switches.

I do something a bit more complex with my setupcomplete.cmd I have it check for a certain batch file name in the c:\drivers directory. If that batch file exists I call that batch file towards the end of the setupcomplete.cmd file. Remember that directory comes from the fog server with hardware specific drivers. Well if there are self extracting .exe installers in the driver pack that are hardware specific I include them in the driver directory on the fog server. Those get copied over and the setupcomplete.cmd file will call the batch file in the c:\drivers directory which installs the hardware specific .exe drivers and applications.

@uwpviolator I’ve found that I need to call that pnputil 2-3 times to find all hardware hidden behind other hardware.

I agree that 1709 did some bad things to the non SCCM image cloners.

The short answer for this is to create a custom fog iPXE menu (using the web gui). This will chain back to your organization’s pxe server. Then from FOG you would set this new menu item as the default.

So the idea is your default pxe server chains to fog’s ipxe. If FOG has something to do it will do it, if not the default action for the FOG menu is to chain back to your organization’s pxe server. Just be aware you will need to chain back to a point where the pxe client won’t turn around and chain back to the FOG server again creating a chain loop.

@mmoore5553 When you get the second nic installed let me know and I will give you the instructions. The setup is not hard you need to know the name of your physical ethernet adapter (eth0 or what ever your kernel calls it) and then set a default route on your second nic pointing towards the internet. Ensure your physical LAN adapter has a static IP address set for the imaging network. And finally use the git method of downloading the installer files. During setup the installer will ask you for the name of your imaging network adapter (not in those words) you just need to ensure its your physical LAN network adapter name. The rest will be installed correctly.

@george1421 Confirmed these applications exist on my test synology nas (I’ve done bad things to this NAS so it might have the kitchen sink too).

du is installed and available.
awk is installed and available.
sha512sum is installed and available.
head is installed and available.
tail is installed and available.

They also exist on my production synology nas.

@tom-elliott Now that’s service!!

I can say for the synology nas, you have to install php as a package. I’ll confirm that the other utilities exist.

@mmoore5553 I would agree, the hidden file is create in /opt/fog called .fogsettings (the dot in the beginning of the name makes it hidden). If that file does not exist then the FOG installer did not complete. So you have a botched install.

Recommendation: If you were to reinstall the FOG server, use debian instead of ubuntu. Connical has been doing some bad things with ubuntu lately causing us pain. Ubuntu is based on Debian so all of the install commands work the same.

@mmoore5553 You can fix what is there now, and then add the usb network later. Its just easier to do it in the beginning. But reinstalling to just fix what is wrong is more effort than fixing it.

You will need to edit the following files to fix what has been changed.

Correct the fog server IP address here:
/opt/fog/.fogsettings
/tftpboot/default.ipxe
/etc/dhcp/dhcpd.conf

Then in the webgui you need to go to the fog configuration settings. Pick the Expand all options and then search for the old fog server IP address, change and then save the settings. I think its in 3 places under fog settings.
Lastly in the storage management -> default storage node you need to fix the IP address there too.

It should take you about 10 minutes to fix then reboot the fog server.

@mmoore5553 Well you have a mess to clean up

Well not really. FWIW if you want to have a dedicated imaging network but have fog able to reach the internet for installation (only needed for that) then its ideal if you install a second network adapter in your fog server. When you install fog you will tell it to only image using network adapter X while network adapter Y has internet access to download the required files. Once the files have been downloaded you can unplug the second network adapter until you need to update fog, if you have security concerns. Or you can use the second network adapter for FOG management. That bit is up to you.

If this is possible in your environment I can guide you on how to set it up.

@mmoore5553 So then there is a possibility that the FOG server’s IP address/subnet mask has changed?

@tom-elliott I think that the new method is cleaner than before. Is that call in the fog replicator code? The thought would be to reverse engineer it. Or see if we could get some node.js code running on the NAS to respond to the replicator with the answer its looking for. I know quite a few people use a NAS as a storage node.

@kafluke Assuming its possible, you will need to install php on your windows nas. I started working on a PoC for using a windows 2012 server as a nas. You can either install WAMP (well just WAP) on windows or install a php plugin for IIS.

@tom-elliott said in FOG continuously syncs files that haven't changed to remote storage nodes:

. if the nodes don’t have the webfiles this would explain the continuous syncing. Fog can’t validate the remote files are the same so it will continuously delete and resync all the files.

Ugh, this is a game changer. When did this “feature” change? (not intending to make this sound harsh) This requirement will now break using a nas as a storage node.

@kafluke said in How do I schedule FOG image replication for after hours?:

@george1421 thank you so much! These are even the exact times that I needed to set the job for! You da man! This can be marked resolved now.

That is why I get paid the big bucks… oh wait… never mind.

@mmoore5553 So fog is on an isolated imaging network.

To install fog you need to have internet access. That is a requirement if you install from git or the tarball.

FOG does not like it if you change the fog server’s IP address after fog is installed. If you do change the IP address then fog will break. Its possible to fix, we just need to know this happened.

What is your logic to have fog on an isolated imaging network?

@tesparza A suggestion I can give you is this. Use 7-zip to extract that direct-x .exe file. It is a self expanding archive file. Then you will need to change how you deploy it, you will need to deploy it as a fog snap-in pack and not a .exe

@tesparza Well that is why, she no work. Its asking you a question on the hidden screen

@shad0wguy I can tell you setting up nfs was the hardest bit of getting the nas to work as a storage node. I need to look back at my post to find what was the key to make it work. It was simple once I learned what was needed.

For testing I can give you some tips.

Login to your fog server. Then run this command.
sudo su -
Then find out who you are
whoami
If you are root then good. You can test your nfs mounting by
mount -t nfs <nas_ip>:/IT-Files/Images /mnt
When that mount command works then you know you have the nas nfs setup correctly. Also watch your case, you are dealing with linux which is case aware.

On the nas you need to have nfs v3 enabled. FOG doesn’t support nfs v4 yet.