Can I Implement Sign in MacApp

Can I Implement Sign in MacApp

hey everyone good afternoon we're in the final stretch but we have another awesome presentation to kick off and then stay tuned right afterwards um after he's done with questions I'm gonna go ahead and give you some info about going to the party tonight but without further ado let me introduce Nathaniel Strauss from Shakopee public schools gonna talk all about using nomad loggin with jams pro and turn it over to you Nathaniel thanks thanks for coming everybody I am Nathaniel Straus I'm trying to hold schools we've about 4,500 Mac's and being a school district every year we pretty much have to refresh those Mac's so that means basically we deploy 700 to 750 max uh-huh for a year so there we go [Music] okay perfect and so that's pretty much a yearly refresh cycle that we have to deal with it was passed on by our school board at some point that instead of rolling out these Mac's year by year maybe ninth grade through 12th grade because we are a one through one program that instead we just deploy everything at the same time all four grades at the same time so instead of doing one year's worth work that'd up being four years worth of work so before we get any further let's look at the agenda talk about how we got here what no man login actually is the security authorization database and off changer deploying Nomad login with jam fandp and then how to integrate Nomad login with Nomad so I just want to go over account types out of Mac just regular account types because I realize not everybody understands what all the common ones are so we're gonna talk about how to get to local accounts today so a local account uses the local directory service and you authenticate locally on a computer on account info is local and there's no LDAP binding required a mobile account is probably what most people are used to it's probably what a lot of people are still using you're bound to the Mac the authentication authority is still LDAP a lot of time after directory your account info is cached locally on that computer and again you are bound the network account is probably used less often maybe use more in a lab environment there anything else and this is where you are still authenticating to LDAP like Active Directory your account info is mostly stored on the network usually on a network drive and all that binding again is happening so why did we decide that a local account was what we wanted to move to it's really about which authority holds the keys right so and I have a Mac usually a laptop at this point I want to make sure that that mat can always login and that user never doesn't have a way to log into their Mac so if I'm using a bound account a mobile account and...