Posts made by ITSolutions

This is by design, you should be able to access it either ipaddess/fog or ipaddress/fog/management

Here is a guide on how to set it up. There have been mixed reports on this working.

https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node

@CDown Everyone has their opinion on the best version. I recommend Ubuntu, for anyone not overly familiar with Linux, it is the easiest to find guides usually for troubleshooting. I would go with 14.04 as it is the latest LTS(not counting 16.04 that just came out, as it changed a lot and could break things).

I would recommend setting up with 2 HDD or 2 partitions, one for the OS and database and one for the images, this will avoid the accidental mishap of filling the HDD when capturing an image and locking yourself out of the system. I usually will setup a second drive and mount it to the /images folder before installing FOG this will help FOG install everything in the correct spots and not have to walk through moving the images store later on. Not sure of how many images you will have, but were I am right now, we have images for each model with over a dozen models and a 500gb drive is more than enough. Just a good thing to plan ahead on storage. Let me know if you have an questions along the way.

@CDown That maybe your problem there. As both Ubuntu and FOG have changed so much between the versions in question it is hard to start tot troubleshoot. Especially if this is a new install with no data to worry about I would recommend wiping and starting fresh.

While you are at it I would also recommend installing the trunk of FOG as it is very stable and is better supported now and in the future. I have been using trunk for nearly a year now and I know many others have been for at least as long. It will also be more compatible with newer hardware as it is released. Not to mention the great new features that have been added to trunk.

@CDown Did you perform an upgrade to 14.04 and install FOG 1.2 over .32 or did you do a complete wipe of the old 12.04/FOG .32 and start fresh?

When you unplug the network cable to move it over to the new network you will need to restart the DHCP service
sudo service isc-dhcp-server restart

Or just restart the machine, when you get it moved off the “live” network to it’s segregated network location.

@csieb Can you try using the FOGService.msi file as the snapin file and then running
FOGService.msi /quiet /uninstall

@Connie You need to re-upload the picture. It must not have worked correctly

@ITCC So this is your first image with the FOG client for testing? I would try the command I mentioned earlier and see if that helps. You can also try uninstalling and reinstalling the client to see if something went wrong in the install.

You could try running
sudo ./installfog.sh --recreate-CA --recreate-keys

Also forgot to ask is this a new install of FOG? Also is it a new image, I see it is on a VM?

Are you getting this on all machines or just this one?
What version of FOG are you using(the number in the cloud)?

@Quazz ah, yes you are right. I didn’t think about that, enterprise only. And not installed by default. But the FTP test should work from Windows. I would try connecting to the FTP share from the CentOS that should give you an indication as to if the server with NFS is accessible.

@arnaudrigole Yes, even from a Windows machine you can try mount 10.1.11.64:/Images *
This will mount to the next available drive letter to test if the NFS is accessible. It should ask for Username/password, make sure to use the FOG username/password as that is what you gave access to.

You can also try to connect to the FTP share with ftp://10.1.11.64 and see if it gives access.

Basically we are trying to narrow down where the failure is, it definitely appears the permissions on your NFS share are not correct in some fashion, but just want to see if you can connect to everything independently.

@arnaudrigole Let’s see if @Wolfbane8653 can help as he wrote the steps and probably is more versed than I in this method.

But to help him out can you give us a little more information:
What OS is FOG on, Debian, Ubuntu, Cent, Red Hat?
What version of FOG are you using (1.2 or Trunk, if trunk what version does it say in the cloud on the management page)?
What version of windows is the NFS share coming from Win 7, Win 2008, 2012?
What version of Filezilla are you using?

It’ll make it easier to narrow down possible version issues with this information.

One quick question also is can you access the NFS share from any other machines?

For your second issue to access your local storage, you don’t need to use FOGCrypt. The password is plain text in the webgui. The only thing to use FOGCrypt for is the legacy client. So try changing the storage node password to the plain text of your new password.

For the NFS part, did you make sure the password for the share is your new password for the FOG account that you changed? Also are you running the commands over SSH using the FOG account or another account? In the steps on that article the only account getting access is the FOG account, so if you are using best practice and not doing things under the FOG account with SSH that could give you the permissions error. Try running all SSH under the FOG account and see if that works for you.

Edit: Sorry but I am not a linux “expert” and not great with fedora in general, usually on debian/ubuntu distros. But I think I see what the issues seem to be.

So I am assuming you have /run/media/root/fedora-expanded/images and /run/media/root/fedora-expanded/images/dev?

Have you tried this article https://wiki.fogproject.org/wiki/index.php?title=Adding_Storage_to_a_FOG_Server?

If you want all of your images moved to this new spot and not have the original location it maybe best to set it up like this and make sure the mount points are /images and /images/dev otherwise you need to make many more changes to make everything work. It sounds like just changing your mount point would be easiest and best now that everything is moved to your new drive.

What OS are you using(ubuntu, CentOS, Redhat, etc) and what version of FOG?
I assume everything worked before added the storage correct?
Did you mount the new volume as /images and /images/dev or is this additional storage?

You can try running chmod -R 777 /images to set the correct permisssions.

Past that until we get more information we can’t help anymore.

FOG creates an account named “fog” to do all of it’s functions. It is very bad practice to use “fog” as the account for you to login as this account gets a random password set by the installer. I am guessing that the account is getting locked out due to password violations caused by FOG. I would create a different account for you to use such as FOGAdmin or whatever and let FOG use the local “fog” account.

@herrpommesfrite Yes, it should be the same thing. Is there anything else installed on your image or is a clean win 7 image?

@herrpommesfrite That shouldn’t make a difference. If the old client was uninstalled then it shouldn’t cause any issues with the new client. Can you try changing the host name in FOG to something new, just name it “adtest”. I am just trying to rule out all possibilities.