How do I remove a folder from viewing ?

[DaveHoskings]

I have just moved from Novell servers to Microsoft and I
cannot find a setting that was automatic in Novell. I
would like users to only see folders that they have access
to but I cannot find a setting for this. Currently
everyone in my company sees all the folders but can only
access certain ones (ones that I have defined as
accessible). I don't want them to see folders that they do
not have access to.

Any suggestions?

Thanks,

DH

 

[Scott Harding - MS MVP]

You cannot do this with Windows and never have been able to. You can only
restrict their access or share the fodlers out at a different level so they
only see the folders you want them to. I wish MS would include this but not
yet......you can also hide shares by adding a $ to the end of their
sharename. There may be 3rd party apps but whats the difference really? If
they can't get into it they aren't going to see anything..........

 

[Guest]

Never say never.

ScriptLogic Corporation (www.scriptlogic.com) is releasing a new product
that will do exactly what you want (beta 10/04, release 12/04). Simply
install it to your file servers that host the shared data and it will only
allow users to see what they have access to -- just like Novell did. So
simple too -- there is nothing to configure, it simply filters directory
lists based on the user's NTFS security.

Scott, you ask what is the difference between not seeing it and seeting it
but not having access? Everything in my opinion. Ever hear the saying
"Curiosity killed the cat"?

Brian Styles
ScriptLogic Corporation

 

[Lanwench [MVP - Exchange]]

Never say never.

ScriptLogic Corporation (www.scriptlogic.com) is releasing a new
product that will do exactly what you want (beta 10/04, release
12/04). Simply install it to your file servers that host the shared
data and it will only allow users to see what they have access to --
just like Novell did. So simple too -- there is nothing to configure,
it simply filters directory lists based on the user's NTFS security.

Scott, you ask what is the difference between not seeing it and
seeting it but not having access? Everything in my opinion. Ever hear
the saying "Curiosity killed the cat"?

True, but as long as the users can't DO anything they aren't supposed to, I
don't care what top-level folders they see. If they want to spend a lot of
time staring intently at the mysterious folder called "Accounting", no big
deal to me. The main reason I'd like to be able to hide folders users don't
have access to is to make everything look nice and pretty.

 

[Scott Harding - MS MVP]

I did mention there may be 3rd party apps that can do this

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Lanwench [MVP - Exchange]"

 

[Guest]

I think we're all in agreement.

Ultimately, the protection is there - can't get into the door if you don't
have the key. Just nice to also be able to hide the door completely...

Always nice to have the option.
-Brian

I did mention there may be 3rd party apps that can do this

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

"Lanwench [MVP - Exchange]"

True, but as long as the users can't DO anything they aren't supposed to, I
don't care what top-level folders they see. If they want to spend a lot of
time staring intently at the mysterious folder called "Accounting", no big
deal to me. The main reason I'd like to be able to hide folders users don't
have access to is to make everything look nice and pretty.

 

[Gary Smith]

I think we're all in agreement.

Ultimately, the protection is there - can't get into the door if you don't
have the key. Just nice to also be able to hide the door completely...

Agreed, and here's why: Server X has about 600 shares. I have access to
about 8 of them. When I go to map a logical drive to one of those shares,
I'm presented with a drop-down box listing all 600. Scrolling to the one
I want is _very_ tedious, especially when accidently landing on the wrong
one will give me an Access Denied message and pop me back to the top of
the list.

 

[Lanwench [MVP - Exchange]]

Agreed, and here's why: Server X has about 600 shares. I have
access to about 8 of them. When I go to map a logical drive to one
of those shares, I'm presented with a drop-down box listing all 600.
Scrolling to the one I want is _very_ tedious, especially when
accidently landing on the wrong one will give me an Access Denied
message and pop me back to the top of the list.

net use x: \\server\share

 

[Gary Smith]

net use x: \\server\share

That works nicely *if* you know the share name in advance -- and know how
to spell it.

 

[Lanwench [MVP - Exchange]]

Lanwench [MVP - Exchange]

net use x: \\server\share

That works nicely *if* you know the share name in advance -- and know
how
to spell it.

And presuming one knows how to use a PC and have electricity and full use of
one's thumbs, etc. :-D
I'd expect that someone who needed to access the info would know where it
was, and how to spell it. The info could very easily be put into a batch
file login script that you run from your desktop when need be. You've
already said you need only 8 out of 600.
Since I set up many of my shares as hidden (with the $) anyway, browsing
won't help someone....

 

[Gary Smith]

Lanwench [MVP - Exchange]

net use x: \\server\share

That works nicely *if* you know the share name in advance -- and know
how
to spell it.

And presuming one knows how to use a PC and have electricity and full use of
one's thumbs, etc. :-D

Yeah, those are also helpful.

I'd expect that someone who needed to access the info would know where it
was, and how to spell it. The info could very easily be put into a batch
file login script that you run from your desktop when need be. You've
already said you need only 8 out of 600.
Since I set up many of my shares as hidden (with the $) anyway, browsing
won't help someone....

I don't need to do this often, but every now and then I'll get email from
a co-worker with reference to a share that I need to access once or twice
and probably never again after that. Very often the information is
incomplete ("The file is in my shared folder"), and it's usually quicker
to browse for it than to elicit the full details. It would really be nice
if the list showed only machines that had an available share.

I do use batch files for shares I access frequently.

 

[Lanwench [MVP - Exchange]]

Lanwench [MVP - Exchange]

Lanwench [MVP - Exchange]

net use x: \\server\share

That works nicely *if* you know the share name in advance -- and
know how
to spell it.

And presuming one knows how to use a PC and have electricity and
full use of one's thumbs, etc. :-D

Yeah, those are also helpful.

I'd expect that someone who needed to access the info would know
where it was, and how to spell it. The info could very easily be put
into a batch file login script that you run from your desktop when
need be. You've already said you need only 8 out of 600.
Since I set up many of my shares as hidden (with the $) anyway,
browsing won't help someone....

I don't need to do this often, but every now and then I'll get email
from
a co-worker with reference to a share that I need to access once or
twice
and probably never again after that. Very often the information is
incomplete ("The file is in my shared folder"), and it's usually
quicker
to browse for it than to elicit the full details. It would really be
nice
if the list showed only machines that had an available share.

I do use batch files for shares I access frequently.

You have an awful lot of shares, so this won't always be easy. You can
always ask the person what the drive letter or UNC path they're pointing at
is - they can see this in Windows Explorer. Train 'em to give you as much
info as possible up front.