Preventing access to Public Folders through OWA


I would like to prevent access to public folders for some users of Outlook Web Access. The only way I can see is to set permissions on each and every folder. This wouldn't be a problem as they will never (!?) need to access public folders but I would like to know if there is a simpler way.

DJWalkerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JasonBighamCommented:
You want them to have access to these folders with Outlook but not OWA?
0
DJWalkerAuthor Commented:

It's not necessary but I would prefer it that way.
0
JasonBighamCommented:
There is a small visual basic script for OWA Segmentation. From there you'll be able to control individual components for OWA.

http://support.microsoft.com/default.aspx?scid=kb;en-us;311154&Product=exch2k
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

David WilhoitSenior Consultant, ExchangeCommented:
Nice article Jason, never even thought to try something like this. Can someone tell me what the administrative needs or goals would be for something like this? just curious....

D
0
JasonBighamCommented:
My thinking was that the admin would be worried about users pulling items from the public folders via OWA... specifically, very large items that frequently find their way into the PF system. This is assuming that the admin does not use Outlook over VPN for example, and uses OWA due to bandwidth concerns.

What I find more interesting about segmentation is that it allows a way to streamline 2000 OWA a bit, as it is definately slower than 5.5 was. You can just hack out the bits you don't want.

Haven't done it myesly though. OWA 200 is slower, but not enough to bother me.
0
David WilhoitSenior Consultant, ExchangeCommented:
used 2003 yet??
0
JasonBighamCommented:
Naw... it is an unspoken rule around here to stay a version behind. Or at the very least, until the first service pack is out.

I have played with the 2003 OWA, albeit briefly. It's nice. Makes me wonder what their plans for Outlook are, because the 2003 OWA is a near replacement for Outlook now. When you buy a Exchange CAL you technically get Outlook free, so i guess they aren't going to lose that Enterprise revenue if they do plan on replacing Outlook with OWA in the workplace.
0
David WilhoitSenior Consultant, ExchangeCommented:
Outlook 2003 will do the RPC-over-HTTPS now, so Outlook functionality without VPN or opening messy firewall ports is now possible. although, only with XP, not 2000. Web access will offer nearly the same functions, but not quite all, so i don't think Outlook is ready for teh scrapheap yet.

BTW, E2K3 is a superior version, even in Beta.

D
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.