I
Ian McNeice
We encountered a situation in Exchange 2003 amongst 2000
staff where for no apparent reason a particular user would
not be able to view another person's calendar even though
the correct share and permissions were etsablished. This
also occurred when sharing contacts. Even more odd was
that when viewing multiple shared calendars you can view
one users' calendar but another would provide 'folder not
found' type of message.
I have found a fix. We have a number of mailstores on our
Exchange SAN and by a process of elimination I discovered
that the sharing of Outlook resources would fail when two
users were not in the same mail store. When we moved two
users into the same mailstore, bingo - it worked. We now
ensure that when we are working with managers and their
PAs for example, that both exist in the same mailstore to
ensure all sharing activities are fine.
Clearly one should be able to share across mailstores and
I have referred this back to my own Microsoft contact for
feedback. But in the meantime if you have this kind of
issue you may wish to move some of your users around to
test the fix for yourselves.
regards
Ian
staff where for no apparent reason a particular user would
not be able to view another person's calendar even though
the correct share and permissions were etsablished. This
also occurred when sharing contacts. Even more odd was
that when viewing multiple shared calendars you can view
one users' calendar but another would provide 'folder not
found' type of message.
I have found a fix. We have a number of mailstores on our
Exchange SAN and by a process of elimination I discovered
that the sharing of Outlook resources would fail when two
users were not in the same mail store. When we moved two
users into the same mailstore, bingo - it worked. We now
ensure that when we are working with managers and their
PAs for example, that both exist in the same mailstore to
ensure all sharing activities are fine.
Clearly one should be able to share across mailstores and
I have referred this back to my own Microsoft contact for
feedback. But in the meantime if you have this kind of
issue you may wish to move some of your users around to
test the fix for yourselves.
regards
Ian