When joining the domain, we use the DNS suffix so we could have one mobile config profile for joining
the domain, yet have our computers go in a different use.
Now we're going to talk about accessing network shares with a mobile config profile and do something
similar.
So I've created a mobile config profile called Pushchairs on the Dock.
And let's go ahead and take a look at it now.
All of the settings are default except for doch items and dock items.
We're going to amount to SMB shares from our Active Directory server one called DC Local, which is
going to be a share that is on a server that's local to each site and then SMB Global, which is going
to be a share that's on our New York server that everybody in the organization can access.
So let's go ahead and deploy that profile and.
When we deployed our active directory profile, we had two jobs, we had a copy job and installed job,
and I had mentioned that we were going to go ahead and get around that in the future.
So let's take a look.
We're just going to do everything with one job.
And the first part of it is downloading the profile.
So at each site we have a Web server with an installs folder on it.
And so when you go to HTP installs, it is going to bring you to a Web server that is local to your
site and the rest of the path is the same.
So this will work at every site and download the mobile config profile locally.
So this is going to download it and then say that to the temp folder and then we're going to import
the profile and delete it, just like we did with the Active Directory job.
Now, on these machines, we can see that we've got the Active Directory profile set and we are logged
in with our active directory users.
And I'm going to go ahead and move these so we can see everything happened.
So go ahead and run the job and then you can see that.
We've got an additional mobile config profile and we have our two shares.
So let's go ahead and take a look at our shares and so we do have our local share.
And we have our global share now, the first time you make a connection to the user will get prompted.
So on the local share, let's go ahead and create a new folder and we're going to just do something
so it's identifiable for us.
So local.
And then local, and then we'll create a folder called ICRA and let's go ahead and go to our or Windows
Server.
This is the New York one.
And let's go ahead and look at her files.
OK, so on local, you can see that we've got McGarvey because that's the one that's in New York and
we can't see the folder for L.A. So now let's go ahead and go global and we'll do the same thing.
And we're going to go ahead and create a folder on this one.
And we're going to do the same thing over here.
And you can see that these are accessible to both.
Now, when I am on the the New York computer, my hobby and I see the high series file and I go to delete
it, it's.
It's going to say that I can't do it because of permissions.
So when you write these files to the shares that all the Windows permissions are still going to be respected.
Now, the good thing about this is if I go ahead and I purposely or accidentally delete the shares or
dismount them, that I can always bring them up with the items that are in the dock.
Now, I can't erase these no matter how hard I try.
They're basically you can't remove them, there's just no options to remove them, so this is a much
easier way of providing shares than instructing users to go to connect to server.
Furthermore, when they do that and they if they were to accidentally throw the share in the trash because
it could appear on the desktop, if you have your preferences set up to show connected servers, this
is basically going to unmounted.
And then the user would have to go to connect to server to get it back again.
And that's just not something that most people are going to understand how to do.
But by presenting the shares on the dock, there's just no way for the users to get rid of them.
So let's go ahead and see what happens when we delete the mobile config profile, so just like before
I created a job by getting the unique identifier with profiles and let's go ahead and run it.
And as you can see.
The items are removed, and if I go ahead and get rid of this on.
Then it's it's basically it's gone, there's there's no trace of it.
And if I want to get it back, I mean, this doesn't remove permissions or access to it, but the user
is just not going to have an easy way.
They're going to have to go to connect to server.
All right, another way that you could provide an easy to use mount is through home directories.
So if in your Windows environment you have set it up home folders for your users, then they will become
available.
And the Mac.
So I'm going to just go ahead and log in with our active directory user.
And let me point out that for this to work when we go to test.
And do the PDS configured, so what needs to be enabled is the use windows, you see path where home
must be equal to enable in our lesson on creating the mobile config profile.
You'll notice that this was checked by default.
And when we joined active directory with a script, we didn't specify a parameter for it, but it also
takes on by default.
So we have our old accounts, global, local, and now you can see that we have a network home.
And so this is the home folder for.
Our user, and so we can see its domain controller home and remember, in our environment at least,
DC resolves to the local site.
So it's only going to be available in New York for this user.
You could point it to a you know, you could point it to a share that's available across the country
if it's going to be a traveling user.
But in our example, we're just doing it this way.
So if we go there, we can see we've got the same folders.
And just like when we added this through the docs mobile config settings, it can't be deleted.
There's no option if you try to drag it in the trash, it just doesn't work.
So anyway, that's just another way that you can provide an easy to access network share for your users.