OWA Public Folders won't open attachments/files if dragged to Public Folders

Hi experts!
I have Exchange 2003 and when I drag a file (xls, doc, pdf, whatever) to a public folder, I am able to later open that attachment/file from within a client Outlook but if I try to access it via OWA, I don't see the icon for the file and if I double click to open, it comes back with "You are not authorized to view this page".  

If I post to the Public Folder with a file as an attachment instead of dragging the file, I am able to open the attachment via both Outlook and OWA.  

Anyone know what the difference is and why?

Thanks!
thetraveler359Asked:
Who is Participating?
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.

SembeeCommented:
It is a feature known as "FreeDocs". By default it is disabled for OWA.

From the OWA Admin Tool:

Enable Freedocs

"Freedoc is the term used to describe a data file residing on the Exchange server store. For example, if a user drags and drops a Microsoft Word document from their desktop into a Public Folder, it becomes a Freedoc on the Exchange store. Allowing users to create freedocs can be a security risk for some organizations. For this reason Outlook Web Access disables Freedoc access by default for browser initiated HTTP requests in Exchange 2003. Users attempting to gain access to freedocs using a browser will be presented with a '403 Forbidden' error.

If you want to allow Freedoc access for your organization with Outlook Web Access, use the Freedoc settings in the right-hand pane:

Note: This feature may break the default document that may be set on some public folders. "

You can control this feature using the OWA Admin tool which is a free download from Microsoft.

Simon.
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
thetraveler359Author Commented:
Thanks Simon!

What does it mean that it may break the default document that may be set on some public folders?  I assume since I don't know what that is and haven't set one up that I don't need to worry about that?
0
thetraveler359Author Commented:
I'm a bit confused on OWAAdmin setup.  I installed it on my client PC within the domain (made sure to have installed .NET1.1 and IIS).  When I try to access https://MYMAILSERVERNAME/OWAAdmin it gives me a Security prompt, I click yes, and it gives me a 404 error "The page cannot be found".

Did I miss something?  

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

SembeeCommented:
When you have installed it on your own machine, it should go to https://yourmachinename/owaadmin - not the name of the server. Once the page has loaded you can select the server that you want to administrate.

You don't install it on the Exchange server itself - but a client workstation or another server without Exchange.

Simon.
0
thetraveler359Author Commented:
I pointed to https://MYCOMPUTERSNAME/owaadmin and got a "Page cannot be displayed" message this time.

0
SembeeCommented:
I have had the same problems. I needed to make a change at a client earlier this week. I tried 4 machines before I got one to work correctly. I think the .net framework service pack upsets it.

Simon.
0
thetraveler359Author Commented:
So should I just give it a go on a different PC or reinstall the .net?  Thanks Simon.  I'll close this question down since you already did answer my original question.  Thanks!

0
SembeeCommented:
I tried reinstalling .net - it didn't work. Eventually I found a machine (a DC I think it was) and managed to get the tool installed. Made the change I wanted then removed it.

Cheers for the points.

Simon.
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.