Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
   

Blocking Attachments with Outlook Web Access

Page 1 | Page 2 | Page 3 | Page 4

For those of you who hate dealing with those pesky registry settings, there is a fairly new tool for administering OWA properties. The tool is essentially a set of web-pages that you install on a server that allows you to connect to front-end and backend servers to manipulate the settings.

 You have to watch the “Accepted Front-end Servers” field as the OWA Admin tools are more restrictive than the registry keys. Remember this field represents the syntax the User will use when they connect and not the actual name of the server. Also, in our environment, we had problems entering multiple entries of fully-qualified names of the servers and had to instead place the entries directly in the registry. None of the other settings on these pages has given us any trouble.

 So if you are looking to provide limited OWA functionality for Internet use, partner connections or even internally, you can do it in less than an hour and with no equipment purchases.

.
 

Blocking Attachments with Outlook Web Access

Page 1 | Page 2 | Page 3 | Page 4

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008