So if we take a look at our New York machine and compare it to our L.A. machine, we could see something
that's readily clear.
And then on the New York machine, we've got our local icon for our server share.
But on the L.A. machine, we have a local and global.
And if you remember, we upgraded the mobile config profile to get rid of the global icon if we removed
it and did that in monkey admin.
Then why is the L.A. machine still have the global icon?
Well, let's go ahead and take a look at Monkey Adnen.
Now, when we've been designing our manifests, we've considered the machine.
And if you have multiple locations, then you should consider all of your machines all around the country
or wherever they're located in your monkey manifests and design your entire monkey infrastructure from
a single monkey admin console.
Now, the issue here is, is that you can see that we do have the one on one checked, but our monkey
admin in this demo is tied to our New York server.
And unless we copy the settings from the New York server to our server, then the server is not going
to have these changes on it.
So what we need to do is synchronize the servers.
So I'm going to go ahead and minimize monkey admin.
And right here I'm on my New York monkey server and I'm going to go ahead and run a script and this
script is going to synchronize them to monkey servers together.
Now, you can see that it made an update to the package info for our version, one to one of our mobile
config profile, and it updated all of our catalogs.
OK, so now that we've done that, let's go ahead and have monkey check its server again and it's going
to be checking the server.
And so now you can see that it knows that it has the dark mobile config profile to upload.
All right.
And now our machines match entirely.
So in our next video, we're going to discuss how we can do this synchronization automatically using
a service called Chron.