|
|
Browse by Tags
All Tags » devmsgteam » OWA (RSS)
Showing page 1 of 3 (26 total posts)
-
I’ve seen a few cases come through where customer’s are trying to implement the customization features that were introduced with Exchange Server 2007 SP1. There’s a few key areas that seem to cause trouble so I figured it would be worth walking through a simple scenario that covered many of the different aspects. ( Link to Part 1 of the series , Link to Part 2 of the series ) It’s been a long time coming, but I’m finally getting around to completing this series of posts. I had originally
-
While working with one of my customer we noticed that the yearly recurring appointment doesn’t show in Outlook Web Access or Exchange Web Services(EWS) application. Customer created a monthly or yearly recurring appointment. He set the request to occur on the second, third, or fourth weekday of a month. But, whenever we use Outlook Web Access (OWA) client or customer’s Exchange Web Service (EWS) application to view this request, the request is set to occur on the first weekday of the month; but strangely,
Posted to Le Café Central de DeVa (Weblog) by deva on July 22, 2009
Filed under: Exchange Web Services (EWS), Outlook 2007, KB, meeting request, appointment, DevMSGTeam, Programming, development, OWA, EWS, EWS Troubleshooting, problems, Rollup, Recurring Appointment, Service Pack
-
There is no supported way to do this. OWA uses the IE language settings to decide which language to display. Remember that OWA is a web application and goes off of browser settings just like most every other web site out there. During the intial log-in to OWA you can set the language to use in OWA. You can also override the language setting once logged-into OWA. However, there is no supported way of forcing Englishe or any other language to be a speicific language other than to change IE (or other
Posted to Dan's WebDAV 101 (Weblog) by danba on April 28, 2009
Filed under: OWA, DevMsgTeam, ie, english, login, language, force, browser, login page
-
I’ve seen a few cases come through where customer’s are trying to implement the customization features that were introduced with Exchange Server 2007 SP1. There’s a few key areas that seem to cause trouble so I figured it would be worth walking through a simple scenario that covered many of the different aspects. ( Link to Part 1 of the series ) We continue our effort to implement our HelpTicket Outlook Web Access form by adding an element to the UIExtensions.xml file in the C:\Program Files\Microsoft\Exchange
-
With the continuation of the previous blogpost , today we’re going to see how we can use Microsoft Office Outlook Web Access or the Exchange Management Shell to configure language settings for Outlook Web Access in Microsoft Exchange Server 2007. Microsoft have provided various options to customize the OWA pages, contents/images/themes in a simpler way. As a part of that, we cam make sure that we can do the language setting for OWA, which determines the language of the Outlook Web Access logon page
Posted to Le Café Central de DeVa (Weblog) by deva on March 2, 2009
Filed under: Locale, Exchange Server 2007, Best Practices, cmdlet, Powershell, Exchange Management Shell (EMS), API Changes, Support Guidelines, Configure, mailbox, Errors, Customization, DevMSGTeam, development, OWA, Client Access Server (CAS), Forms Based Authentication, logon, identity, bulk, Language, Regional Settings
-
We seem to get a fair amount of questions and cases where the supportability of certain OWA customizations isn’t clear. In the past, many organizations have found ingenuous ways to modify the OWA files on the server in order to make them behave in different ways. Unfortunately, changing these files takes you into uncharted territory. The OWA web application undergoes extensive testing, and when Microsoft makes any changed to these files, it has to go through testing again.
-
Per the support KB , Microsoft PSS has the support policy for customization of Outlook Web Access for Exchange that cover its versions like 5.5, 2000 & 2003. Per the article, we can get more information regarding the support policy for OWA customization for its various versions like, “…The Exchange 5.5 version of OWA is made up of Active Server Pages (ASPs). The Exchange 2000 and Exchange 2003 versions of OWA are composed of two main components: templates and controls. Templates are served from
Posted to Le Café Central de DeVa (Weblog) by deva on January 31, 2009
Filed under: Store, Exchange Server 2003, Support Guidelines, KB, Not Supported, DevMSGTeam, hotfix, OWA, Exchange Server, PSS, Support Policy, ISAPI, Exchange Server 5.5, XSL
-
I’ve seen a few cases come through where customer’s are trying to implement the customization features that were introduced with Exchange Server 2007 SP1. There’s a few key areas that seem to cause trouble so I figured it would be worth walking through a simple scenario that covered many of the different aspects. The simple (and contrived) scenario that I’m going to run through is the use of a custom message type to represent a helpdesk request. This example will cover composing, sending
-
Issue: One of my customer updated me that he created an appointment by using WebDAV. But the user has the following issues when he tries to view the mailbox owner's calendar: The appointment does not appear when Microsoft Outlook is in the Day, Week, or Month view. The appointment appears correctly when the appointments are sorted by category. The appointment appears correctly when the delegate user views the appointment by using Microsoft Outlook Web Access (OWA). Why it’s happening? Later when
Posted to Le Café Central de DeVa (Weblog) by deva on December 31, 2008
Filed under: Outlook 2007, Outlook 2003, Support Guidelines, Calendar, WebDAV, KB, Not Supported, appointment, DevMSGTeam, development, MAPI Property, debug, OWA, Gotcha, Outlook, Complex Calendaring, Outlook View, Recurring
-
Here is some basic information on how FBA authentication is done with WebDAV. To provide some insight into how this works, you should look at the sample code of KB891748 and review it with the explanation below. Note that if you are going against Exchange 2007, you should reconsider using FBA authentication since FBA authentication is really for OWA and the settings for OWA and WebDAV are separate under 2007 – please refer to the links below for further information. 891748 How to programmatically
Posted to Dan's WebDAV 101 (Weblog) by danba on December 12, 2008
Filed under: OWA, WebDAV, FBA, Exchange, 2007, authentication, Forms based authentication, basic, 2000, 2003, DevMsgTeam, owaauth.dll, 440, exadmin, iis settings, esm settings, fba authentication, KB891748
1
|
|
|