• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. tatanas
    3. Best
    T
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 46
    • Best 3
    • Controversial 0
    • Groups 0

    Best posts made by tatanas

    • RE: Unable to install printer

      Finally I found where the problem came from !

      We are using a NAS Synology to share the printers drivers. It’s a share accessible without password (guest account enable on the NAS). We’ve got no access problem to this share at anytime.
      This NAS is joined to the domain… And here is the problem !

      As soos as we unjoined the NAS from the domain, FOG printers are pushed without problem.

      I don’t know why but if you execute printui command as local system account when the drivers files are shared on a NAS member of a domain, there is an access error. If you try the same command as local Administrator, it works…

      So unjoining the NAS from the domain was the solution.

      posted in Bug Reports
      T
      tatanas
    • RE: Start imaging right after the Full host registration (without reboot), possible ?

      At the end of fog.man.reg, just add those lines between “. /bin/fog.inventory” and “usleep 2000000”

      sysuuid=$(dmidecode -s system-uuid)
      sysuuid=${sysuuid,,}
      mac=$(getMACAddresses)
      curl -Lks -o /tmp/hinfo.txt --data "sysuuid=${sysuuid}&mac=$mac" "${web}service/hostinfo.php" -A ''
      [[ -f /tmp/hinfo.txt ]] && . /tmp/hinfo.txt
      
      . /bin/fog.download
      
      
      posted in FOG Problems
      T
      tatanas
    • RE: Unable to install printer

      EUREKA !

      In the Fog service properties, I change the “Open session as” in Connection Tab from “Local system account” to “Administrator” with his current password.
      Then I reset the client Encryption Data on the Fog web console, restart the Fog client service and Voilà ! All printers are installed.

      Now we need to find why this problem appears “randomly” on host which was working fine ?

      posted in Bug Reports
      T
      tatanas
    • 1 / 1