@NT_Tech Access control is a plugin now which has much more use than the “mobile” vs “non-mobile” account.
FOG was indeed a single user system, from it’s original startup. The only thing that kind of made things different was the mobile interface.
I want you to understand, mobile interface was it’s OWN element from the main interface. This meant having to update two GUI platforms to ensure all functionality was maintained. When moved to a single interface that could do both mobile and full screen usages, I removed the “mobile only” user type.
I want to stress, while it wasn’t necessarily intuitive, even in 0.32 a “mobile only” user had exactly the same level of usage as the full admin users. The GUI access was limited and didn’t allow a mobile only user to see anything, but a mobile user could delete items, change things, etc… if they knew the url pathing and calls. They couldn’t see it, but it was not “limited” in the way you thought it was. As the access control plugin was created and managing a single interface made updating and keeping things in a more testable and common way, I decided to remove the “mobile only” option. This was not intended to hurt people who were using the element, but rather there were better things in place that did far better at controlling the scope of things and in a more granular and appropriate fashion.
I dumped the database as a backup and used PHPMyAdmin to delete the first 1000 entries in the imaginglog table.
It all works now! There was obviously a bad record somewhere in there that was breaking the report.
As a side note, the imaging log issue was arrarently fixed. When I change the definition on a host is DOES NOT change the record of what was previously imaged…as it should be.
All this talk about joining to specific OUs is kinda gross… (Just my opinion).
If you don’t want your computer objects to be joined and placed inside the default “computers” OU, you can just change the default…
I’ve got a nested OU inside my primary OU, it’s called “DEFAULT”. Everything new / renamed that gets joined shows up in there. This way, even if we forget to move the computer where it should go (like “Lab xxxx”, “Conference Room”, etc). The machine will at least get all the policy that we have applied to every machine in the building, and will also grab the right policy on reboot after domain joining.
It’s super spiffy and it lets me totally avoid all this Specific OU joining stuff.
You’d have to build a new kernel for this support.
I removed all USB HDD potentials, as what was happening more often than not was FOG was imaging the external drives when that was NOT the intended drive. Because of this, I removed USB HDD’s from the kernel.