Printers Management : Win10x64 NOK, Win7x64 OK
-
Hi,
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 ?
My stuff :
Server :
FOG Version : Running Version 1.5.9
OS : Debian GNU/Linux 10
FOG Client Version : 0.12
Specifications :
> All images are on a Synology NAS storage : mounted with NAS_ip:/images
> French user :)
> “If everything would work the first time, what would you have learned?”
Challenges make knowledge growth … by George1421 ;) -
@Jonathan-Cool said in Printers Management : Win10x64 NOK, Win7x64 OK:
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).But SYSTEM user is local system only. I’m pretty sure it doesn’t have rights on remote systems.
If i try to access this share using \NAS\drivers_imp\ or @IP\drivers_imp, it’s works without any credentials
But who are you testing this as? SYSTEM or a domain level users logged into a domain computer?
as a test why not try something like command script
net use \\x.x.x.x\drivers_imp /user:domain\user <password> xcopy \\x.x.x.x\drivers_imp\test.txt . net use /del \\x.x.x.x\drivers_impjust to see if it is a user permission issue. The other thing you need to know where . points to. I would maybe use the full path here like c:\drivers or some other existing path.
-
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) -
@Jonathan-Cool Do I see this right, confirm that Win10 is having that issue per se. Anyone an idea why SYSTEM user is not able to copy files from a UNC path?
-
Just to help to debug : same problem on Win10 physical computer.
Exact version of Win10 during test : 1803, last updates 2018.11.15. -
@Jonathan-Cool Are both WIN7 and WIN10 machines joined to a domain? Is the server that your drivers are shared on joined to a domain?
-
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) -
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 ?
-
@Jonathan-Cool To me this seems like a “simple” permission issue. What if you create a public share for this drivers where no authentication is needed? Not sure if I miss the point here.
-
@Jonathan-Cool Is your NAS also connected or configured to your samba domain?
-
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 ?
-
@Jonathan-Cool Still seems to be a permission problem from what I can tell.
You can try to test by assigning a drive letter as the system user to the samba share and see if you can then access the files using the drive letter assignment.
Something like:
- net use V: \server\share /user:name1 passw2
- xcopy V:\drivers C:\drivers
- net use V: /delete
I’m guessing if the W10 joined the domain that could work too.
-
@Jonathan-Cool I find it very interesting that a SYSTEM account will work on Windows 7 but not Windows 10. One thing I would like to see is doing the same thing with PSExec running as the SYSTEM account and once you have that command window open change the directory to where you usually have the drivers dumped to. Run the xcopy from the NAS. I would be curious to see the behavior difference between Windows 7 and Windows 10.
Also, can you capture a screenshot of the security permissions of the folder specially on Windows 10 that the drivers are dropped into? Something like this:
-
Hi !
I’m back with the answers …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.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 ?
-
@Jonathan-Cool Error 58 indicates this has to do with how Samba has changed between Windows 7 and Windows 10, specifically for security.
What Samba version is the NAS running?
Try logging in with Samba credentials to the share in the net use command instead of guest logon.
-
Hi,
fog@fog-nas:/$ samba -V Version 4.1.20 fog@fog-nas-44:/$I will try ti logging with samba credentils asap …
-
Hi,
is the smb1 protocol enabled on windows 10 ?
by default it is not.
-
@davido38 Yes, i enabled this protocol during my tests
My stuff :
Server :
FOG Version : Running Version 1.5.9
OS : Debian GNU/Linux 10
FOG Client Version : 0.12
Specifications :
> All images are on a Synology NAS storage : mounted with NAS_ip:/images
> French user :)
> “If everything would work the first time, what would you have learned?”
Challenges make knowledge growth … by George1421 ;) -
@Jonathan-Cool
As-tu essayé de modifier la clef de registre windows 10HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
LmCompatibilityLevel avec une valeur 1 ou 5 ?
-
@davido38
Hi,
I tried with LmCompatibilityLevel = 1 (already set) or LmCompatibilityLevel = 5 (i rebooted after modification) and no more success
