• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. JYost
    3. Topics
    • Profile
    • Following 1
    • Followers 0
    • Topics 29
    • Posts 70
    • Groups 0

    Topics

    • JYostJ

      FOG Client unable to rename or join domain on some laptops

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      4
      0 Votes
      4 Posts
      837 Views
      S

      @JYost Oh well, I was too quick looking at this without noticing the first part of it being really old. Next try:

      6/5/2020 2:42:30 PM HostnameChanger Checking Hostname 6/5/2020 2:42:30 PM HostnameChanger Renaming host to HE-L002107 6/5/2020 2:42:30 PM HostnameChanger Joining domain 6/5/2020 2:42:35 PM HostnameChanger Success, code = 0 6/5/2020 2:42:35 PM Power Creating shutdown command in 60 seconds

      Looks pretty good to me so far. And from then on the rest of the log shows:

      6/5/2020 2:46:22 PM HostnameChanger Checking Hostname 6/5/2020 2:46:22 PM HostnameChanger Hostname is correct 6/5/2020 2:46:22 PM HostnameChanger Attempting to join domain 6/5/2020 2:46:22 PM HostnameChanger Host already joined to target domain

      So I can only guess on what you mean by “not entirely sure what the error messages should be telling me”. Guess you mean these log entries:

      6/5/2020 2:38 PM Client-Info Version: 0.11.15 6/5/2020 2:38 PM Client-Info OS: Windows 6/5/2020 2:38 PM Middleware::Authentication Waiting for authentication timeout to pass 6/5/2020 2:40 PM Middleware::Communication Download: http://10.6.190.155/fog/management/other/ssl/srvpublic.crt 6/5/2020 2:40 PM Data::RSA FOG Server CA cert found 6/5/2020 2:40 PM Data::RSA ERROR: Certificate validation failed 6/5/2020 2:40 PM Data::RSA ERROR: Trust chain did not complete to the known authority anchor. Errors: The signature of the certificate cannot be verified. (NotSignatureValid) 6/5/2020 2:40 PM Middleware::Authentication ERROR: Could not authenticate 6/5/2020 2:40 PM Middleware::Authentication ERROR: Certificate is not from FOG CA

      The fog-client installed on this machine was pinned to a FOG server different to the one it is talking to right now. I suppose you switched your certificates or FOG server some time between installing this fog-client (0.11.15) and letting it talk to it now. Good news is that the fog-client figured there is an update (version 0.11.19 in the logs from then on), installed that and re-pinned to the current FOG server which essentially fixed the problem.

      which brings to mind another question…why are there still fog.log entries from back in March and then appended with the log entries from Friday?

      This means the fog-client on this machine (or your master??) has been running in March or the date/time of this machine was way off.

    • JYostJ

      Change to HOSTS section

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      2
      0 Votes
      2 Posts
      777 Views
      S

      @JYost What you see when you first click hosts is the search view. Typing in the menu bar search field you should see results below.

      To change this you go to FOG Configuration -> FOG Settings -> FOG View Settings and change setting VIEW DEFAULT SCREEN from SEARCH to LIST. Don’t forget to click Update to save the change.

    • JYostJ

      Odd behavior when adding hosts - FOG 1.5.8

      Watching Ignoring Scheduled Pinned Locked Moved Solved Bug Reports
      3
      0 Votes
      3 Posts
      1k Views
      S

      @JYost Yeah, truly a bug. Fixed in latest dev-branch. Change will be in the next release.

    • JYostJ

      Fog Host Management Screen - Creating new hosts issue

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      3
      0 Votes
      3 Posts
      1k Views
      JYostJ

      @JYost
      Thank you George…this pointed me to the etc/network/interfaces file where I found that the dns-search field only had “domain.local” and was missing “domain.com”. Once I added that into the dns-search field all was good and FOG was able to see devices which were online (denoted by green Windows icon).
      Thanks again guys…great support as always!!!
      Go ahead and mark this as solved.

    • JYostJ

      Need a list of FOG Client uninstall GUIDS

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      2
      0 Votes
      2 Posts
      604 Views
      S

      @JYost As far as I know the inner workings of the fog-client installer I don’t hink you actually need to uninstall older versions first. Just install 0.11.19 and it will take care of an older version if it is installed - remove it and install the newer version.

    • JYostJ

      Fog 1.5.5 to 1.5.8 - Creating SSL Certificate - FAILED

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      19
      0 Votes
      19 Posts
      4k Views
      S

      @JYost The images themselves have not much to do with the fog-client software. It just does the host management (reboot on imaging tasks, domain join and so on).

      But I do understand your question! Between 1.5.0 and 1.5.8 there were many changes in FOG and FOS (FOG Linux OS) which does all the actual work when imaging. We moved to newer versions with many tools in FOS, especially also partclone. But as far as our testing shows you should be able to use your old images without any change. Give it a try, just do a deployment to one of your hosts and see if it works. It should.

    • JYostJ

      Remotely imaging a laptop using FOG

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      5
      0 Votes
      5 Posts
      2k Views
      george1421G

      @JYost said in Remotely imaging a laptop using FOG:

      Now that I’m looking at it I see exactly what you mean about going in and pre-creating the HOST.

      This is referred to as manually registering the host. The only bit of information that may be problematic is the target computer’s MAC address. If you have the mac address then you an just go into the web ui and add a new host and enter its name, image, mac address via the web ui. You won’t get the full inventory right away, but there will be enough information to pxe boot the target computer. If the fog client is already running on the target computer, when you create a deploy task the target computer will reboot, or power on if WOL is enabled on the target computer. But to do this, the target computer needs to be configured to boot through PXE to the FOG menu every time. If there is nothing to do the target computer will continue on booting from the local hard drive.

      ALSO, if the fog client is installed on the target computer BUT the target computer is not registered in FOG the target computer will be added to the FOG server in the pending state. You will need to approve the target computer to have it added to the inventory. You will still need to set the image name but you should have a near hands off registration.

    • JYostJ

      Import / Export Images across network to other fog servers on network via GUI

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      4
      0 Votes
      4 Posts
      1k Views
      JYostJ

      Excellent George, I will give that a try. Thanks for the feedback!

    • JYostJ

      Please add ability to renumber images via the GUI

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      7
      0 Votes
      7 Posts
      2k Views
      Tom ElliottT

      @JDnoble18 download it to the fog server. Run it. That’s it.

      How you run is up to you. But I’d say do sh ./renumberImageIDs.sh once it’s on the fog server.

    • 1 / 1