C:\ Directory Security

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Help me out here folks.

I work in a fairly large school district. We just completed a refresh of
some 1,700 computers. Starting with this refresh we are deploying Windows XP
SP2 and NTFS. The previous operating system was Win 2K with Fat32.

As can be expected, there have been a couple of bumps along the way,
upgrading the file system. But today we had a situation where one of the
users, in the past, was creating a .txt file in the root directory of C: for
a report that she has to do on a regular basis. Now, with NTFS, she can't
create the file in C:, and one of my co-workers is up in arms about it.
Instead of just creating a different folder to place this blasted .txt file,
he wants to make it an issue.

So, here is where I'd like some help. I want to list all the reasons that
security on the Local Machine is violated by allowing the user to create
files in C:, and collect as many KBB's about it as possible. Would anyone
mind pitching in and helping me out?
 
You need to educate the user to create a new file
in the "My Documents" folder. The icon is right
there on the desktop and is placed there for convenience.

--
Carey Frisch
Microsoft MVP
Windows Shell/User

---------------------------------------------------------------------------------

:

| Help me out here folks.
|
| I work in a fairly large school district. We just completed a refresh of
| some 1,700 computers. Starting with this refresh we are deploying Windows XP
| SP2 and NTFS. The previous operating system was Win 2K with Fat32.
|
| As can be expected, there have been a couple of bumps along the way,
| upgrading the file system. But today we had a situation where one of the
| users, in the past, was creating a .txt file in the root directory of C: for
| a report that she has to do on a regular basis. Now, with NTFS, she can't
| create the file in C:, and one of my co-workers is up in arms about it.
| Instead of just creating a different folder to place this blasted .txt file,
| he wants to make it an issue.
|
| So, here is where I'd like some help. I want to list all the reasons that
| security on the Local Machine is violated by allowing the user to create
| files in C:, and collect as many KBB's about it as possible. Would anyone
| mind pitching in and helping me out?
 
Right, I understand that. But what I need are the reasons why users should
not be allowed to create files in the C:\ root directory. Obviously, its been
made off-limits for a reason, and I need to be able to explain why. For me,
it seems perfectly reasonable that a user can't create a file there, but I
need to be able to give reasons and examples why they shouldn't.
 
To put it another way, what malicious things could a user do if they were
allowed to create files in the C:\ directory?
 
Pete said:
To put it another way, what malicious things could a user do if they
were allowed to create files in the C:\ directory?
Click to expand...

Errm.... shove a virus right into C:\Windows? Delete system files? Take
your pick. Particularly in a school, users should never be allowed
access to system files. They should have only a few restricted folders
where they have access.

Malke
 
Back
Top