This section is all about installing applications to a large population of max using the methods described,
will work on a few dozen max in a single building to tens of thousands of Macs and buildings located
all over the world.
Now we're going to use A.R.T. to demonstrate how.
But the purpose of these lessons isn't to teach specifically, but to teach how to install applications
with scripting.
Apple remote desktop is just the vehicle to deliver these scripts to the machines.
Now, there are many management systems out there for Mac and we can't demonstrate them all.
But what you learn here will apply to any other system you may have.
Now, if you do have a large population of Macs in multiple locations, there's a future section dedicated
to some additional techniques that won't be covered in this section that will help you in this scenario.
As we go through this section, we will use primarily the Unix job tool.
The reason for this is that we can copy any script we make into any other tool and it keeps Apple remote
desktop out of the equation.
We do have a however, it is very useful for prototyping.
You can create a best script on your own system, copy and paste it into already been tested on a few
VMS very quickly.
Once you're confident in your script, you can use that code with other tools knowing that it will work
well.
So before we go into details about installing applications, let's let's discuss a little bit more.
So we've been working with with our team sample machines and we've had these these lists here.
And so I want to explain how these lists are generated.
Now, these are what are known as smart lists.
So if any computer meets some criteria, it will appear in that list.
So in New York, we know that all computers start with the name zero one.
And our computer is not only in New York, it's also in building one and it's also in room one hundred.
Now, if I change this to one on one, then my computer disappears because my computer is in room one
hundred.
Now, if you're going to go ahead and use a card for prototyping and not as a complete management system,
you're going to want to get a sampling of machines in here that are unique in some way.
So I've got machines in different sites and I've got machines with different operating systems.
So that may be enough detail for what I do.
But for what you do, you might want to have more groups of machines to to test with.
Furthermore, if a card is going to be your main deployment system, then you may want to have groups
for all sorts of rooms or buildings or configurations.
So another feature that I really like in HD is the ability to create a template.
So when we deployed mobile config profiles, we basically follow the same procedure for all of them.
So what we basically do is we would download the profile, we would import the profile and then we would
delete the profile.
So we're probably going to do that quite a bit.
So if I go to a template and say, see this template and then I say deploy configuration profile.
And save this.
Then the next time I want to create a script, I can go to template and then take that template and
now really I have to do is change the name of the mole config profile and everything else is done.