In this lesson, we're going to discuss how to install monkey tools on our clients.
Now, let's go ahead and take a look at the install monkey job and as you can see, monkey tools as
a package.
And we're going to use our package template to download, install and then delete that monkey tools
package.
Now, the Monkey Tools package is the same package that we use to install the monkey tools on our admin
workstation.
OK, so we need to configure monkey tools because monkey needs to know where our monkey repo is.
So if we go ahead and click on this job, I have a script that's going to write keys to a p e file that's
stored in library preferences.
So in other words, it's going to be a preference file that gets applied to all the users of the computer
or basically any time monkey runs.
It doesn't matter who's logged in or even if the computer is logged in, then it's going to know where
the software repo YORO is.
All right.
So the software repo URL is basically the URL that we've been typing into Monkey.
So that's the URL that takes us to the Catalog's manifests and packages page.
So if the URL that you type in here gets you to that page, then the software repo YORO is correct.
The next key I want to define is the client identifier and here I have it set to site default.
Now in our demonstration, we had a site default manifest and we had a developer's manifest.
And so any client that I run this job on, it's going to download install software that's in the site
default manifest.
If you don't specify this key, if you just erase it from the script, then Monkey is going to look
for manifests based off of the computer's name.
So the first thing it's going to do is try to find a manifest that with a name that matches the computer's
fully qualified domain name.
And if it can't find that it's going to try to find a match with its host name.
And if it can't find that, then it's going to try to find a match with its serial number.
And then lastly, it will just go ahead and download the the site default manifest.
So in this script, I'm just specifying it outright.
The next key that I like to define is one called suppress user notification, and I set that to true.
So the user notification is suppressed.
So what what that means is that users are never going to get notified by a monkey that there are software
updates or software installs available.
All right.
So then how do users install software or how do they know their software to install?
Well, when you import software in a monkey, you can specify whether it should be automatically installed
or not.
And in my environment, I have all my software set to install automatically with no user intervention.
And so the user notification is not needed.
Now, your environment could be different.
So I want you to be aware of this of this key.
Now, there's a lot of other Ts that are available, and if you go to the monkey site, then you can
see that there's this supported managed install keys and this applies to the file that we're in right
now.
And so basically it will give you a bunch of keys and their default setting.
And if you want to change anything from the default, then you can just go ahead and specify it in this
file.
All right.
So let's go take a quick look at the developers one.
And you can see it's exactly the same.
It just says developers.
So that's how you configure a monkey client.
So let's go ahead and install the monkey install monkey on each machine and I'm going to go ahead.
So it matches the demonstration we did earlier.
I'm going to go ahead and put site default on our McGarvey machine and I'm going to put developers on
our high CRM machine.
And then just like when we installed the monkey tools on our admin machine, we have to go ahead and
restart.