FOG client on Mac OS X

[Joe Schmitt]

@Louis-CSUSA Be sure to stop the service via the launchctl unload command I provided. The “Invalid security token” message can be fixed by a simple “Reset Encryption Settings” on the host via the fog web portal. What’s more concerning is that the service did not auto start itself on boot. Are you absolutely positive you restarted the machine after installing? Linux is the only OS capable (as of right now) of doing a complete service start without a reboot.

[Louis CSUSA]

@Jbob The FOG log is starting to look normal now (like on the PC side). I was able to remove the “invalid security token” by hitting the Reset Encryption Settings as you suggested. Before that though, we did stop the service via launchtrl unload and rebooted again (for safe measure). I’ve attached our latest FOG log.

When we installed the service the first time, we did perform a reboot right after.

0_1463084556540_foglog2.log

[Joe Schmitt]

@Louis-CSUSA So after the newest reboot the client automatically started itself? Also, note to self: ignore the wtmp user in user tracker in the next release.

[Louis CSUSA]

@Jbob Hey JBob, after the reboot it did not start on it’s own. We had to manually load it using the same command.

As an aside, HostNameChanger said that users are still logged in, and enforce is disabled. Is that a setting on the OSX side that we need to change?

[Joe Schmitt]

The fact that you had to manually start it is a problem. Pinging @Tom-S for this conversation (I’ll be busy for the next several hours). As for the “Users are still logged in”, that is a checkbox in the web portal under a host/group

Specifically the “Host changes every cycle”. If disabled, it will wait for users to log off first. @Tom-Elliott perhaps we could name it something like “Wait until users are logged off” and invert it, or have some (?) hover next ot it?

[Louis CSUSA]

@Jbob Since this is our first time doing this, we can reimage this unit again and start from scratch tomorrow. I want to make sure that user-error (on our side) isn’t giving you bad data. We will report back more tomorrow.

Thank you very much @Jbob!

[Joe Schmitt]

@Louis-CSUSA not a problem. I’ll have limited availability tomorrow as well. I’ll try and replicate the issue on the single Mac I have to test with (one of the difficulties of developing an OS X client ).

[Wayne Workman]

@Jbob said in FOG client on Mac OS X:

perhaps we could name it something like “Wait until users are logged off” and invert it, or have some (?) hover next ot it?

I like that idea.

[Tom S]

Well this is indeed a bit odd. If running the launchctl commands start and stop the service, the service should start on its own based on your plist. Essentially this is what happens when the mac boots and hands off the thread to launchd. So hmmmmm. Permissions??? Perhaps!!

Please run:

ls -la /Library/LaunchDaemons/org.freeghost.daemon.plist

and

ls -la /opt/fog-service

This will verify permissions.

Also, in security under System Preferences, try allowing apps from anywhere. This is obviously not a fix but certainly could help resolve a possible issue.

Please post your results

Thanks,
-T

[Wayne Workman]

@Louis-CSUSA I forked your posts to here: https://forums.fogproject.org/topic/7561/network-booting-a-mac

Please post in there.