need to keep an existing public calendar, but user is leaving, is it possible?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dogbyte - 16 May 2007 14:09 GMT

i have an employee that is leaving in a couple of days, but we need to
keep her public calendar that alot of other folks use in their
office. Is there a way i can some how extract her calendar and keep
it separate from a user account in active directory? we are running
2003 exchange server and im going to have to delete her account when
she quits. everyone has alot of input on her calendar, she was the
main receptionist and made their appointments as she received them by
phone. i need something just like that but not attached to a user
account, so when the new person takes over, and maybe quits one day,
we wont have to do this all over again.

Reply to this Message

Dogbyte - 16 May 2007 14:30 GMT

> i have an employee that is leaving in a couple of days, but we need to
> keep her public calendar that alot of other folks use in their
[quoted text clipped - 6 lines]
> account, so when the new person takes over, and maybe quits one day,
> we wont have to do this all over again.

sorry i guess it takes some time to post the message

Reply to this Message

jimmuh - 16 May 2007 16:35 GMT

I'm no expert, but it seems that it makes more sense just to import the data
into the replacement person's account (or into the account of someone else
you want to maintain the calendar). AFAIK there's no way to have a calendar
that isn't "owned" by a user account. It's not like it would be very hard to
do this, even if you have a high turnover rate in that job.

> > i have an employee that is leaving in a couple of days, but we need to
> > keep her public calendar that alot of other folks use in their
[quoted text clipped - 8 lines]
>
> sorry i guess it takes some time to post the message

Reply to this Message

Dogbyte - 17 May 2007 14:03 GMT

> I'm no expert, but it seems that it makes more sense just to import the data
> into the replacement person's account (or into the account of someone else
> you want to maintain the calendar). AFAIK there's no way to have a calendar
> that isn't "owned" by a user account. It's not like it would be very hard to
> do this, even if you have a high turnover rate in that job.

yeah i just didnt know if there was a way to have it set as fully
public, where no one owned it, i thought i'd heard of people moving a
calendar to the public store folder on the exchange server.

Reply to this Message

jimmuh - 17 May 2007 16:17 GMT

Not that I know of, but my experience with Exchange is very slight. I run
some domains, but none of them do e-mail at all. They are for controlling
manufacturing processes. I'll watch this thread to see if someone comes up
with a bright idea. but, if I were you, I'd post in an Exchange Server
newsgroup. I'm sure you'll get a definitive answer there.

> > I'm no expert, but it seems that it makes more sense just to import the data
> > into the replacement person's account (or into the account of someone else
[quoted text clipped - 5 lines]
> public, where no one owned it, i thought i'd heard of people moving a
> calendar to the public store folder on the exchange server.

Reply to this Message

Rate this thread: