Posts made by Jonathan Cool

@sebastian-roth
Wahou ! Funny things !
So … all location use NAS as storage for images.
I’m the only one to use snapins.
Can i use the DefaultMember (Auto generated fog nfs group member) to store snapins ? I think, it’s the simple way … no ?

@sebastian-roth said in 1.5.4.8 to 1.5.9 : snapins dosen't work anymore:

What does your setup look like? On your FOG master node the NAS is configured as storage, right? Any other storages defined?

There is the defaultMember : not used.
There are 4 NAS for 4 differents geographic locations used to imaging (capture and deploy images) and for deploy snapins. NAS are not defined as Master Storage …

Hi everybody,

I used FOG 1.5.4.8 for a while to deploy snapins sucessfully using a NAS as node.

After upgrade to 1.5.9 (to fix a printers management missing INF field), snapins doesn’t work anymore …

I setup a new server and import database.

I created a new snapin and tried to deploy it on a workstation …and it’s failed.

I’m not sur but i think this line is wrong : “15/03/2021 13:23:31 Middleware::Communication Download: http://NASIP//fog/service/snapins.file.php?mac=D8:9E:F3:48:0C:2E&taskid=3946”
Why Fog client tried to download snapins.file.php on NAS instead of FOG Server ?
Have you a quickfix for this issue or do we need to update to 1.6 stable ?

snap OK sur FOG 1.5.4.8 avec client 0.11.16

------------------------------------------------------------------------------
 15/03/2021 15:20 Client-Info Client Version: 0.11.16
 15/03/2021 15:20 Client-Info Client OS:      Windows
 15/03/2021 15:20 Client-Info Server Version: 1.5.4.8
 15/03/2021 15:20 Middleware::Response Success
 15/03/2021 15:20 SnapinClient Running snapin netlogonTx64
 15/03/2021 15:20 Middleware::Communication Download: http://FOGip1548/fog/service/snapins.file.php?mac=50:XX:4C:XX:67:XX||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=3938
 15/03/2021 15:20 SnapinClient C:\Program Files (x86)\FOG\tmp\netlogonTx64.zip
 15/03/2021 15:20 SnapinClient Processing SnapinPack netlogonTx64.zip
 15/03/2021 15:20 SnapinClient Extracting SnapinPack
 15/03/2021 15:20 Bus Emmiting message on channel: Notification
 15/03/2021 15:20 SnapinClient Starting snapin
 15/03/2021 15:20 SnapinClient Snapin finished
 15/03/2021 15:20 SnapinClient Return Code: 0
 15/03/2021 15:20 Bus Emmiting message on channel: Notification
 15/03/2021 15:20 Middleware::Communication URL: http://FOGip1548/fog/service/snapins.checkin.php?taskid=3938&exitcode=0&mac=50:9A:4C:02:67:44||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
------------------------------------------------------------------------------

snap NOK sur FOG 1.5.9 avec client 0.12.0

------------------------------------------------------------------------------
 15/03/2021 13:23:31 Client-Info Client Version: 0.12.0
 15/03/2021 13:23:31 Client-Info Client OS:      Windows
 15/03/2021 13:23:31 Client-Info Server Version: 1.5.9
 15/03/2021 13:23:31 Middleware::Response Success
 15/03/2021 13:23:31 SnapinClient Running snapin wapt_agent
 15/03/2021 13:23:31 Middleware::Communication Download: http://NASIP//fog/service/snapins.file.php?mac=D8:9E:F3:48:0C:2E&taskid=3946
 15/03/2021 13:23:32 Middleware::Communication ERROR: Could not download file
 15/03/2021 13:23:32 Middleware::Communication ERROR: La connexion sous-jacente a été fermée : Une erreur inattendue s'est produite lors de l'envoi.
 15/03/2021 13:23:32 SnapinClient C:\Program Files (x86)\FOG\tmp\wapt_agent.zip
 15/03/2021 13:23:32 Middleware::Communication URL: http://FOGip159/fog/service/snapins.checkin.php?taskid=3946&exitcode=-1&mac=D8:9E:F3:48:0C:2E&newService&json
------------------------------------------------------------------------------

@JJ-Fullmer Many thanks for the lot of informations
After i update my fog server, i will use your precious informations to deploy my printers.

I will be back !

@Tom-Elliott Hi !
Thank you for your answers. I will try to update to the last stable version.
I will be back to post the result.

So, i can’t find any documentation about this field … maybe just set a path to the .dat file … i guess.

Hi !

I’m using the Printer Management to push the printer on the computers. It’s work flawlessly.

But now, i want to deploy a specific configuration of the printer : with theses commands, i can export and/or import a configuration :

export : RUNDLL32 PRINTUI.DLL,PrintUIEntry /Ss /n"Printer Name" /a Path\ConfigFile.dat m f g p

import : RUNDLL32 PRINTUI.DLL,PrintUIEntry /Sr /n"Printer Name" /a Path\ConfigFile.dat m f g p

I saw a special field on FOG Printer Management named “conf file” but i can’t use / edit this field.

There, 2 screenshots for better explanation : https://drive.google.com/drive/folders/1EjICoI8wM3DvKuyOlsbYO6_Wry-9RV91?usp=sharing

Maybe i did a mistake ?

Thank you

This old topic is solved !
I was setup a new FOG stable server on a debian (on a new disk) and snapins works flawlessly.

Solved !

Thank you to all for your answers.

I think, i will use the safe approach : i will clone my existing Golden Win 7 image in Virtual Box.
With the cloned image, i will install Ubuntu with Grub and upload the new “Golden Dualboot Win7/Ubuntu image”.

In my ref image, i do … nothing 'cause all conf", softs and scripts are run at the post-deployement …

I will try this approach and “i will be back” with the results.

Thank you for “the right way”

I’m using successfully a Golden Win7x64 img in my entreprise since years.
Recently, someone asked to me a dual boot with Windows & Ubuntu on a school room (25 computers). Only on one school room, not all rooms.

With my Win7x64 Golden img, i’m using the “resize” image type to reduce the final size of the image.

So … with dual boot, i can’t use this option (i think, not sure).

Is there a way to deploy the Win7 Golden image and after to deploy a Ubuntu classic image on other partition ?

Actually, i’m using one partition with my Golden Image : in reallity : the 100mb reserved partition and the system partition.

I’m not sure if i can but i was thinking about that :

• with fog.postinit : initialize partitions : how ? i don’t know at this point
• using fog server to deploy Golden Image in a classic way
• using postdownload script to deploy the Ubuntu image and install, configure Grub (Win7 in first)

Do you think i’m on the good way ?

Or i’m totally out ?

Thanks you for you advice.

Hi !

What is the best option for me ?

Maybe is to create a new fog installation (on new disk) with a stable version ?

I really need the snapins feature quickly.

Thank you for your answer

Hi,
I tried to update to 1.5.6.700 version but not more success …
i don’t want especially work in alpha version, just a version with snapins feature works … but i don’t want to lose my 16 hosts definition and my image definition.
Maybe i can tried to go to stable branch ?
(tips : https://forums.fogproject.org/topic/9370/how-to-download-the-different-branches/3)

Hi !
I’m using a local fog server for specific needs :
Sys Info :
Debian GNU/Linux 9
FOG Version : channel Alpha | Version 1.5.4.586
FOG_SNAPINDIR /home/images/snapins
FOG_CLIENT_SNAPIN_ENABLED checked

The upload task and download task work sucessfully but i can’t create any snapin : FOG says :Snapin Create Fail : A filen eithier already selected or uploaded, must be specified!

I tried whith 2 differents exe with this parameters :

Snapin Name : python-3.7.3-amd64
Storage Group : default
Snapin Type : Normal Snapin
Snapin Template : Batch Script
Snapin Run With : /c
Snapin File : python-3.7.3-amd64.exe
Snapin Argument : /quiet InstallAllUsers=1 PrependPath=1 Include_test=1
Snapin Command : cmd.exe /c  /quiet InstallAllUsers=1 PrependPath=1 Include_test=1

==> Snapin Create Fail : A filen eithier already selected or uploaded, must be specified!

Snapin Name : Putty
Storage Group : default
Snapin File : putty.exe

==> Snapin Create Fail : A filen eithier already selected or uploaded, must be specified!

root@foglocal:/home/images# ls -lha
total 24K
drwxrwxrwx 5 fog  root 4,0K janv. 11 09:08 .
drwxr-xr-x 7 root root 4,0K janv. 10 14:55 ..
drwxrwxrwx 2 fog  root 4,0K janv. 11 09:08 dev
drwxrwxrwx 2 root root 4,0K janv. 11 09:08 HPProBook640G2-CM2017
-rwxrwxrwx 1 fog  root    0 janv. 10 11:56 .mntcheck
drwxrwxrwx 3 fog  root 4,0K janv. 10 14:03 snapins
-rwxrwxrwx 1 root root    5 janv. 10 16:12 test.txt

root@foglocal:/home/images/snapins# ls -lha
total 12K
drwxrwxrwx 3 fog root 4,0K janv. 10 14:03 .
drwxrwxrwx 5 fog root 4,0K janv. 11 09:08 ..
drwxrwxrwx 3 fog root 4,0K janv. 10 14:03 ssl

History :

   14  apt-get update
   15  cd /opt/
   16  git clone https://github.com/FOGProject/fogproject.git
   23  cd fogproject
   24  git pull
   25  git fetch --all
   26  git checkout working-1.6
   27  cd bin/
   28  ./installfog.sh 
   41  cd /etc/dhcp/
   42  nano dhcpd.conf
   59  nano /etc/network/interfaces

What can i do to debug this error ?

Hi,
Today is a good day !
i tried a new test : i used an other NAS (Seagate) and created a public share.
With the same windows 10 station, i can xcopy files as SYSTEM and the printer was correctly installed.

So, now, on the Syno NAS, i will tried to join our domain … i will be back

@Quazz Hmmm, you right ! … seem to be possible !
I so close to resovle this issue … maybe, need to check the NAS configuration ?

Some news … weird … : see below … : on the Win10 1803 station :

C:\>PsExec64.exe -S cmd

C:\WINDOWS\system32>cd ..

C:\Windows>cd ..

C:\>whoami
autorite nt\système

C:\>net use Z: \\fog-nas\drivers_imp
L'erreur système 58 s'est produite.

Le serveur spécifié ne peut pas exécuter l'opération demandée.


C:\>net use Z: \\fog-nas\drivers_imp /user:admin
L'erreur système 58 s'est produite.

Le serveur spécifié ne peut pas exécuter l'opération demandée.


C:\>net use Z: \\fog-nas\drivers_imp /user:admin password
L'erreur système 5 s'est produite.

Accès refusé.


C:\>net use Z: \\fog-nas\drivers_imp /user:fakeuser fakepassword
La commande s'est terminée correctement #WTF ?! fakeuser doesn't exist on  the NAS ! What the HELL ?!


C:\>net use
Les nouvelles connexions seront mémorisées.


État         Local     Distant                   Réseau

-------------------------------------------------------------------------------
OK           Z:        \\fog-nas\drivers_imp  Microsoft Windows Network
La commande s'est terminée correctement.


C:\>net use Z: /delete
Z: a été supprimé.

@davido38
Hi,
I tried with LmCompatibilityLevel = 1 (already set) or LmCompatibilityLevel = 5 (i rebooted after modification) and no more success

@davido38 Yes, i enabled this protocol during my tests

Hi,

fog@fog-nas:/$ samba -V
Version 4.1.20
fog@fog-nas-44:/$ 

I will try ti logging with samba credentils asap …

Hi !
I’m back with the answers …

@Quazz

C:\>whoami
PC-test-Win10\administrateur

C:\>net use Z: \\fog-nas\drivers_imp
La commande s est terminée correctement.


C:\>xcopy Z:\test.txt
Z:\test.txt
1 fichier(s) copié(s)

C:\>PsExec64.exe -S cmd.exe

PsExec v2.2 - Execute processes remotely
Copyright (C) 2001-2016 Mark Russinovich
Sysinternals - www.sysinternals.com


Microsoft Windows [version 10.0.17134.523]
(c) 2018 Microsoft Corporation. Tous droits réservés.

C:\WINDOWS\system32>whoami
autorite nt\système

C:\WINDOWS\system32>cd C:\

C:\>net use
Les nouvelles connexions seront mémorisées.

La liste est vide.


C:\>net use Z: \\fog-nas\drivers_imp
L'erreur système 58 s'est produite.

Le serveur spécifié ne peut pas exécuter l'opération demandée.

@quinniedid

PC-test-Win10\administrateur

C:\>PsExec64.exe -S cmd.exe

PsExec v2.2 - Execute processes remotely
Copyright (C) 2001-2016 Mark Russinovich
Sysinternals - www.sysinternals.com


Microsoft Windows [version 10.0.17134.523]
(c) 2018 Microsoft Corporation. Tous droits réservés.

C:\WINDOWS\system32>net use
Les nouvelles connexions seront mémorisées.

La liste est vide.


C:\WINDOWS\system32>net use Z: \\fog-nas\drivers_imp
L'erreur système 58 s'est produite.

Le serveur spécifié ne peut pas exécuter l'opération demandée.


C:\WINDOWS\system32>cd \\fog-nas\drivers_imp\
'\\fog-nas\drivers_imp\'
CMD ne prend pas les chemins UNC comme répertoires en cours.

C:\WINDOWS\system32>

and the screensot of permissions displayed by Win10 : https://drive.google.com/open?id=1OEPXC-dYWlqfksnCKwxKFIzjbhj-7VoE

The win10 station and win7 station aren’t on the domain. Same with the NAS … but works win7 so … i think it’s not a domain issue. Isn’t it ?

Hi,
@quinniedid Nope, the NAS is only on the LAN but not configured for the samba domain.

I tried a new simple test on the Win10 v1803 : if i copy / paste the drivers into C:\ and set the printer (on the FOG printer management), the printer is seen correctly on the win10 … and i can SEE the drivers in the “printmangement.msc” Windows tool … so, the culprit is the share … not the driver, not the ini file … just the share … OR Windows 10 configuration.

So, the drivers are on a Synology NAS with :

• fog user (used to push FOG image by FTP)
• guest user enable.
  https://drive.google.com/open?id=1Rkkuvf221OG28hgBvZO4NbSs7TbSqjyh

The printer section on FOG :

Name : XXXX
Printer Port : IP_1xx.xxx.xxx.xxx
Printer INF file : \NAS…\HP_M402_DNE\hpdo602a_x64.inf
Printer IP : 1xx.xxx.xxx.xxx
Printer Model : HP LaserJet Pro M402-M403 n-dne PCL 6 (found into the inf file)

What can i try now ?