Calendar on intranet

[csteinhilber]

I'm pretty green when it comes to dealing with Exchange, but I have what I think is a reasonably simple task. To list conference room bookings on my company's intranet. But I've done quite a bit of research online, and I'm left very confused and unclear how to proceed.

The set-up:
- Exchange 2003 (unsure of service pack level, but can certainly confirm if any SP are needed) on server "X"
- IIS, serving intranet (classic ASP/VBSCRIPT) on server "Y"
- All conference rooms have Outlook accounts with Auto-Accept Agents

All I really want to do, on server Y, is have my ASP page be able to query the Exchange server and produce a custom list of bookings such as:

Conference Room A-
11:00-12:00 - Meeting w/ Bigwigs (George, Paul)
1:00- 1:30 - Conference Call (John, Ringo)
Conference Room B-
No meetings scheduled
Conference Room C-
8:30-12:00 - Breakfast of Champions (Mike,Frank,Joe)

etc.

I've read about OWA, but I'm not sure that I'd be able to customize the format of the data that's returned if I use OWA (not only that, but it dosn't seem like the URL format

http://server/exchange/ConferenceRoomA/calendar/

is able to access the Conference Room calendar - while

http://server/exchange/myname/calendar/

is able to pull up my own).

I've read about CDO, but I'm not even sure that it's used with Exchange 2003 (all the online resources for it are many years old and seem to relate to older versions of Exchange).

And the fly in the ointment seems to be the fact that the intranet server IIS is not running on the same box as the Exchange server. Is there a way to get around this setup?

Basically I was imagining creating an object in ASP/VBS, through which I could retrieve datasets from given account calendars, and then loop through those datasets myself to output the appointments how I want to. Is this even possible?

Any insight would be appreciated.
Thanks in advance,
-Carl

 

[billieT]

CDO is still valid. What you'd do is set up your magic script, and then have it redirect to the Exchange

http://WWW server,

since that will be running in any case.

As to how to do what you want, I wouldn't have the faintest idea. It is not a simple problem unless you're a VB programmer with a good understanding of the Exchange web parts. You might find that there is a third-party program out there that can do what you want (and if you weigh it up against potential development costs, it may well work out cheap).