![]() If we check the Extension Attributes page of the device that we have deployed with this policy scoped to it, this looks to be true: I think the easiest option here is to make use of Extension Attributes: Without knowing this, we can't really act on it reliably. Next, we're going to want to know when a device has auto logon enabled. Now we need to make use of this new-found freedom. It will run the script to enable the auto logon at startup. With those two parts done, we now have a policy that will run at enrolment complete for any device that comes through that PreStage. Jamf Pro - Auto Logon Script Policy Restart Tab This is important, as we've just configured the device to automatically login as this user on startup, not when the script runs. Jamf Pro - Auto Logon Script Policy General Tab Jamf Pro - Auto Logon Script Policy Script TabĪbove, you can see where those parameter labels come in to play.īelow, we've configured the device to automatically restart as soon as the script completes. I've prefixed this with a "00." in an attempt to help ensure that it is the very first thing that runs when it tells Jamf that the enrolment is complete. Next, we'll create a new computer policy. This will make it much easier to remember what does what when it comes to creating the policy. So here, we've added the script to Jamf, and then updated the parameter labels to Username and Password. Jamf Pro - Adding the script Jamf Pro - Adding the script parameter labels After that, we're going to create a policy to actually do something with the script, and scope it to our Devices - Lab - Auto Advance smart group that we created earlier. To achieve our goal, we're going to make use of this:įrom here, we're going to need to add this script to our Jamf Pro instance, and configure the options (makes it easier in future if you name these now). You're allowed to skip account creation, but then not sign in … Might be worthy of a feature request. Unfortunately, this doesn't seem to be an option in Jamf Pro right now, which I think is incredibly short-sighted. We're going to have the device automatically sign in as our local admin user that was created as part of our PreStage settings. I wanted more, and it's taken a few months to get to this stage. This is not overly helpful for them unless they're checking the policy history. ![]() So far, I've just been running policies in the background while the device has been seemingly idle at the log on window. One of the major issues I've been facing up to this stage has been giving the local technician decent feedback about how the software installation has been going. ![]() Now, we're going to want to do something with this group, otherwise what's the point. Anyway, the first Smart Group we're going to make use of is one that contains devices that are enrolled via the Lab - Auto Advance PreStage method.Īn image speaks a thousand words, so we're going to be making heavy use of them in this post! Jamf Smart Group Creation Settings Jamf Smart Group Creation CriteriaĪny devices that come through that PreStage will now be automatically added to this Smart Group.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |