AD Integration on new FOG 1.1.2



  • Hi All,

    I have just upgraded from .32 to 1.0.1 to 1.1.1 and now 1.1.2 without many issues. However, I have noticed a change in the new version which is causing us some problems.

    On the old version, you set up a base OU in the options (e.g. ROOMS) then if you wanted to add a particular host or group to a sub-OU of that, you were allowed to type it in in the field. Now it is just a drop-down, you aren’t allowed to type it at all.

    Is this the proper action, or is my install playing up?
    If this is usual, are there any plans to alter this action back it its previous more useful method?
    As a work around, is there anywhere to enter a list of OU’s which will be selectable from the new drop-down?


  • Developer

    this is normal. that is the svn revision number, and technically you are no longer running the latest official version of fog. you are running a developer’s pre-release version.


  • Developer

    [quote=“fre2709, post: 33240, member: 24947”]Thanks X23,

    i had already discovered this on another forum entry.

    One thing to note, and I dont know if this normal. After applying the SVN the version number in the “FOG cloud” symbol changes. Mine now says 2052. This breaks the latest version reporter because it now says my version is out of dat and I need to install 1.1.2!![/quote]

    This is okay, the SVN is considered “bleeding edge” it’s where all the new fixes are worked on, you can consider it an “active beta” for a lack of better way to describe it.

    FOG Is set up so that it will check to see what the latest reported version is so it can determine if there is an upgrade for you, however, it doesn’t have the ability to distinguish being “up-to-date” and being on the “bleeding edge”. So this error is only a minor cosmetic detail. When we make a major revision and update to FOG 1.1.3 or 1.2.0, then changes will be made to look for that version.

    [B];TLDR SVN versions will always report this, but it is not an error so long as you did in fact install the SVN and not the current supported version.[/B]

    If you don’t need the fixes that have been added to the SVN, you don’t have to use it, you can use the latest stable version if you would like.



  • Thanks X23,

    i had already discovered this on another forum entry.

    One thing to note, and I dont know if this normal. After applying the SVN the version number in the “FOG cloud” symbol changes. Mine now says 2052. This breaks the latest version reporter because it now says my version is out of dat and I need to install 1.1.2!!



  • Hi,

    to use latest svn trunk open a shell:

    Install Subversion:
    [CODE]sudo apt-get install subversion[/CODE]
    Checkout SVN:
    [CODE]svn co https://svn.code.sf.net/p/freeghost/code/trunk/ /opt/trunk[/CODE]
    Install latest FOG Development Version:
    [CODE]opt/trunk/bin/installfog.sh[/CODE]
    Update to latest SVN Version:
    [CODE]cd /opt/trunk
    svn update[/CODE]

    Regards X23



  • Thanks Tom and thanks to the FOG team for providing this software,

    applying the SVN seems to have fixed it. Being a Linux newbie though had to search for instructions on how to install SVN’s.

    The installfog.sh script for the last few version updates including the SVN is automatically adding a root password to the config.class.php file though. Had to remove the password to allow the schema updater to work. Even if I remove it from the .fogsettings file it still seems to appear in the config.class.php

    Sorry I forgot to add the basics to my enquiry - new to the forum too. We are using Ubuntu 12.04LTS on a HP ML350G5 server box.

    I did search for a solution but nothing relevant came back so maybe I was using the wrong keywords…



  • For future use maybe a LDAP/AD browser to allow selecting the OU where the computer will end up would be useful.


  • Senior Developer

    There has been a “fix” for this in SVN. The intent of that field was if there’s only one or no entries, the field is text. Otherwise you can use the FOG Settings Active Directory settings field to specify multiple OU’s and make “selecting” of those OU’s dynamic.

    The “fix” in SVN is simply to test the count of the parameters. If 0 it’s a text field. If only one entry it’s a text field. If more than one, it’s a dropdown box. Hopefully that will help.



  • I’ll add that this was a great feature in the previous version, and am having issues due to this change.


Log in to reply
 

445
Online

39174
Users

10821
Topics

102951
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.