• "No valid data" shows when special character / is used in image name

    Moved
    4
    0 Votes
    4 Posts
    1k Views
    Wayne WorkmanW

    @juan-bertolotti Are you able to delete the image?

  • 0 Votes
    4 Posts
    1k Views
    Wayne WorkmanW

    @robertd Checkout the below image, this is how you password-protect the entire fog menu. This will accomplish what you’re after. Technicians need only to enter the key-combination in order to be prompted for user/pass credentials. The accepted credentials are those in the FOG web interface users area.

    0_1503530821572_hide menu password.png

  • FOG Client reboot/shutdown timer custom value

    Solved
    6
    0 Votes
    6 Posts
    2k Views
    Tom ElliottT

    You didn’t do anything wrong sir. I didn’t fully understand the question and mistook the request.

  • Single disk (resizeable) 1 partition restore

    3
    0 Votes
    3 Posts
    1k Views
    S

    @fractal13 said in Single disk (resizeable) 1 partition restore:

    each image overwrote the MBR, GPT partition types, and partition UUIDs.

    Even if you set it to one single partition in the image settings before deploy? Shouldn’t do so I suppose.

  • Group > Printer > Add And Remove

    1
    0 Votes
    1 Posts
    734 Views
    No one has replied
  • More granular user control

    Solved
    2
    0 Votes
    2 Posts
    1k Views
    THEMCVT

    And I just found the Access Control plugin- I think this is what I’m looking for.

  • Change color for not enabled snapins

    Solved
    6
    0 Votes
    6 Posts
    2k Views
    Matthieu JacquartM

    @tom-elliott Yes, I just test it on RC5, perfect 😉

  • Deploy Single Snapin Shows All Snapins, Not Those Assigned to Host

    Moved Solved
    15
    0 Votes
    15 Posts
    4k Views
    Tom ElliottT

    It should look like:

    0_1501183211866_164a7593-af02-4c13-9471-599068c5051c-image.png

  • Display Host Name Throughout Host Management

    Solved
    6
    2 Votes
    6 Posts
    2k Views
    Tom ElliottT

    Added in working.

  • Using Host Tags as Variables in Snap-Ins

    7
    1 Votes
    7 Posts
    3k Views
    J

    @sourceminer said in Using Host Tags as Variables in Snap-Ins:

    use the host Tags as variables

    +1for use the host Tags as variables

  • Host Printer List Refresh On Update

    7
    0 Votes
    7 Posts
    2k Views
    J

    @Tom-Elliott

    No problem. Yes it does prompt to update. Thanks!!

  • FOG 1.5.0 RC2 Host Landed Page

    Solved
    3
    0 Votes
    3 Posts
    944 Views
    J

    @Tom-Elliott

    It’s funny, I noticed it a bit later after I posted this. 🙂 It’s looking good though!

  • Fog Client Aware of Image Queue Depth

    12
    0 Votes
    12 Posts
    4k Views
    AngryScientistA

    That’s very promising to hear Wayne! I must admit that you shot beyond my skill set with your bash script and use of the API. I look forward to your “generic” solution!

  • "Start/Checked in" and/or "Completed" columns in Snapin Log

    Solved
    3
    0 Votes
    3 Posts
    1k Views
    T

    @Tom-Elliott Thanks for your hard work - good to know it will be there in a future release.

  • Kernel 4.11.6 UEFI VARS and efibootmgr

    Moved Solved
    8
    2 Votes
    8 Posts
    3k Views
    Tom ElliottT

    I’ve updated the current 4.11.6 kernels to include both the vars and the boot editing elements.

    Hopefully this helps.

  • 0 Votes
    3 Posts
    934 Views
    F

    @Tom-Elliott I didn’t realise it was as easy as that - will give it a whirl next time we get a new batch of computers.

    Thanks

  • Recycled / Disposed Computers

    2
    0 Votes
    2 Posts
    894 Views
    Tom ElliottT

    You could write a plugin that could do this for you. Something like an “archive” plugin that moves hosts out of the “main” element and into your “new” element.

    I realize writing a plugin can be hard, but I don’t think this is something that should be a part of the “core” of fog.

  • Start Date/Time on Tasks

    Unsolved
    2
    1 Votes
    2 Posts
    931 Views
    Wayne WorkmanW

    @LPetelik Great idea, I think this would be very useful.

  • Active Directory OU aliases

    5
    0 Votes
    5 Posts
    3k Views
    george1421G

    @moses If you look at this post: https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/6

    You’ll see how to identify the location by it IP address of where the FOS image is running.

    myip=`ip route get 8.8.8.8 | awk 'NR==1 {print $NF}' | cut -d "." -f1-2`; case "${myip}" in 10.1) sitecode="NYC"; timezone="Eastern Standard Time"; oupath="ou=computers,ou=nyc,dc=domain,dc=com"; ;; 10.2) sitecode="LA"; timezone="Western Standard Time"; oupath="ou=computers,ou=la,dc=domain,dc=com"; ;; *) # Default code for the unknowns sitecode="CORP"; timezone="Eastern Standard Time"; oupath="ou=computers,ou=corp,dc=domain,dc=com"; ;; esac

    If you couple that with this post:
    https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/7 you can see how I use sed to modify the unattend.xml script

    # Unattend.xml path (note the case specifics in the file name and path) unattendfile="/ntfs/Windows/Panther/unattend.xml"; sed -i -e "s#<MachineObjectOU>\([^<][^<]*\)</MachineObjectOU>#<MachineObjectOU>${oupath}</MachineObjectOU>#gi" $unattendfile

    If someone wanted to merge all of the bits together from that tutorial into a script it might look like this.

    #!/bin/bash . /usr/share/fog/lib/funcs.sh # windows 7 osdiskpart="/dev/sda2"; # create a directory to hang the Windows C: drive partition on in FOS # the 2>/dev/null below just redirects any errors from the mkdir command to null. i.e. # if the directory already exists, I don't want to know about it, just hide the error. Understand # that I could have tested if the directory already existed, but that takes more programming steps # I'm just going to try to create it and ignore the error if it already exists. mkdir /ntfs 2>/dev/null # This next command connects the hard drive partition to the directory we just created. You will see the # 2>/tmp/mntfail at the end of the mount command. In this case if the connection fails we want to write # the output to a text file we can review and test to see if it exists. If the file exists then something went # wrong with the connection to the hard disk partition. mount.ntfs-3g "${osdiskpart}" /ntfs 2>/tmp/mntfail # this last bit of magic checks to see if the mntfail file exists and if it does then it means the mount # failed so there is no need to continue on with the script. mntRet="$?"; if [ ! "$mntRet" = "0" ]; then echo "Failed to mount C:"; # display what happened cat /tmp/mntfail; # give the reader a chance to see what the error was sleep 12; # terminate the post install script exit 1; fi # Unattend.xml path (note the case specifics in the file name and path) unattendfile="/ntfs/Windows/Panther/unattend.xml"; chassis=`dmidecode -s chassis-type`; chassis="${chassis%"${chassis##*[![:space:]]}"}"; #Remove training space chassis="${chassis,,}"; # Convert string to lower if [ "$chassis" = "laptop" ]; then chtype="Portable"; elif [ "$chassis" = "tablet" ]; then chtype="Tablet"; else # We'll default every other chassis type to desktop chtype="Desktop"; fi # you may need to replace the host 8.8.8.8 with a valid target address if you have a closed network myip=`ip route get 8.8.8.8 | awk 'NR==1 {print $NF}' | cut -d "." -f1-2`; case "${myip}" in 10.1) sitecode="NYC"; timezone="Eastern Standard Time"; oupath="ou=computers,ou=nyc,dc=domain,dc=com"; ;; 10.2) sitecode="LA"; timezone="Western Standard Time"; oupath="ou=computers,ou=la,dc=domain,dc=com"; ;; *) # Default code for the unknowns sitecode="CORP"; timezone="Eastern Standard Time"; oupath="ou=computers,ou=corp,dc=domain,dc=com"; ;; esac sed -i -e "s#<ComputerName>\([^<][^<]*\)</ComputerName>#<ComputerName>$hostname</ComputerName>#gi" $unatendfile sed -i -e "s#<TimeZone>\([^<][^<]*\)</TimeZone>#<TimeZone>$timezone</TimeZone>#gi" $unattendfile sed -i -e "s#<MachineObjectOU>\([^<][^<]*\)</MachineObjectOU>#<MachineObjectOU>${oupath}</MachineObjectOU>#gi" $unattendfile

    Understand these are just snippets of code that are stuck together in some kind of logical order. The above hasn’t been tested. There are also some assumptions in this script as to the partition layout for win7. There are other scripts in other of my tutorials that does a better job of actually finding the ‘C:’ drive on the target computer. In the snippet above the fog client isn’t used to name the computer or connect it to the domain. The unattend.xml file is use for that. So you need to have the other bits in the unattend.xml file so the target is capable of doing what it needs. Like having a user account defined that is allowed to add computers to the domain and such.

  • Help with translation messages.po

    Moved Unsolved
    2
    1 Votes
    2 Posts
    924 Views
    Wayne WorkmanW

    Moved this to feature requests and marked as unsolved.

196

Online

12.3k

Users

17.4k

Topics

155.9k

Posts