Default and anonymous will always be there. They have to be set one way or another. Default none means no one on the system who is an authenticated user can work with the calendar and anonymous applies to anyone outside the trusted domain.
I always use the minimum security required. Default to read or none, Anonymous to none, and add the user or security group that needs access. Permissions take sometime every now and then to go through but it works. I also uncheck visible on default and anonymous so that only users who need to see the calendar do. If they have visible check but no permissions they just see a blank calendar. From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 3:07 PM To: MS-Exchange Admin Issues Subject: RE: Public folder calendar issue That sounds just like I have it setup. Admin person is owner, the Planning group is set as Publishing Author, but Default was set to None. I've changed that to Author, and I've also removed Anonymous, which also was set to None. Joe Heaton ________________________________ From: John Cook [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 12:02 PM To: MS-Exchange Admin Issues Subject: RE: Public folder calendar issue I have similar PFs set up like this but I only have these perms - Default(Author), Myself (owner) and whatever group the calendar pertains to is given either publishing Author or if it's a small group I make them owner. The result is that anyone can add an appointment but only owners can delete them (that meaning that I have to be asked to delete something so that it does not "mysteriously" disappear when a user decides their appointment is more important) HTH John W. Cook System Administrator Partnership For Strong Families 315 SE 2nd Ave Gainesville, Fl 32601 Office (352) 393-2741 x320 Cell (352) 215-6944 Fax (352) 393-2746 MCSE, MCTS, MCP+I,CompTIA A+, N+ From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 2:52 PM To: MS-Exchange Admin Issues Subject: RE: Public folder calendar issue I went into ESM, and looked at the client permissions, and there were indeed some accounts that obviously don't exist anymore, as they were listed by the SID, instead of user name. I've cleaned that out, and still getting the issue. Joe Heaton ________________________________ From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 11:23 AM To: MS-Exchange Admin Issues Subject: RE: Public folder calendar issue Have you checked the folder for orphan permissions? I've seen those produce some pretty odd and unpredictable symptoms. ________________________________ From: Joe Heaton [mailto:[EMAIL PROTECTED] Sent: Friday, January 11, 2008 1:18 PM To: MS-Exchange Admin Issues Subject: Public folder calendar issue First off our specs: Exchange 2K3 SP2 XP Pro SP2 on clients Using Outlook 2K3 I have a public folder for a shared calendar for our Planning group. Entries are not visible, except to the person who entered them. We have set permissions to this calendar through ESM, using a security group with everyone in the Planning group set as Publishing Author. Not sure what other information is needed to help me, so please ask questions and I will try to answer them as best I can. Joe Heaton AISA Employment Training Panel 1100 J Street, 4th Floor Sacramento, CA 95814 (916) 327-5276 [EMAIL PROTECTED] ************************************************************************ ************************** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ************************************************************************ ************************** CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
