Best posts made by Tom Elliott
-
RE: FOG Server CPU usage 100%
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.
-
Static Documentation for API
https://news.fogproject.org/simplified-api-documentation/
This is based off the information provided here:
https://forums.fogproject.org/topic/10036/api/2# -
RE: Do windows update on uploded image stored on fog server
@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.
-
RE: Thoughts and ideas
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-dashboardAs I work, I’ll end up making the code more my own, just this is how I’m basing the work currently.
-
RE: Windows 7 GPT error whin imaging up, but it's not GPT!
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 commandfog
and press enter through all the stops. The upload should happen properly and your disk is now properly setup for MBR. -
RE: Active directory Join issue
@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.
-
RE: "Error is 2" problem opening c:/
Linux is not windows. Change this hosts kernel device to either blank or the real device in linux.
-
RE: FOG Git Installation on Ubuntu 14.04
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/
-
RE: PXE image looping
@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 .
-
FOG 1.5.6 Officially Released
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 -
FOG LDAP Plugin 1.6
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:
-
RE: Latest Development FOG
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.
-
RE: Fog on existing network, clients wont boot.
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.
-
RE: Access control plugin in Git 5572 add page not displayed
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.
-
PHP 7.0.0 finally Released
Hey all,
Normally I make a proper news article to post in the announcement but I don’t think we should go that route for this particular bit of news.
I’ve already tested FOG Trunk with PHP 7.0.0 RC8 and fixed the code base to be as operational as possible. Even better, due to all the other edits from about a year ago, I already had a good starting point. For example, not using mysql functions and what not. All I had to change was removing one line of code and all of a sudden everything starting working perfectly with it.
I will say, PHP 7 is MUCH more memory efficient and a LOT faster. For example, on PHP 5.6.16 the dashboard page on a server that only had FOG installed on it would come in around 9M. Same principle with PHP 7.0 installed, the same page used 2M of memory. This means quite a lot. I also played with injected hosts and had 4k hosts. 5.6.16 would take about 6 - 7 seconds to start returning the page and about 16 - 18 seconds to fully render the page. With PHP 7.0 the same amount of hosts on the same system returns in about 3 seconds, and fully renders in about 12. While the timing for amount of data doesn’t seem all that significant the memory usage is MUCH better. 5.6.16 would come in around 168M, 7.0 Comes in at about 130M.
I know this is nothing but gibberish, but believe me, if you can update, I would HIGHLY recommend it. One it would be nice to know of any problems I might have in the code, and two it would definitely help out those of you who have MANY MANY hosts in your setup.