Printers Management : Win10x64 NOK, Win7x64 OK



  • 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)



  • 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)



  • @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?



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


  • Developer

    @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?



  • 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)
    
    

  • Moderator

    @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_imp
    

    just 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.



  • 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 ?


  • Moderator

    @Jonathan-Cool said in Printers Management : Win10x64 NOK, Win7x64 OK:

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

    I guess I would have to ask what credentials are you using here? You are using an UNC path, then I would assume you are using windows CIFS protocol. What process owner is launching the psexec? (sorry I didn’t read much of this thread if its already been answered).


  • Developer

    @Jonathan-Cool You might try using IP in UNC path and use xcopy: PSExec -S xcopy \\x.x.x.x\drivers_imp\test.txt . (untested)

    Make sure you run this as system user!



  • 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 ?


  • Developer

    @Jonathan-Cool Don’t think we’ll find any logs about the copy process. I am not sure how to debug this.

    This is a bit different but still it might be helpful to debug the issue. Try using PsExec to start a Windows command line as local system account (which is used to run the fog-client) and see if you can copy files from your NAS: https://superuser.com/questions/1165384/unable-to-access-network-drive-as-system-account-on-windows-10windows-server-20

    Possibly this might help in the client?!? https://support.esri.com/en/technical-article/000002722



  • 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 :(


  • Developer

    @Jonathan-Cool Just to sum this up. Working with Win7 no problem but in Win10 it only works when the drivers are NOT on the NAS but stored locally?!

    I wonder if this is some kind of windows driver location security thing!?


 

598
Online

5.4k
Users

12.6k
Topics

118.6k
Posts