Not really....it could be anyone who has permission to write to that
calendar. This doesn't get audited. I don't think you can see any 'owner'
properties in the calendar item itself - but you might try posting in
microsoft.public.outlook to see if anyone there has an idea.
> Not really....it could be anyone who has permission to write to that
> calendar. This doesn't get audited. I don't think you can see any 'owner'
> properties in the calendar item itself - but you might try posting in
> microsoft.public.outlook to see if anyone there has an idea.
But this information must be stored somewhere, because public folder items
can have different permissions for their owner and for other people...
Massimo
--
Susan Conkey [MVP]
"Glass" <goldme...@hotmail.com> wrote in message
news:34541714-a2f2-40f7...@72g2000hsu.googlegroups.com...
It may live in the item, but that's still an Outlook thing, not an Exchange
one. It is not audited.
Description of the Calendar logging feature in Outlook
http://support.microsoft.com/kb/841615/
Microsoft Office Outlook has a feature to log calendar transactions.
Because of the Calendar logging feature, calendar transactions that
are generated by client features, by user actions, by the object
model, or by the MAPI Calendar Table are written to a log file. The
log file contains information for the following items:* Sniffer (Inbox
auto-processing)
* Free/busy publishing
* Reminders
* Calendar item actions (creation, modification, or to deletion)
* Resource booking
The main goal of the Calendar logging feature is to quickly identify
situations where, for example, meetings are inexplicably deleted from
a Calendar folder.
James Chong (MVP)
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com
On Feb 14, 12:44 pm, "Lanwench [MVP - Exchange]"
<lanwe...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote:
> Massimo <bar...@mclink.it> wrote:
> > "Lanwench [MVP - Exchange]"
> > <lanwe...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> ha scritto
> > nel messaggionews:eRs$VsxbIH...@TK2MSFTNGP06.phx.gbl...
>
> >> Not really....it could be anyone who has permission to write to that
> >> calendar. This doesn't get audited. I don't think you can see any
> >> 'owner' properties in the calendar item itself - but you might try
> >> posting in microsoft.public.outlook to see if anyone there has an
> >> idea.
>
> > But this information must be stored somewhere, because public folder
> > items can have different permissions for their owner and for other
> > people...
>
> > Massimo
>
> It may live in the item, but that's still an Outlook thing, not an Exchange
> one. It is not audited.- Hide quoted text -
>
> - Show quoted text -
"Glass" <goldme...@hotmail.com> wrote in message
news:34541714-a2f2-40f7...@72g2000hsu.googlegroups.com...
Every object has PR_CREATOR_NAME property.
Use Mdbvu32.exe and examine WHO is created object (appointment, meeting,
etc..)
"Lanwench [MVP - Exchange]"
<lanw...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:eRs$VsxbIH...@TK2MSFTNGP06.phx.gbl...
Every object has PR_CREATOR_NAME property.
Use Mdbvu32.exe and examine WHO is created object (appointment, meeting,
etc..)
"Lanwench [MVP - Exchange]"
<lanw...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
news:e3syfLz...@TK2MSFTNGP06.phx.gbl...
James Chong (MVP)
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com
On Feb 14, 3:31 pm, <no spam> wrote:
> NOT TRUE.
>
> Every object has PR_CREATOR_NAME property.
>
> Use Mdbvu32.exe and examine WHO is created object (appointment, meeting,
> etc..)
>
> "Lanwench [MVP - Exchange]"<lanwe...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message
>
> news:e3syfLz...@TK2MSFTNGP06.phx.gbl...| Massimo <bar...@mclink.it> wrote:
>
> | > "Lanwench [MVP - Exchange]"
> | > <lanwe...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> ha scritto
> | > nel messaggionews:eRs$VsxbIH...@TK2MSFTNGP06.phx.gbl...
> | >
> | >> Not really....it could be anyone who has permission to write to that
> | >> calendar. This doesn't get audited. I don't think you can see any
> | >> 'owner' properties in the calendar item itself - but you might try
> | >> posting in microsoft.public.outlookto see if anyone there has an
> | >> idea.
> | >
> | > But this information must be stored somewhere, because public folder
> | > items can have different permissions for their owner and for other
> | > people...
> | >
> | > Massimo
> |
> | It may live in the item, but that's still anOutlookthing, not an
Awesome; thanks. I've never used that. Good to know.
(but I'm still correct in that it isn't audited in logs)