@george1421 Can confirm that this is the fix. Recently just deployed 650 EliteDesk 800 G2 SFF’s and upgrading to trunk (using the newer kernel) fixed it.
Best posts made by RLane
RE: Groups can no longer hold more than one member (Trunk 7825)
Here was another thread that contained the same issue:
I believe it was fixed in the latest revision update. @Tom-Elliott can correct me if I’m wrong.
Ideal FOG Setup
So I’ve been a member here for a long time and been using FOG since 0.32. I love it, love the community and environment. I also appreciate all of the work and effort that the dev’s put into it.
I’ve noticed one of the key organizations that use FOG are those of you in the educational sector. As a network admin, I’m responsible for the imaging of machines over the summer. I do this every year to keep everything fresh and up to date, along with making changes that the teachers request in labs.
Now that summer is approaching (students have a day left here) – what is the ideal setup for FOG?
I’m running 1.2.0 right now - Ubuntu 14.04
I am not using any trunk releases
After reading about the trunk speeds being so much quicker for gig server and gig client imaging, I’m convinced I should upgrade
The client seems promising and should be available soon – another reason I’m convinced I should upgrade
Obviously Tom already said that the next stable release will be soon, however, should I rebuild my FOG server (export users, client, etc.) and rebuild it fresh and use the trunk builds?
Should I wait until later in the summer for an upcoming stable reason?
I’m curious to see what everyone thinks.
RE: Automated Deployment
Welp, I’m sorry for bugging everybody. After working on this all day and night, I found that the wrong unattend file was being used… with a restart set to hit 25 seconds after the first user logs in.
On a happy note, my Win10 deployment is finalized, so thanks all for that.