Yea mine too.

The suggestion wasn't all that wrong. The pf permissions were all
correct and the next logical step was the last one I listed originally
and Jonathan "echoed". That was to delete/purge the mb and recreate it
and import the pst. That worked.

I've never had to use pfdavadmin before. Go figure.

Thanks Sean.

 

Stu where is the BBQ list signup?

 

From: Sean Martin [mailto:seanmarti...@gmail.com] 
Sent: Friday, January 07, 2011 3:58 PM
To: MS-Exchange Admin Issues
Subject: Re: user cannot see public folders anymore

 

If Michael's mind is great, mine is just so-so...

 

Just a bummer the suggestion didn't appear to help solve the problem.

 

- Sean

On Fri, Jan 7, 2011 at 12:29 PM, Raper, Jonathan - Eagle
<jra...@eaglemds.com> wrote:

There's an echo in here...

 

In here....

 

Great minds think alike!

Jonathan L. Raper, A+, MCSA, MCSE
Technology Coordinator
Eagle Physicians & Associates, PA
jra...@eaglemds.com
www.eaglemds.com 

________________________________

From: Sean Martin [mailto:seanmarti...@gmail.com] 
Sent: Friday, January 07, 2011 4:01 PM 


To: MS-Exchange Admin Issues

Subject: Re: user cannot see public folders anymore 

 

Have you looked at PFDAVAdmin to verify permissions?

 

- Sean

On Fri, Jan 7, 2011 at 11:50 AM, Eldridge, Dave <d...@parkviewmc.com>
wrote:

2003 sp2 running on 2003 enterprise server

I just finished moving exchange to new hardware and we removed the old
server yesterday. I have one user that cannot see the public folders.

I have tried deleting and reconnecting the mailbox. 

I have deleted and reconnected same mailbox to a new user.

I have tried using owa.

Neither works.  I get unable to expand folders.

 

My next step is to pst his mailbox and delete it again but create a
brand new mailbox and import the pst in.

Other than this last step any other ideas?

Thanks

 

dave

This e-mail contains the thoughts and opinions of the sender and does
not represent official Parkview Medical Center policy.

This communication is intended only for the recipient(s) named above,
may be confidential and/or legally privileged: and, must be treated as
such in accordance with state and federal laws. If you are not the
intended recipient, you are hereby notified that any use of this
communication, or any of its contents, is prohibited. If you have
received this communication in error, please return to sender and delete
the message from your computer system.{token}

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

 

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

 

________________________________

Any medical information contained in this electronic message is
CONFIDENTIAL and privileged. It is unlawful for unauthorized persons to
view, copy, disclose, or disseminate CONFIDENTIAL information. This
electronic message may contain information that is confidential and/or
legally privileged. It is intended only for the use of the individual(s)
and/or entity named as recipients in the message. If you are not an
intended recipient of this message, please notify the sender immediately
and delete this material from your computer. Do not deliver, distribute
or copy this message, and do not disclose its contents or take any
action in reliance on the information that it contains.

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

 

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

Reply via email to