• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Almost there. A couple of gotchas that I found when installing 1.2.0 (trunk to follow)

    Scheduled Pinned Locked Moved
    General
    2
    2
    606
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      KKTwenty101
      last edited by

      I used CENTOS 6.7 in a hyper-v host.

      • Don’t forget to disable SELinux
      • Domain 2202 errors (for me) was due to me upgrading from 0.32 - the domain password was correct but the username drops the DOMAIN portion of DOMAIN\USERNAME so basically drop the domain\ part
      • Whilst the above is CORRECT for fixing 2202 errors what I didn’t do was update each host. It isn’t enough to simply change the master AD credentials - they will only affect NEW registrations. The existing registrations have one per host. We have 278 hosts and our apprentice wasn’t relishing the prospect of going into each one. What I did instead was save a configuration file, edit the SQL and copy the – Table structure for table hosts' and -- Dumping data for table hosts` into a new text (.SQL) file, I did a search and replace on my DOMAIN\ then reimported the SQL from command prompt (thus dropping and recreating the hosts with new AD information). Low and behold no more 2202 errors!
      • Blank drives with no partition table barf partclone in 1.2.0 (apparently fixed in trunk). I created a dirty fix that DD the first 512 of the drive then added a simple label using parted partlabel. This fixed partclone for me.
      • Multicast didn’t work for me until I truncated the two multicast tables (this is in the wiki).

      Overall though 1.2.0 works just fine for me. Now to get trunk running…

      1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott
        last edited by

        You could also just put all hosts into a group, and update the ad information that way.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post

        197

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project