Best posts made by ch3i

@boeleke Hi, If your NAS is mounted on your FOG server via NFS you can’t re-export it as NFS via FOG server. You have to create a node storage with IP of NAS ans specify NFS and FTP path in the node settings. Before you have to create a user “fog” in your NAS with the same password of the “fog” user of the FOG server.

When you’ll upload/download image on that node (Your NAS) the fog client will connect directly on your NAS not via your FOG server.

@boeleke FTP and NFS path or the sames on your NAS ?

@boeleke For QNAP the NFS path seem to be : /share/your_nfs_share but for the ftp access it’s /your_nfs_share. In FOG trunk (https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk) you can differentiate NFS and FTP path. In your version FTP and NFS path must be the same !

@boeleke I’m working in a School and use Trunk version Trunk versions of FOG are “stable”.

@boeleke said:

I teamviewed with @ch3i & he did it!
New password , more rights on the QNAP & better settings for the node.

Thank you verry mutch guys! For the patience ;)!
You can set this topic on SOLVED

There was two problems : NFS path and NFS network access.

@boeleke What version of FoG client are you using ? 0.9.11 ?
I ask you about that because I’d that problem on 0.9.10.

@boeleke The legacy password is for the legacy client : it’s useless in your case.
Could you post the fog.log present on a client at c:\fog.log ?

@george1421 said:

@Wayne-Workman said:

Nope.
Just need a “fog” user, and ftp and nfs configured for a directory. You also need a subdirectory called dev and you need a .mntcheck file in both the shared directory and the dev directory.

Do we have a wiki on a kb on setting this up? If not I can look into it tonight. I have our (redundant) backup synology nas just idling right now.

For Freenas : https://wiki.fogproject.org/wiki/index.php?title=Use_FOG_with_FreeNAS . It can help you.

@george1421 Please look at : https://forums.fogproject.org/topic/6857/the-storage-groups-associated-storage-node-is-not-valid/7

@Tom-Elliott and @Wayne-Workman said, try to launch your web browser in private mode to ensure that you don’t have auto-fill and cache :

• Chrome/Opera : Ctrl+Shit+N
• Firefox/IE : Ctrl+Shift+P

@arnaudrigole said:

@Sebastian-Roth
Thank you, i think too !
But the described procedure seems to be not secured! (grant RW access for “all”, “all machines”, “everyone” on shared folders…

the cryptowall “locky” ransomware that we had last week ravaged our datas and infected all folders which was shared with “everyone” rw right…

Au besoin PM moi sur le forum, je pourrais surement te venir en aide.

@GFm In the web UI : FOG Configuration > FOG Settings > FOG Service > FOG_GRACE_TIMEOUT

@abos_systemax Hi, I don’t see ipxe64/86.efi files in /tftpboot :

ls -l /tftpboot/*.efi
-rw-r--r-- 1 fog root 196960 mars   1 17:13 /tftpboot/intel.efi
-rw-r--r-- 1 fog root 914112 mars   1 17:13 /tftpboot/ipxe.efi
-rw-r--r-- 1 fog root 196480 mars   1 17:13 /tftpboot/realtek.efi
-rw-r--r-- 1 fog root 195744 mars   1 17:13 /tftpboot/snp.efi
-rw-r--r-- 1 fog root 195936 mars   1 17:13 /tftpboot/snponly.efi

@Quazz Hi, when you install the FOG client you have to enter the ip address or the hostname. You have left the default value during installation fog-server

@MagicLink said:

i try with Filezilla and can’t connect with root or fog user (“LOGIN incorrect”). Winscp/putty works.

Can you post the result of : service vsftpd status

@MagicLink It’s seem to be good, can you post the result of : cat /etc/vsftpd.conf

@raumin Hi, I saw your post on another topic about that error, have you try Tom solution ? : https://forums.fogproject.org/topic/6857/the-storage-groups-associated-storage-node-is-not-valid/4

@andyroo54 You can edit it from the GUI on the “User Management” tab. There is no link between fog user on GUI and fog unix user.

@Wayne-Workman said:

You can script this. Just write a batch file to detect if there is a “Wireless Network Connection 1” or not… There are other ways too, like detecting if there is a battery percentage or not, if there is a lid-close setting available or not. Once you have these checks in a script and working, you can just push your snapin to all systems.

@FlowLive Hi, you can use DMI information to get chassis type.

On a linux (in my case it’s a VM on an ESXi) :

# dmidecode --string chassis-type
Other

On a windows laptop using a script(in my case a HP Elitebook 820) :

Dim Wmi :Set Wmi = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Dim Arg, Col, Obj

For Each Col In Wmi.ExecQuery("Select * from Win32_SystemEnclosure")
For Each Obj In Col.ChassisTypes
 Select Case Obj
  Case 1  :Arg = "Other"
  Case 2  :Arg = "Unknown"
  Case 3  :Arg = "Desktop"
  Case 4  :Arg = "Low Profile Desktop"
  Case 5  :Arg = "Pizza Box"
  Case 6  :Arg = "Mini Tower"
  Case 7  :Arg = "Tower"
  Case 8  :Arg = "Portable"
  Case 9  :Arg = "Laptop"
  Case 10 :Arg = "Notebook"
  Case 11 :Arg = "Handheld"
  Case 12 :Arg = "Docking Station"
  Case 13 :Arg = "All-in-One"
  Case 14 :Arg = "Sub-Notebook"
  Case 15 :Arg = "Space Saving"
  Case 16 :Arg = "Lunch Box"
  Case 17 :Arg = "Main System Chassis"
  Case 18 :Arg = "Expansion Chassis"
  Case 19 :Arg = "Sub-Chassis"
  Case 20 :Arg = "Bus Expansion Chassis"
  Case 21 :Arg = "Peripheral Chassis"
  Case 22 :Arg = "Storage Chassis"
  Case 23 :Arg = "Rack Mount Chassis"
  Case 24 :Arg = "Sealed-Case PC"
  Case Else 
   Arg = "Unknown"
End Select
Next
Next

WScript.Echo " Type = " & Arg

or via wmic :

c:\wmic systemenclosure get chassistypes
ChassisTypes
{10}

@ManPage Hi, I think there is no option to do that. But it’s a good idea.