Posts made by Jonathan Cool

Hi,
I’m sorry for the UP but the issue is still here
Can’t copy drivers with a Win10 v1803 computer …
am i the only guy use this feature (Printers management) on FOG ?

Hi,
@quinniedid
WIN7 computer has joined the samba 3.x domain.
WIN10 hasn’t joined the domain.
Drivers are not on the domain server but on a NAS disk (anonymous share)

Just to help to debug : same problem on Win10 physical computer.
Exact version of Win10 during test : 1803, last updates 2018.11.15.

I’m back with some results on Win7 & Win10 :

On Windows 7 : (logged on local administrator)
C:\install>whoami
PC-test-win7\administrateur

C:\install>PsExec.exe -S cmd.exe

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


Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.

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

C:\Windows\system32>xcopy \\xx.xx.xx.xx\drivers_imp\
\\xx.xx.xx.xx\drivers_imp\test.txt
1 fichier(s) copié(s)

C:\Windows\system32>



On Windows 10 : (logged on local administrator)
C:\install>whoami
PC-test-win10\administrateur

C:\install>psexec -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.345]
(c) 2018 Microsoft Corporation. Tous droits réservés.

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

C:\WINDOWS\system32>xcopy \\xx.xx.xx.xx\drivers_imp
Spécification du lecteur non valide
0 fichier(s) copié(s)

C:\WINDOWS\system32>

With administrator account (local administrator account on the Win10) : 
C:\install>whoami
PC-test-win10\administrateur

C:\install>xcopy \\xx.xx.xx.xx\drivers_imp
\\\xx.xx.xx.xx\drivers_imp\test.txt
1 fichier(s) copié(s)

Hi,

@george1421

I use -S with PSExec to run the xcopy with SYSTEM account.

I think, I don’t need any credentials because the share is open to anonymous users (public hidden read only share).

If i try to access this share using \NAS\drivers_imp\ or \@IP\drivers_imp, it’s works without any credentials

@Sebastian-Roth
No more success with the IP address …

Weird, nope ?

Hi @Sebastian-Roth ,

I tried to copy files from NAS with PSExec and i can’t … :

PSExec -S copy \\NAS\drivers_imp\test.txt

“Couldn’t access NAS” : same results with Win7 or Win10 …

I not sure but PSExec isn’t the best tool to copy files, isn’t it ?

Hi @Sebastian-Roth ,

Yes, you right.

In win10, the port is created but the drivers aren’t copied on the system (no drivers found in printmanagement.msc).

Where i can find any logs about the copy process ? No information in the fog.log

Hi !
I’m trying to use the printer management service with FOG.

On a Win7x64 with an HP LaserJet PRO M402, it’s work.
The same printer with Win10x64 is not showing in the Windows printer management.

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)

On the Win7x64 client : after the FOG service execution (drivers on NAS) :

• in the Windows printer management : i can see the printer
• with printmanagement.msc : i can see :
  -> the port
  -> the drivers

On the Win10x64 client : after the FOG service execution (drivers on NAS) :

• in the Windows printer management : i can’t see the printer
• with printmanagement.msc : i can the port BUT i cannot see the drivers …

If i use the “Fog PrinterManager Helper” on the Win10x64 with the same parameters (drivers on NAS) :

• in the Windows printer management : i can see the printer
• with printmanagement.msc : i can :
  -> the port
  -> the drivers

The share is a public share without any authentification.

FOG seem not be able to copy the drivers on Win10x64 with the FOG Client … or something like that …

If i use the FOG Client on the Win10x64 with local drivers (Printer INF File : C:\HP_M402_DNE\hpdo602a_x64.inf) :

• in the Windows printer management : i can see the printer
• with printmanagement.msc : i can :
  -> the port
  -> the drivers

What can i do ?

Win10x64 version : 1803 (without any antivirus)

Today, i’m the very happy french of the world … 'cause it’s WORKS !
I tried on o7010, o5050 and o7050 and it’s works !
Wahouuuuuuuuuuuuuuuu
I just want to say many thanks to you both and i think, it’s not enough … !

Long live to FOG Project

fog.postinit :

sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr]*[Ss][Ee][Rr][Vv]#gi" /bin/fog.upload
sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr]*[Ss][Ee][Rr][Vv]*#gi" /usr/share/fog/lib/funcs.sh

Label on C drive removed on the Golden image.

Happy Face

Solved !!

@Quazz said in Win7x64 : Golden Image : partitions problems ... again:

@Jonathan-Cool My “fuck this shit” solution atm is the following if you’d like to try it

Note that this is experimental and can cause issues on systems with odd labels so use at own risk… but

sed -i -e "s#\\[Rr\\]\\[Ee\\]\\[Ss\\]\\[Ee\\]\\[Rr\\]\\[Vv\\]\\[Ee\\]\\[Dd\\]#[Rr]*[Ss][Ee][Rr][Vv]#gi" /bin/fog.upload
sed -i -e "s#\\[Rr\\]\\[Ee\\]\\[Ss\\]\\[Ee\\]\\[Rr\\]\\[Vv\\]\\[Ee\\]\\[Dd\\]#[Rr]*[Ss][Ee][Rr][Vv]*#gi" /usr/share/fog/lib/funcs.sh

In the second line, we can see a “*”, is-it a mistake or not ? (line concerning funcs.sh)

After your answer, i will try :

• to update my fog.postint
• remove my C label

@Quazz
Hi.
I can try to remove my C label partition and see the result or it’s not necessary anymore ?
Same question for the last “sed” you proposed …

Maybe my best option is waiting the fix in a next release … ?

I will try to remove this label on the C drive and recapture the image … and try a new download on the optiplex 7050.

I will be back !

@Quazz said in Win7x64 : Golden Image : partitions problems ... again:
Did you assign a label to the drive per chance?

Yes, my drive is named “System” into my Golden Image … https://drive.google.com/file/d/0B48PuYLEHxQLUEU5clJOZC1Vb3c/view

Maybe this name is confusing FOG ?

Maybe i choose wrong parameters when i created my VM with Virtual BOX the first time ? (details on the first topic) ?

Yes i can !

d1.fixed_size_partitions :

:2

d1.partitions :

label: dos
label-id: 0xc91a5cff
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=      204800, type=7, bootable
/dev/sda2 : start=      206848, size=   335335424, type=7

d1.minimum.partitions :

label: dos
label-id: 0xc91a5cff
device: /dev/sda
unit: sectors

/dev/sda1 : start=        2048, size=       52316, type=7, bootable
/dev/sda2 : start=      206848, size=   335335424, type=7

What do you think about that ?

Hi,
I’m back … i typed the same commands on client during a DL Debug Task … : same results : (with SSH)

[Fri Sep 28 root@fogclient ~]# fog
 * Running post init scripts.........................Done
 * Press [Enter] key to continue
^C
[Fri Sep 28 root@fogclient ~]# grep Vv /usr/share/fog/lib/funcs.sh 
            if [[ $label =~ [Rr][Ee][Cc][Oo][Vv][Ee][Rr][Yy] ]]; then
            if [[ $label =~ [Rr][Éé][Ss][Ee][Rr][Vv][Éé] || $label =~ [Rr][Éé][Ss][Éé][Rr][Vv][Éé] ]]; then
[Fri Sep 28 root@fogclient ~]# grep Vv /bin/fog.upload 
                            *[Rr][Ee][Cc][Oo][Vv][Ee][Rr][Yy]*|*[Rr][Éé][Ss][Ee][Rr][Vv][Éé]*)
[Fri Sep 28 root@fogclient ~]# blkid -po udev /dev/sda1 | grep LABEL
ID_FS_LABEL=Réservé_au_système
ID_FS_LABEL_ENC=Réservé\x20au\x20système
[Fri Sep 28 root@fogclient ~]# 

The patch seem to be applied as you can see … " if [[ $label =~ [Rr][Éé][Ss][Ee][Rr][Vv][Éé]"

@Quazz Sorry, i’m not sure if i understood the question about this file … i take a screenshot of the folder of my Golden Img :
https://drive.google.com/file/d/1iN8YbEsgOsCSu622R9qG4JzRE9xjXo1B/view?usp=sharinga
But, yes, i recapture the image before lastest sed

I’m back with bad news …

my fog.postinit :

#!/bin/bash
## ....
#. ${postinitpath}<SCRIPTNAME>

sed -i -e  "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr][Éé][Ss][Ee][Rr][Vv][Éé]#gi" /bin/fog.upload
sed -i -e  "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#[Rr][Éé][Ss][Ee][Rr][Vv][Éé]#gi" /usr/share/fog/lib/funcs.sh

Upload Debug Task : Seem to be good this time … https://drive.google.com/file/d/1cv2Lerb5MGFQlwkvHO1jKcfoa8580KWv/view?usp=sharing

After a deploy on o7050, same problem : Reserved Partition : 78Gb …

Maybe i can try a debug download task to see what the hell is going on ?

Back with the results … : https://drive.google.com/file/d/1Kf9DscMwdhU7VCRf5Y-L7rL86qXQc1wP/view?usp=sharing

Holy shit, i forgot to run “fog” and ctrl+c … i will be back soon with the real results …

@Sebastian-Roth said in Win7x64 : Golden Image : partitions problems ... again:

@Jonathan-Cool Holy crap (sorry)! Thanks heaps for testing both blkidcommands, the one Quazz posted and the one I did. I would have never expected those to return such different results!! As we use the blkid -po udev syntax in the scripts (ref) we are back in the race. Mind trying this script:

#!/bin/bash
## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post init scripts are
#. ${postinitpath}<SCRIPTNAME>

sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#\[Rr\]\[Éé\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Éé\]#gi" /bin/fog.upload
sed -i -e "s#\[Rr\]\[Ee\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Ee\]\[Dd\]#\[Rr\]\[Éé\]\[Ss\]\[Ee\]\[Rr\]\[Vv\]\[Éé\]#gi" /usr/share/fog/lib/funcs.sh

Again, boot up the client in debug mode and run:

grep Vv /usr/share/fog/lib/funcs.sh
grep Vv /bin/fog.upload
blkid -po udev /dev/sda1 | grep LABEL

If those match you can go ahead and capture the image (issue command fog on the console and step through).

Hm, it’s seem not match …

my fog.postinit :

#!/bin/bash
## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post init scripts are
#. ${postinitpath}<SCRIPTNAME>

sed -i -e "s#[Rr][Ee][Ss][Ee][Rr][Vv][Ee][Dd]#[Rr][Éé][Ss][Ee][Rr][Vv][Éé]#gi" /bin/fog.upload
sed -i -e "s#[Rr][Ee][Ss][Ee][Rr][Vv][Ee][Dd]#[Rr][Éé][Ss][Ee][Rr][Vv][Éé]#gi" /usr/share/fog/lib/funcs.sh

The results on my VM - Debug Upload Task : https://drive.google.com/file/d/1vAlGXD-PKZgv_Kwve9NIsSkWqobHyOR2/view?usp=sharing