In this demonstration, I will create a volume assigned to drive letter,
create a folder on a volume and share the folder.
You will also learn about optic rights,
NT F s permissions and share permissions.
Let's begin by looking at the share volume itself.
right click to manage
and click on storage
within storage. We're gonna go to disk management.
Just management will bring up
graphic of all the images and all the drives you should see
I'm gonna slide this up so we can see everything.
And right now you can see we have a disc zero,
which has the C drive,
a disc one which is blank on Ella allocated,
and a disc to which is an external hard drive.
Actually, USB drive in this map to F
also a CD rahm. But it's not manageable because it's not loaded.
up here you see a system
partition and a boot partition.
The system partitions starts
and the boot partition is the partition that boots into
when system tells it where to go.
Normally, you only have one system and one boot partition. And that's why you don't see a menu. If you had a multi boot system, you would actually see a menu
for which boot partition to select.
So Disc zero and disc one
our representative single drives. That's how the operating system sees them
in reality. In this situation,
each disc zero and this one have three hard drives in a raid array.
But that's handled at the drive controller card level.
And the operating system only sees the output from the controller card
in the output from the controller Card
announces this as a single Dr.
So we see disclosure was a single drive, and this one is a single Dr.
So go to the disc one drive and I've prepared for use
the other options. So it's calling a new, simple volume.
So just to show that let's make it
30,000 megabytes or 30
Let's call it is where we sign and drive later.
Let's for this case. Let's call it tea for temporary
and we're going to format it. We're going to format. It is NT F s.
Give the volume label of temper
and do a quick format.
When we do that, it reads everything back to us
and then you had finished.
Now you see it's his formatting,
and as soon as it's formatted,
you don't show up with Dr Water. We assigned to it with the volume name we gave it.
So here we are tempted
noticed the rest of the space here is unallocated,
and I could create another
with the remaining space.
instead of doing that, however, let's cancel.
And let's cancel this
because let's assume that we want the entire disc to be a single volume
so we could go here didn't elite volume
when you delete a volume and erases all data on that volume, so make sure that you don't have any data
or that the data is okay to lose,
I am going to force the deletion
and now so unallocated again.
So let's go back now and make
the entire volume one
notice here, by the way, minimums, disk space and megabytes is eight,
and maximum is the size of the entire disc
and we're going to excite. It
knows that will allow you to sign it. D you know D is already in use
because at the moment D isn't active.
So let's assign it g and said
and we can make that stand for share.
Yeah, let's see if it'll take a name with a space in it.
Just a case. You curious?
So now we're the drivers being formatted and in t f s is gonna be assigned to drive letter,
and it's gonna be made available.
So as soon as that's done,
we should be able to go to
So from the S drive Now
and see that the folder is empty.
So now let's make a new folder
and let's make another new folder.
So now we've created two folders.
Let's take a look at the permissions on the folder.
Now we talk about rights and we talk about permissions and we talked about share permissions.
Rights has to do with who gets to make changes
to the properties of this folder,
not the changes himself, but who has permission to make them
of the go to security.
We see the folder has an optic name,
have object permissions
So since we're the creator owner,
we get full control.
But let's change one. Let's go into
It's going to security.
And let's say the users
down here show that they have
read and some special permissions.
Let's give them read only
Excuse me. Take users Go.
Come here and notice that the
permissions have grade boxes.
Gray boxes means see permissions are inherited from a parent.
So if I come back here
and go to the volume itself, Dr s
and look at the properties,
Here they have the permissions,
and all they have are special permissions. Because everyone,
the good and the users
the user's this time have
read executing list folder contents and read.
And they're not great this time. They're not inherited.
They actually came from the drive itself.
We go back, look at the same thing
held other permissions.
They have the same permissions. But they're gray now, which means they've been inherited.
Which means I can change them.
I can take away their reading, reading, execute
Let's give them full control.
So now we're going to see users have full control
go back in. And look,
the full control we gave them
is not inherited because
those permissions are not gray.
Now we can create a file attempt to s.
And if we created filing him to us by saying new
and we now we'll get the permissions for the text document
noticed they have full control over the file because they have full control over the folder in which it's created.
So here's a question. What happens if we copy this file
and put it in temp one?
permission changes we made.
Stay with the folder,
and the answer will be
No, they did not. They do not have full control.
What happens is Thebe permissions are actually part of
the file storage and the written to the file storage area.
copy and paste a file, you making a second copy, so it's a new right
and it gets new permissions.
So now let's watch a different behavior.
and we're gonna create another filing temp to we're gonna call a test move
and we try to move a file from
be able to retain the permissions that were originally set
here We have temp one
And here's attempt to.
text document called Test move.
Attempt to users had full control. So I would expect
if I go in here and look at users
that I see full control and I do,
it's like you can see it here.
So if I take test move
and they do it, Microsoft says to do
and I grab it and I move it.
I should be able to retain permissions.
In other words, over here, users only have
I go over here and take a look.
My users should have full control if he kept the same for missions from attempt to,
strangely enough, how they did it,
even though he used to move back.
So let's try it a different way.
Let's make a new text document
and it's hollow. Test move to
let's want to command prompt.
And how would I go to his s dr
Type s colon? Enter?
And if I want to go to a folder name,
I change directory or CD,
and I'm gonna go to camp
Now, did I have to capitalize that
if Iran Lennox the answer be Yes. In Windows,
And of a type directory or D i r.
There's test move to.
So if I use the move command
you can see here I'm going to move is to command the sources. Test
source file is test moved to dock text, and I'm in
attempt to directory. I'm going to move it to the temp. One
So let's close the command problem.
It was test moved to
lo and behold, users now still have full control.
That's a quirk in windows.
the graphical interface, even when you tell it to move, it does a cut and then a paste,
which means it writes a new file.
If you use the command line, it doesn't write a new file. It actually keeps the exact same
bits and bytes on the drive,
and he goes into the file tables
the file tables that this file should now be in a different folder.
So when you use the move Commanded doesn't get re written. Since the file doesn't get rewritten, the permissions don't change.
Henry. We'll get one more piece share permissions
And let's share this
in the safe, specific people,
I notice I'm getting to pick people here.
I can pick individuals acting pick groups.
everyone that should work
by default has read control.
Or I could give them read right
Pelican administrators. They have read right by the fall.
And if I could share,
it's now shared using this string
Win 2008 Dash P. H. Y, which is the name of this
computer and in the name of the cold.
and I go and I hit run
notice again, I don't have to capitalize.
It doesn't say s drive anymore, says server name
So what happens is if you think of this as two different
*** to have to go through or two different
checkpoints to cross,
you get the least of the two permissions.
So if I have full control with the file level,
then I have full control if I access to file directly.
But if I have read only at this level,
so if I look a test moved to
which we know just a minute ago I had full control of
And the difference is when I accessed it directly,
right off the hard drive,
I got the hard drive permissions.
Now, when I access it via the share,
I get the hard drive permissions. But then they're filtered by what the share allows and this share only allowed read.
So if I access the director, I have full control.
But if I access it via a share. My full control is changed by whatever Mason's affair has,
because I can't have any greater permissions than the least of the two.
If I have read only on the file and full control on the share,
I'll still have read only
because when I get to the file, I'll still have just read only even though the fear, so they could have
I now have created the share
So now I've closed off everything except the shared volume, and you can see it says Win 2000 p h. Y
So let's go back and let's click on
and you click on the server. We see there's actually three shares on this.
Two of them existed already, and we created the third.
If we wanted to make this permanent and give it a drive letter,
say map Network drive.
We can give it a drive letter and let's say em,
and if we tell it to reconnect and log on
every time the system boots up, it will go back and look for this same
system again based on the
backslash backslash server name, back slash share name construction.
now, it says that the EM drive.
So I have mapped a share to a Dr letter. So now I can run commands based on the drive letter.
map to the EM drive.
So now, on this computer, that share name is this Dr Leiter?