![]() JAMF PRO STATUS INSTALLYou want to install them in a specific order. My only suggestion is to number these packages. But, if you want to know how I'm syncing HTTPS DP's, let me know. The first thing we'll need to do is download and get the PKGs on to your distribution point(s). It is not production ready.įor now, we'll continue to use the versions available from nu. Work is underway with NoMAD 2 with all sorts of quality of life improvements, and feature updates. However, keep in mind that Jamf acquired them back in 2018: - Since then, nothing much has really happened development-wise, as they're pushing the Jamf Connect (paid licence) angle. If you haven't heard of these, it's worth taking a look. To get around that issue, I make use of NoMAD and NoMAD Login. They are not bound, and haven't been for some time. Our lab machines are authenticating against Active Directory. Right, let's tackle the final two policies. You then have a group based on the room AND that they need to have completed the onboarding. Perhaps you only want room specific software to install after this whole process is complete so that the users can just get on with the basics? Clone this, and add an AND clause with the room information. You could also base other Smart Groups off of this, too. Now we can scope any future policies to this group knowing that they have very likely finished doing what we need them to do first, and that they are in a certain state. JAMF PRO STATUS PROLet's create another Smart Group based on this new attribute.ĭisplay Name: Devices - Lab - Onboarding CompleteĬriteria: Onboarding Status IS Onboarding Complete Jamf Pro - Smart Group Screenĭone. Great, now we have another attribute to work with, we need to actually do something with it. Input Type: Script Jamf Pro - Extension Attribute Screen ![]() Status=`defaults read /Library/Preferences//Library/Preferences/ac.uk.grayw.blog onboardingComplete`ĭescription: Checks to see if the onboarding defaults string is set to complete We'll create the Extension Attribute as a script that looks like this. To make scoping of generic policies easier, we're going to make use of this by creating another Extension Attribute. We'll let it get those on the next check in once we're done. We don't want other policies running during that jamfCommand policy line, and interfering with our onboarding process. There's a reason I'm not doing this before the recon command. usr/bin/defaults write /Library/Preferences/co.uk.grayw.blog onboardingComplete -string "Complete" ![]() To do that, I'm going to write out to a plist file. There are certainly improvements we could throw in here, and perhaps this isn't the perfect method, but I want to know when a device has reached the end of this process. usr/bin/defaults write /Library/Preferences/co.uk.grayw.blog onboardingComplete -string "Complete"ĭEPNotify "Status: Install NoMAD & NoMAD Login" ![]() JAMF PRO STATUS UPDATE# Send updated inventory for Smart Groups and check for any remaining scoped policiesĭEPNotify "Command: MainText: Installing Room Specific Requirements"ĭEPNotify "Status: Update inventory record." In this post, we're going to go over the last few lines of our DEPN script to get them into a user ready state. In part 4, we covered creating some more Smart Groups, filling out our DEPN script with the rest of the application policies we wanted to deploy, and making use of the Inventory Preload feature. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |