Best posts made by Tom Elliott

If I had to guess, your Dell machine is set to see your Drives in “RAID” mode.

You should be able to change the Sata operation mode from RAID to AHCI, which then FOG should be able to see the disks.

https://news.fogproject.org/fog-1-4-0-rc-6/

For benchmark/testing.

Using Joe’s server as the testbed, it was taking about 42 seconds to load the group membership page and around 30 seconds for the tasking page.

It now takes 3 seconds to load, and 5 (total) to render on membership. Tasking is relatively instant.

https://news.fogproject.org/simplified-api-documentation/

This is based off the information provided here:
https://forums.fogproject.org/topic/10036/api/2#

@rmurra81 I don’t if you’re trying to crack at me or not. I’m siding that you aren’t and you’re suggesting by this being in “feature” requests you think I’m “wasting effort” to make this thing a feature.

As we have it, this is not really the case. A feature request does not necessarily mean it will be something I will be adding. This thread was opened in 2015 so I’m not sure what the “hope” for resurfacing this was. I understand what’s being requested, but it’s likely not something I’m going to put much effort into, considering I really want to focus my efforts toward FOG 2.0.

And this for dashboard:

I’ve been working to move this into a “bootstrap” type system.

My basic works are right now off:
https://github.com/creativetimofficial/light-bootstrap-dashboard

As I work, I’ll end up making the code more my own, just this is how I’m basing the work currently.

It is in GPT, regardless of what windows is telling you. When the initial install was on the system, it was most likely formatted using GPT for the partition layout. Windows is, well, kind of dumb in how it shows you data. It will say “MBR” but in reality, the system IS in MBR, but the GPT segments have not been properly removed.

Start the upload task as a Debug task. When at the prompt, run: fixparts /dev/sda and Confirm and write the data. Then run the command fog and press enter through all the stops. The upload should happen properly and your disk is now properly setup for MBR.

https://news.fogproject.org/fog-1-4-3-officially-released/

@Arrowhead-IT To add on, if you don’t mind.

Particularly pertaining to the different hashes, this is intentional.

The intent is to make it that much harder for somebody to see/guess your password. The FOG System in whole does the encryption/decryption when and as needed.

For even more security, with the new client at least, any time a client checks in the hash changes too. This is to further obfuscate possibly breach of your AD Password.

https://news.fogproject.org/fog-1-5-0-rc-6/

Linux is not windows. Change this hosts kernel device to either blank or the real device in linux.

https://news.fogproject.org/fog-1-5-0-rc-8/

size on server was a default in 1.2.0, but it was also a performance hog. You can still have this if you would like it, but you must enable it through the FOG COnfiguration -> Fog settings element.

The apache may fail simply because the webroot is trying to default to /var/www. Try running the installer with:

./installfog.sh --webroot /var/www/html/

https://news.fogproject.org/fog-1-5-0-rc-9/

@ManofValor the settings look fine. This is particularly why I love teamviewer though. I can’t find an error on my side namely because. I don’t have a uefi system to work with. I’m pretty certain I’ve screwed up somewhere but I haven’t a clue what or where .

https://news.fogproject.org/fog-1-5-6-officially-released/

Update hint:
An issue was found in 1.5.6 that calls for an early next release to fix that. Find the details here if you run into problems with FTP connections on kernel updates or storage nodes in 1.5.6: https://github.com/FOGProject/fogproject/issues/311

Hello all,

Just wanted to state that I’ve made a slight feature adjustment/improvement to the LDAP plugin.

You can now decide to use an AD displayName field for the environment.

Hopefully this makes sense and makes things a little nicer. It does mean to see the changes and make changes, you will have to remove and re-add the plugin. This isn’t overly difficult, just try to remember to get your configuration before hand.

Just an example:

And for creating the new LDAP item:

SVN 3633 released.

I know it’s been a while since I last updated this area, but you all are likely aware of most of the changes.

This release, and for the last few revisions, I’ve been making strides in commonizing the functions for the installer.

If you haven’t been paying much attention, I’ve added a few features to this installer.

You can now use your own config file rather than only with the /opt/fog/.fogsettings. It will default back to this file.

The Options listing:

Usage: ./installfog.sh -[hdUuHSCKY] -[f <filename>]
        -h -? --help                    Display this info
        -d    --no-defaults             Don't guess defaults
        -U    --no-upgrade              Don't attempt to upgrade
        -H    --no-htmldoc              No htmldoc, means no PDFs
        -S    --force-https             Force HTTPS redirect
        -C    --recreate-CA             Recreate the CA Keys
        -K    --recreate-keys           Recreate the SSL Keys
        -Y -y --autoaccept              Auto accept defaults and install
        -f    --file                    Use different update file
              --uninstall               Uninstall FOG

The uninstall option does not work yet, though there is some work towards starting it, it does not do anything directly yet.

The autoaccept option does operate. It should even operate for installs, though if it can’t find the proper defaults, it will ask for information.

The force-https has been added for quite some time. It basically will make your access to the fogserver point to https: rather than just giving you http.

The recreate-CA option creates the Certificate Authority. This is what’s installed with the new client install that enables the Client to know it can trust the FOG Server.

The recreate-keys item just recreates your private key if you should need it.

The file option requires a file if you’re going to use it. This is where you can use a different update file, or specify one if you’re fresh installing, but don’t want to retype all the values.

Hopefully this helps you all.

Logging is redirected but no more from a hidden file. It still happens as it did before, but it’s smarter I think.

To everybody responding to this thread. @jguest systems are loading in UEFI/EFI and appears, from what he can tell, to only allow EFI. This means, no amount of .{,k,kk,}pxe will work at all.

We made small progress with using the snp.efi file.

I didn’t describe configuration because it’s not a simple thing to try to explain using a cell phone. When I get home I’ll try to describe more. You can also call out for @Lee-rowlett to see if he can spur in a few dimes.