> Why is it that the users do not share their outlook calendar, yet if
> you click on open a shared calendar and select a user in the exchange
> list, the non shared calendar opens.
> Yet all settings in outlook are for not share, removed all users
> (default cannot be removed but 'visible' is removed) Everything
> checks out as not shared.
> Its on SBS/Exchange 2003 and Outlook 2007. In the tools menu of
> outlook there is no delegates and no published calendars.
>
> Related to ExMerge or Blackberry that did some changes in the
> permissions?
>
> I have googled and some have seen this in 2006, 2007 and so on but it
> looks like
> there is no answer???!!!
>
> Has to be something somewhere on the server side...
>
> I have checked some permissions on the exchange side and it looks
> like there is some permissions inherited from parent that is set to
> everyone and anonymous to 'read'. Is this ok? Should I change this?
>
> Thanks to all

"Lanwench [MVP - Exchange]" wrote:

> Paul <P***@discussions.microsoft.com> wrote:
> > Why is it that the users do not share their outlook calendar, yet if
> > you click on open a shared calendar and select a user in the exchange
> > list, the non shared calendar opens.
> > Yet all settings in outlook are for not share, removed all users
> > (default cannot be removed but 'visible' is removed) Everything
> > checks out as not shared.
> > Its on SBS/Exchange 2003 and Outlook 2007. In the tools menu of
> > outlook there is no delegates and no published calendars.
> >
> > Related to ExMerge or Blackberry that did some changes in the
> > permissions?
> >
> > I have googled and some have seen this in 2006, 2007 and so on but it
> > looks like
> > there is no answer???!!!
> >
> > Has to be something somewhere on the server side...
> >
> > I have checked some permissions on the exchange side and it looks
> > like there is some permissions inherited from parent that is set to
> > everyone and anonymous to 'read'. Is this ok? Should I change this?
> >
> > Thanks to all
>
> Someone  has definitely done something bad to the permissions.
>
>
> First, find out what groups these users belong to.
> See whether you can open the full mailbox (not just the inbox) in the
> advanced properties of the Exchange server service in Outlook (open
> additional mailboxes)
> See whether you can send as another user.
>
> Knowledgebase article 262054 explains how to grant full mailbox access, but
> it should also be helpful in telling you where to look for where access is
> already granted...be careful, as you don't want to accidentally remove
> anything that *should* be there.
>
> Also see http://support.microsoft.com/?scid=kb;en-us;326061
>
>
>

>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Paul <P***@discussions.microsoft.com> wrote:
>>> Why is it that the users do not share their outlook calendar, yet if
>>> you click on open a shared calendar and select a user in the
>>> exchange list, the non shared calendar opens.
>>> Yet all settings in outlook are for not share, removed all users
>>> (default cannot be removed but 'visible' is removed) Everything
>>> checks out as not shared.
>>> Its on SBS/Exchange 2003 and Outlook 2007. In the tools menu of
>>> outlook there is no delegates and no published calendars.
>>>
>>> Related to ExMerge or Blackberry that did some changes in the
>>> permissions?
>>>
>>> I have googled and some have seen this in 2006, 2007 and so on but
>>> it looks like
>>> there is no answer???!!!
>>>
>>> Has to be something somewhere on the server side...
>>>
>>> I have checked some permissions on the exchange side and it looks
>>> like there is some permissions inherited from parent that is set to
>>> everyone and anonymous to 'read'. Is this ok? Should I change this?
>>>
>>> Thanks to all
>>
>> Someone  has definitely done something bad to the permissions.
>>
>>
>> First, find out what groups these users belong to.
>> See whether you can open the full mailbox (not just the inbox) in the
>> advanced properties of the Exchange server service in Outlook (open
>> additional mailboxes)
>> See whether you can send as another user.
>>
>> Knowledgebase article 262054 explains how to grant full mailbox
>> access, but it should also be helpful in telling you where to look
>> for where access is already granted...be careful, as you don't want
>> to accidentally remove anything that *should* be there.
>>
>> Also see http://support.microsoft.com/?scid=kb;en-us;326061

"Lanwench [MVP - Exchange]" wrote:

> Paul <P***@discussions.microsoft.com> wrote:
> > I think I have found something which is not great...
> >
> > It looks like this is 'builtin' I have tested this on another site
> > and it is the same: a user can open somebody else calendar and add
> > something to it even if it is not shared. The user can even open the
> > other user's inbox !
>
> This is not the default.
> >
> > Can somebody else replicate this ! I am sure you can!
>
> Nope. As said it's not the default.  I promise.
> >
> > What I have in common is using exmerge, does this program changes
> > permissions to extract?
>
> The program doesn't change anything. But you have to set up an account to
> run Exmerge with, or you have to manually change permissions to allow your
> logged in account to run. If someone didn't do that correctly you could
> definitely see the results you're seeing.
>
> Check the KB article I referred to - as mentioned, it shows you how to add
> permissions - but you should be able to see what permissions were already
> added. It's not fun to hunt this stuff down. but hopefully it's just a group
> membership thing.
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> Paul <P***@discussions.microsoft.com> wrote:
> >>> Why is it that the users do not share their outlook calendar, yet if
> >>> you click on open a shared calendar and select a user in the
> >>> exchange list, the non shared calendar opens.
> >>> Yet all settings in outlook are for not share, removed all users
> >>> (default cannot be removed but 'visible' is removed) Everything
> >>> checks out as not shared.
> >>> Its on SBS/Exchange 2003 and Outlook 2007. In the tools menu of
> >>> outlook there is no delegates and no published calendars.
> >>>
> >>> Related to ExMerge or Blackberry that did some changes in the
> >>> permissions?
> >>>
> >>> I have googled and some have seen this in 2006, 2007 and so on but
> >>> it looks like
> >>> there is no answer???!!!
> >>>
> >>> Has to be something somewhere on the server side...
> >>>
> >>> I have checked some permissions on the exchange side and it looks
> >>> like there is some permissions inherited from parent that is set to
> >>> everyone and anonymous to 'read'. Is this ok? Should I change this?
> >>>
> >>> Thanks to all
> >>
> >> Someone  has definitely done something bad to the permissions.
> >>
> >>
> >> First, find out what groups these users belong to.
> >> See whether you can open the full mailbox (not just the inbox) in the
> >> advanced properties of the Exchange server service in Outlook (open
> >> additional mailboxes)
> >> See whether you can send as another user.
> >>
> >> Knowledgebase article 262054 explains how to grant full mailbox
> >> access, but it should also be helpful in telling you where to look
> >> for where access is already granted...be careful, as you don't want
> >> to accidentally remove anything that *should* be there.
> >>
> >> Also see http://support.microsoft.com/?scid=kb;en-us;326061
>
>
>
>

> "Lanwench [MVP - Exchange]" wrote:
>
>> Paul <P***@discussions.microsoft.com> wrote:
>>> I think I have found something which is not great...
>>>
>>> It looks like this is 'builtin' I have tested this on another site
>>> and it is the same: a user can open somebody else calendar and add
>>> something to it even if it is not shared. The user can even open the
>>> other user's inbox !
>>
>> This is not the default.
>>>
>>> Can somebody else replicate this ! I am sure you can!
>>
>> Nope. As said it's not the default.  I promise.
>>>
>>> What I have in common is using exmerge, does this program changes
>>> permissions to extract?
>>
>> The program doesn't change anything. But you have to set up an
>> account to run Exmerge with, or you have to manually change
>> permissions to allow your logged in account to run. If someone
>> didn't do that correctly you could definitely see the results you're
>> seeing.
>>
>> Check the KB article I referred to - as mentioned, it shows you how
>> to add permissions - but you should be able to see what permissions
>> were already added. It's not fun to hunt this stuff down. but
>> hopefully it's just a group membership thing.
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> Paul <P***@discussions.microsoft.com> wrote:
>>>>> Why is it that the users do not share their outlook calendar, yet
>>>>> if you click on open a shared calendar and select a user in the
>>>>> exchange list, the non shared calendar opens.
>>>>> Yet all settings in outlook are for not share, removed all users
>>>>> (default cannot be removed but 'visible' is removed) Everything
>>>>> checks out as not shared.
>>>>> Its on SBS/Exchange 2003 and Outlook 2007. In the tools menu of
>>>>> outlook there is no delegates and no published calendars.
>>>>>
>>>>> Related to ExMerge or Blackberry that did some changes in the
>>>>> permissions?
>>>>>
>>>>> I have googled and some have seen this in 2006, 2007 and so on but
>>>>> it looks like
>>>>> there is no answer???!!!
>>>>>
>>>>> Has to be something somewhere on the server side...
>>>>>
>>>>> I have checked some permissions on the exchange side and it looks
>>>>> like there is some permissions inherited from parent that is set
>>>>> to everyone and anonymous to 'read'. Is this ok? Should I change
>>>>> this?
>>>>>
>>>>> Thanks to all
>>>>
>>>> Someone  has definitely done something bad to the permissions.
>>>>
>>>>
>>>> First, find out what groups these users belong to.
>>>> See whether you can open the full mailbox (not just the inbox) in
>>>> the advanced properties of the Exchange server service in Outlook
>>>> (open additional mailboxes)
>>>> See whether you can send as another user.
>>>>
>>>> Knowledgebase article 262054 explains how to grant full mailbox
>>>> access, but it should also be helpful in telling you where to look
>>>> for where access is already granted...be careful, as you don't want
>>>> to accidentally remove anything that *should* be there.
>>>>
>>>> Also see http://support.microsoft.com/?scid=kb;en-us;326061