OKAY…I “kind of” solved my issue. If you go into the database and change the uType on an account from 0 to 1, then that user cannot delete anything. I was more concerned about that than anything else. I had hoped a type 2 could image and not access the GUI (mobile user) but then the user cannot image at all. But I am 1/2 way there.

Maybe the Access Control will be fixed for 1.54 and I can try it again. I am beginning to regret updating past 1.3…but the past is the past.

Brian

Re: Access Control Plugin

Does anyone have this working? I have it installed but it doesn’t appear to actually add users to the roles and work.

I would love this functionality for my intern and my student accounts.

Brian

@Junkhacker I am using PHPMyAdmin on FOG 1.54 (Ubuntu 16.04 Server) and if I make a user manually the PXE Boot does not allow me to use it to image. I keep getting Invalid Logon.

@Junkhacker I really miss the mobile interface! I used to use it whenever I had an issue around the district. I would not have upgraded had I known I was going to loose features…but I am there now. How do I manually add a user into the database? PHPMyAdmin?

@Sebastian-Roth I certainly would be willing to help with questions where I can. I have used FOG since .32 and love it. My students use it as well but someone recently deleted an image and I need to restrict their access so I don’t have to rebuild it again!

Brian

Well that would certainly work. How would I enter a user directly into the database?

I did try the AccessControl Plugin, which would work by simply taking away all items from the “imager” role, but it doesn’t seem to be working.

It is REALLY important that we return to having some level of access control in FOG. In the early versions we could specify whether someone was a full or imaging only user. For years I have been able to let my student helpers reimage laptops whenever there was an issue with our 1:1 student laptops. Now, if I give them an account, they can do anything that I can do, including deleting images, making new users…

FOG is not a single user system. We need to get back to at least an account that only allows deploying images from the PXE boot if nothing else.

PLEASE re-add this functionality!

Brian

@reese I am having the same issue. How did you safely downgrade back to 1.4.4. I had no issues there but can’t image an entire lab anymore. Just locks up. Hints on the downgrade process would be appreciated!

@tom-elliott Tom, I am open to any distro. While I have always used Ubuntu with FOG, I would like to know what you are programming and testing on, so I can use the same distro. Just makes sense since I am building a new server anyway.

So…what are you using?

Brian

I has a similar issue when we had sent to about 30 machines. While it shouldn’t make a difference as we only let 10 image concurrently, it did. When I edited the php.ini file in /etc/php/7.1/apache2 and changed the memory_limit from 128M to 256M, it worked as soon as I rebooted.

I am on Ubuntu 16.04 LTS and FOG 1.5.4