• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. kratkale
    3. Topics
    K
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 45
    • Groups 0

    Topics

    • K

      Windows 11 | 65x HP Z2 Tower G1i

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      0 Votes
      3 Posts
      483 Views
      M

      @kratkale said in Windows 11 | 65x HP Z2 Tower G1i:

      Can I specify in FOG which hard drive to clone to? For example, using the serial number? That could be stored in the host entry

      Hi, this is a known issue when using NVMe, as you’ve probably already discovered. I’m not sure whether FOG 1.5 supports using serial numbers to target disks, but someone from the team may be able to confirm that. FOG 1.6, however, does support targeting disks by serial number.

      I ran into the same situation. As a workaround, I customized my init.xz to use the PCI path instead, since those appear to be more persistent.

    • K

      Failed to set disk guid ...

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      16
      0 Votes
      16 Posts
      3k Views
      S

      @kratkale You are welcome. It’s good to have people around who rapidly test things that we push out. 🙂 Thanks to you!

    • K

      FOG 1.5.6 Multicast problem?!

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      24
      0 Votes
      24 Posts
      9k Views
      K

      @Sebastian-Roth WhatsApp Image 2019-05-04 at 15.35.11.jpeg WhatsApp Image 2019-05-04 at 15.34.44.jpeg
      25 an 36 PC in Multicast

    • K

      Printer Management with FOG

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      3
      0 Votes
      3 Posts
      918 Views
      S

      @kratkale Ok, I finally got the time to get into fog-client development again. I am trying to answer your questions step by step.

      About port naming: The field Printer Port is what you see in the Windows printing dialog as “Port name”. So if you put in 9100 it will be named 9100 but if you put in an IP the port will be named exactly as you want it. On the other hand if you want to specify a different TCP port for printing you put in x.x.x.x:9111 in the Printer IP field. I will change the field labels in the FOG web UI to make this clear.

      Changing the printer setup on FOG changes sometimes nothing. (e.g. the name of the inf file - the printer …) My solution was to deploy the computer again …

      I am not exactly sure if I get what you mean. Let’s see… If you change any of the settings in the FOG web UI while the fog-client is running on the computer the changes won’t be sent out to the client immediately. This is something I hope to change in the future but that’s how it is right now. But if you change things and then reboot the client machine it should use the changed settings!

      -) Group management with Printers: If I update a group with the option “only Assigned Printers” the clients are not updated. The are still in the mode “No Printer Management”

      This is a known issue I just fixed a couple of days ago. It will be in the next release!

      -) How to install a local pdf Printer, when I use the option: “Only Assigned Printers”

      Find out the settings used in the PDF printer (using the fog-client PrinterManagerHelper.exe or manually from the printer properties…) and set it up in FOG as well?! Should work I suppose.

    • K

      Deployment stops/waits very long with: Reattempting to update database ....

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      30
      0 Votes
      30 Posts
      11k Views
      S

      @kratkale Read through this topic, possibly you have many client’s talking to the FOG server (and the DB for that reason) which might cap the connections.

      About the printers, I might ask you to open new topics so we don’t loose track of different issues in one thread.

    • K

      Upgrade to 1.5.4 from .... (captured: invalid date) Debian 9.5; Client Lenovo M910 (i5 SSD)

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      2
      0 Votes
      2 Posts
      750 Views
      K

      Problem 1 “update” solved:
      I’ve installed FOG again - now it works 😉

      Problem 2 still unsolved.

    • 1 / 1