@Tom-Elliott In first sorry if I seemed to insist heavily.
As i said before your works is great and the help on the forum also.
I will install fog as you explained me with “./installfog.sh -D /var/www -W fog/ -y” parameters.

Sorry again and thanks again for your precious help 😉

@Tom-Elliott said:

I chatted with Atton.

The suggestion I made to add seccomp_sandbox=NO was the issue.

The vsftpd service would “start” but promptly crash. Removing the line of sandbox and restarting the services, all systems appear to be operating properly now, from an FTP standpoint.

A good follow up question is… what is seccomp_sandbox and what does it do when set to no or yes, and what systems should this be set on?

I already know that (after four agonizing yet very educational weeks in February with my first FOG rundown ever) on Fedora 21 Workstation you absolutely must have it turned on.

@Deastrom said:

Is CIFS supported in 1.2.0 though?

Nope, sorry.

Do you have an example of what the storage node in the web interface would look like for a SMB storage node?

The same as one that uses NFS. you have to change the client’s boot code. Let me try to find my notes on it…

@plegrand said:

@ch3i i follow the instructions here : https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk ???
Then there is no more error message about FOG Multicast Management Server.

I’ve got always these :
Estimated FOG sites: Error contacting server
Latest Version: Error contacting server

Could you explain me what is the utility of “FOG prep”

During pxe boot of a client, the console is in qwerty, is there a way to pass it on azerty ?
You told me to create PXE files with azerty layout, but how you do that ?

Thanks a lot for your help

Helped in PM in french 😉

@Andrew-Seals

This is an FTP issue, and you’re in luck, we have a whole article about just this. 🙂

https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
Pay special attention to the “credentials” section of that - and test with the testing steps at the top.

Let us know how it goes, we are here to help.

@moto_ryan said:

@Scott-B

Hello,

I am very excited to be upgraded to the builds, from 1.2 - but I am having the same error. It seems the thread died with a solution if you ar
e behind a proxy, but both Scott and I are not. First, I was aiming for using btsync, but I am running into a permissions error - appears to be btsync itself, something in the config file I found here: https://github.com/tuxpoldo/btsync-deb/issues/182 . I am going to circle back to that error. For now, I used the wget and extracted the tarball. The installer found all of my old settings, but I am stuck adding a repository.

I am running FOG 1.2 on a Debian machine. I am stuck at

Adding needed repository…Failed!
System: Host:XXXXX Kernel: 3.16.0-4-amd64 x86_64 (64 bit) Desktop: MATE 1.10.0 Distro: LinuxMint 2 betsy

Future readers, follow @moto_ryan 's specific problem in this thread here: https://forums.fogproject.org/topic/5756/adding-needed-repository-failed-upgrading-from-1-2-0

To me it seams like shrinking btrfs is not much trouble. Although I have to admit that I’ve never ever tried this myself.

http://docs.oracle.com/cd/E37670_01/E37355/html/ol_use_case2_btrfs.html and various other sites on the net.

But don’t put any effort into this as long as no one is really asking for this!

@Wayne-Workman said:

@ch3i said:

@Wayne-Workman

To solve my problem I had to correct the /dev/sda3 before upload in debug task :
1/ Add free space before and after partition (2Mo for each)

/dev/sda1 100mb Windows Reserved /dev/sda2 Windows OS free space (2mo) /dev/sda3 Ubuntu OS / free space (2mo) /dev/sda4 Extended Partition /dev/sda5 swap linux /dev/sda6 /data linux (free for use) /dev/sda7 d: Windows (free for use)

Glad you got it solved. How did you add free space between the partitions? I’m curious.

Parted

No problem. I’m generally available.

@Guest said:

ok so used that path given and updated to FOG 4489.
now when i run FOG on a new VM i get Operating System not found

The error is on the client or the server ? oO

version 4238 should fix the typo.

Performed the following items in CentOS.

mv /images /home/

ln -s /home/images /images

Now the fog site is reporting correctly.
7-27-2015 8-05-17 AM.png

Thank you!

@Marcus-Allen Look inside of /var/log I had some pretty big files in there too.

Great this worked for me installing FOG on Kubuntu 14.04

Well that was dumb of me. I rebooted the server and everything is working now.

Ok, it is quite simple with grub.

For instance, with a debian jessie:

install ipxe with grub apt-get install ipxe Set the next grub boot to use the ipxe menu grub-reboot 2 Reboot ! reboot

The number to use is the number of the grub entry (counting the submenu) of the pxe entry, starting from 0.

Thank you for your help, I hope the result could help someone in the future.

FOG installs the FOG User when it’s installed.

The GUI is a database. FTP/local unix is a separate user.

If you can login to the Management page, look at Storage Management->Your Storage Node->Management username and password.

That password should be the password your local UNIX FOG user is using.

@Wayne-Workman said:

@Lyendril You can use Magical Jelly Bean keyfinder to extract your key.

Also, if the key is on a sticker on each computer, you could simply just type in this key after each imaging.

If you don’t have a Windows Installation Disk, you could just download one. Enter your key into it and see if it works. If it does not, you could activate over the phone (once) and then take an image of that.

I don’t think it matters so much that each computer is using the key it’s supposed to use - as much as - you have a legal key for each computer that is running said Microsoft product.

+1
In OEM installation, manufacturers use only 1 windows key for all computers (tested on HP), you can saved it (key/certificate) by using ABR (activation backup & recovery - google it) and use it with Windows 7 Digital River download (Not provide anymore by Microsoft but you can find it by another way…).

If you want more details PM me.

Works okay in fog version 3642