Skip to main content

Setting the frame sizes in OWA 2003 programmatically

Had an Interesting question about adjusting the default frame sizes in OWA 2003 that I thought I’d share. In OWA 2003 there are two frames that a user can adjust the size off themselves and these changes are stored so that the next time the user goes into OWA the frame positions are remembered.

The left most frame which houses the navigation bar and OWA shortcuts is controlled via the http://schemas.microsoft.com/exchange/webclientnavbarwidth property which exists on the root folder of the mailbox eg http://servername/exchange/mailbox. You may want to make it wider or narrower depending if your customizing other parts of OWA. The other frame that is adjustable in the right most frame which holds the preview pain. The size of this frame is controlled by the http://schemas.microsoft.com/exchange/wcviewwidth property which is located on the inbox folder eg (http://servername/exchange/mailbox/inbox).

Both these properties are integers and if I was to have a guess I would say the integers represent the size of the frames in pixels. If you want to modify the values you can use a WebDAV proppatch an example script would look like the following I’ve put a downloadable copy of this code here . Setting this property doesn’t affect the user’s ability to resize the frame themselves.


servername = "servername"
mailbox = "mailbox"

xmlhdr = "<?xml version=""1.0"" encoding=""UTF-8"" ?>"
xmlhdr = xmlhdr & "<D:propertyupdate xmlns:D=""DAV:"" xmlns:a=""http://schemas.microsoft.com/exchange/"">"
xmlhdr = xmlhdr & "<D:set>"
xmlhdr = xmlhdr & "<D:prop>"
xmlftr = xmlftr & "</D:prop>"
xmlftr = xmlftr & "</D:set>"
xmlftr = xmlftr & "</D:propertyupdate>"

sDestinationURL = "http://" & servername & "/exchange/" & mailbox & "/"
xmlstr = xmlhdr & "<a:webclientnavbarwidth>200</a:webclientnavbarwidth>" &
xmlftr
df = sendrequest(xmlstr,sDestinationURL)

sDestinationURL = "http://" & servername & "/exchange/" & mailbox & "/inbox"
xmlstr = xmlhdr & "<a:wcviewwidth>400</a:wcviewwidth>" & xmlftr
df = sendrequest(xmlstr,sDestinationURL)

function sendrequest(xmlstr,sDestinationURL)
Set XMLreq = CreateObject("Microsoft.xmlhttp")
XMLreq.open "PROPPATCH", sDestinationURL, False
XMLreq.setRequestHeader "Content-Type", "text/xml;"
XMLreq.setRequestHeader "Translate", "f"
XMLreq.setRequestHeader "Content-Length:", Len(xmlstr)
XMLreq.send(xmlstr)

If (XMLreq.Status >= 200 And XMLreq.Status < 300) Then
Wscript.echo "Success! " & "Results = " & XMLreq.Status & ": " &
XMLreq.statusText
ElseIf XMLreq.Status = 401 then
Wscript.echo "You don't have permission to do the job! Please check your
permissions on this item."
Else
Wscript.echo "Request Failed. Results = " & XMLreq.Status & ": " &
XMLreq.statusText
End If
set XMLreq = nothing
end function
 

Popular posts from this blog

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You ...
Read more

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.