Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

who created an appoitment in a public caladner?

0 views
Skip to first unread message

Glass

unread,
Feb 14, 2008, 5:48:52 AM2/14/08
to
Is there a way of finding this info out?

Lanwench [MVP - Exchange]

unread,
Feb 14, 2008, 9:44:32 AM2/14/08
to
Glass <goldme...@hotmail.com> wrote:
> Is there a way of finding this info out?

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.


Massimo

unread,
Feb 14, 2008, 11:56:23 AM2/14/08
to
"Lanwench [MVP - Exchange]"
<lanw...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> ha scritto nel
messaggio news: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

Susan

unread,
Feb 14, 2008, 12:29:43 PM2/14/08
to
if you change the "view" on the calendar to "by category", then add the
"From" field, you can see who created the item...

--
Susan Conkey [MVP]

"Glass" <goldme...@hotmail.com> wrote in message
news:34541714-a2f2-40f7...@72g2000hsu.googlegroups.com...

Lanwench [MVP - Exchange]

unread,
Feb 14, 2008, 12:44:23 PM2/14/08
to

It may live in the item, but that's still an Outlook thing, not an Exchange
one. It is not audited.


Jamestechman

unread,
Feb 14, 2008, 3:09:12 PM2/14/08
to
Outlook thing.


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 -

nospam

unread,
Feb 14, 2008, 3:21:01 PM2/14/08
to
Every object has PR_CREATOR_NAME property. This is a MAPI property. All
objects also has a PR_LAST_MODIFIER_NAME property. See thise link
http://support.microsoft.com/kb/253291


"Glass" <goldme...@hotmail.com> wrote in message
news:34541714-a2f2-40f7...@72g2000hsu.googlegroups.com...

nospam

unread,
Feb 14, 2008, 3:30:57 PM2/14/08
to
NOT TRUE.

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...

nospam

unread,
Feb 14, 2008, 3:31:35 PM2/14/08
to
NOT TRUE.

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...

Jamestechman

unread,
Feb 14, 2008, 4:38:39 PM2/14/08
to
Yes indeed!


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

Lanwench [MVP - Exchange]

unread,
Feb 15, 2008, 8:43:20 AM2/15/08
to
no spam wrote:
> NOT TRUE.
>
> Every object has PR_CREATOR_NAME property.
>
> Use Mdbvu32.exe and examine WHO is created object (appointment,
> meeting, etc..)

Awesome; thanks. I've never used that. Good to know.

(but I'm still correct in that it isn't audited in logs)

0 new messages