Extract Exchange 2003 data

I have searched everywhere for an answer and seems I am either blind or there is no simple solution. Basically I have a need to report on data stored in an Exchange 2003 data store. There is mention of a OLE DB for Exchange 2000 but nothing for Exchange 2003. For example, A company report on time spent on various categories in a staff's calendar, etc. I would like to use SQl 2005 SSIS to extract and reporting services to report. Why is this so difficult? I come from a Lotus Notes / Domino background and there are numerous articles and ways to do this? Please can some MS guru please give me some direction on where to look?

Cheers

Damien

Damien,

Have a look at this Microsoft support page: http://support.microsoft.com/?kbid=813349

It lists the various methods to access Exchange programmically and status of support. I used to use CDO for this type of access...

Frank

|||

Frank,

Once again this artile is date 2005 and yet still only mentions Exchange 2000 and 5.5? I am confused does microsoft not know that 2003 exists at this date?

Sureley there must be a relevant article for 2003? Anywhere?

Cheers

Damien

|||

Damien,

Try this link: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/e2k3/e2k3/_exchserv2k_provider_extensions.asp

This is from the Exchange 2003 SDK. It lists relevant API's for accessing the Exchange 2003 store.

Frank

external access - the definitive solution?

ok, I know this topic has been covered COUNTLESS times in this group,
yet the solution is still very, very hard to come by. Has anybody
successfully published their reports (through a custom .net web
application using URL access to the report server) to an external
network / internet?
If so, how... Custom security extension? Handing out network logins
(with very restricted rights) to the report server?
A final, solid solution would be greatly appreciated...Yes, we did do it and it and there are compromises. A custom security
extension is painful but is probably most secure. The simplest way for an
Internet solution is to -
1. Permit "annonymous" accesss to a low privelege account on the
ReportServer virtual directory.
2. Everything must be https and you will need a registered FQDN server side
cert.
3. However, one still needs to authenticate the user which needs to be done
by your application. Otherwise you have to go custom+Forms authentication or
handing out network logins .. ugh!
4. In order to secure reports, we used a sessionkey generated by our app and
passed it as a hidden parameter from an embedded IE browser using url access.
5. The RDLs execute SPs and the session check is done at this point. With a
custom solution one would do the check prior to allowing access to the
ReportServer.
6. You then need to follow MBSA guidelines to lock down your IIS server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod104.asp
P.S ... the last part is nuts & you'll wonder why not have all clients
connect over IPSec and be done with it.
"Gearoid" wrote:
> ok, I know this topic has been covered COUNTLESS times in this group,
> yet the solution is still very, very hard to come by. Has anybody
> successfully published their reports (through a custom .net web
> application using URL access to the report server) to an external
> network / internet?
> If so, how... Custom security extension? Handing out network logins
> (with very restricted rights) to the report server?
> A final, solid solution would be greatly appreciated...
>