|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Exchange Server MonitoringI have been reading a lot of conflicting information regarding Exchange Server programming and I am soliciting anybody who can point me in the correct direction. We want to create an application that can monitor message throughput and exchange server loading for 2003 & 2007. The goal is the use C++ COM as the preferred development platform. We want to capture the following items daily for the preliminary release. 1. Number of messages sent by the exchange server. 2. Number of messages received by the exchange server 3. Total size of received messages. 4. Total size of sent messages. I have read so much information (some conflicting) about how to do this efficiently and I was wondering if anybody can point me in the correct direction. I am familiar with OLEDB, MAPI, COM, C++ and all other window architecture. This application must work for Exchange Server 2003 & 2007. This application will be used by network administrators. We have a requirement of no .NET. Thanks, Tom If you have enabled Message Tracking on a Exchange server then on Exchange
2003 you can use WMI to query the Message tracking logs via Exchange_MessageTrackingEntry http://msdn.microsoft.com/en-us/library/aa143739(EXCHG.65).aspx or on 2007 you dont have the Exchange WMI class so you need to using the get-messagetrackinglogs Exchange Management Shell Cmdlets get-messagetrackinglogs http://technet.microsoft.com/en-us/library/aa997573.aspx. To make these queries the user will need to have been delegate at least view only admin rights. The logs files are a simple text format although the format differs between 2003 and 2007 but you can still read the raw log files. To use the log file affectedly you need to understand the different events that are logged eg http://support.microsoft.com/kb/821905. Cheers Glen Show quoteHide quote "Tom" <t**@gigasoftdevelopment.com> wrote in message news:uIusqLE6JHA.1416@TK2MSFTNGP04.phx.gbl... > Hello, > > I have been reading a lot of conflicting information regarding Exchange > Server programming and I am soliciting anybody who can point me in the > correct direction. > > We want to create an application that can monitor message throughput and > exchange server loading for 2003 & 2007. The goal is the use C++ COM as > the > preferred development platform. We want to capture the following items > daily > for the preliminary release. > > 1. Number of messages sent by the exchange server. > 2. Number of messages received by the exchange server > 3. Total size of received messages. > 4. Total size of sent messages. > > I have read so much information (some conflicting) about how to do this > efficiently and I was wondering if anybody can point me in the correct > direction. > > I am familiar with OLEDB, MAPI, COM, C++ and all other window > architecture. > > This application must work for Exchange Server 2003 & 2007. > > This application will be used by network administrators. > > We have a requirement of no .NET. > > Thanks, > Tom > > > Hi Glen,
Thank you very much for your response. That is definitley what I was looking for. Regards, Tom Show quoteHide quote "Glen Scales [MVP]" <gsca***@outlookexchange.com> wrote in message news:eHlX70V6JHA.1092@TK2MSFTNGP06.phx.gbl... > If you have enabled Message Tracking on a Exchange server then on Exchange > 2003 you can use WMI to query the Message tracking logs via > Exchange_MessageTrackingEntry > http://msdn.microsoft.com/en-us/library/aa143739(EXCHG.65).aspx or on 2007 > you dont have the Exchange WMI class so you need to using the > get-messagetrackinglogs Exchange Management Shell Cmdlets > get-messagetrackinglogs > http://technet.microsoft.com/en-us/library/aa997573.aspx. To make these > queries the user will need to have been delegate at least view only admin > rights. The logs files are a simple text format although the format > differs between 2003 and 2007 but you can still read the raw log files. To > use the log file affectedly you need to understand the different events > that are logged eg http://support.microsoft.com/kb/821905. > > Cheers > Glen > > > > "Tom" <t**@gigasoftdevelopment.com> wrote in message > news:uIusqLE6JHA.1416@TK2MSFTNGP04.phx.gbl... >> Hello, >> >> I have been reading a lot of conflicting information regarding Exchange >> Server programming and I am soliciting anybody who can point me in the >> correct direction. >> >> We want to create an application that can monitor message throughput and >> exchange server loading for 2003 & 2007. The goal is the use C++ COM as >> the >> preferred development platform. We want to capture the following items >> daily >> for the preliminary release. >> >> 1. Number of messages sent by the exchange server. >> 2. Number of messages received by the exchange server >> 3. Total size of received messages. >> 4. Total size of sent messages. >> >> I have read so much information (some conflicting) about how to do this >> efficiently and I was wondering if anybody can point me in the correct >> direction. >> >> I am familiar with OLEDB, MAPI, COM, C++ and all other window >> architecture. >> >> This application must work for Exchange Server 2003 & 2007. >> >> This application will be used by network administrators. >> >> We have a requirement of no .NET. >> >> Thanks, >> Tom >> >> >> > >
Other interesting topics
Using Webdav for attachments in 2007
Migrate issues Event sink from Exchange 2003 Exchange 2007 Exch2003 - Add a public delegate? Mailbox Movement Code Changing Mail Received Date via EWS Extarcting email attachmnets from exchange exchange webservices (EWS) authentication problem Adddelegate with EWS Managed API Re: MAPI33 - a great blow to exchange development Re: MAPI33 - a great blow to exchange development |
|||||||||||||||||||||||