A
AdminKen
I have noticed an interesting peculiarity in Outlook 2003 using RPC over
HTTP. I have Outlook 2003 on two different computers. One computer is in a
office and is in a domain (not the same domain as the Exchange server), the
other computer is in a home and is not in a domain. Both are running XP Pro
and have same service packs and Q331320. Both are set to connect to the same
remote Exchange 2003 server (2K3 SBS) using RPC over HTTP.
Here's the big difference, the Outlook 2003 on the computer in a domain
(again, a different domain than the remote Exchange server) has the ability
to see the permissions tab on objects like Calendars, Mailboxes, Contacts,
Public folders etc. The Outlook 2003 at home (not in any domain) does not
show the permissions tab on any items (as in... right-click > Properties >
Permissions). So sharing my calendar, contacts etc.from my home computer is
not possible.
My best guess is that has something to do with the domain /non-domain
situation, missing AD attributes or something like that. (though it may be
unrelated and just a bug on my home pc)
What gives? Is this a known limitation? How can I give my home PC the
ability to set Permissions without joining a domain?
Ken
HTTP. I have Outlook 2003 on two different computers. One computer is in a
office and is in a domain (not the same domain as the Exchange server), the
other computer is in a home and is not in a domain. Both are running XP Pro
and have same service packs and Q331320. Both are set to connect to the same
remote Exchange 2003 server (2K3 SBS) using RPC over HTTP.
Here's the big difference, the Outlook 2003 on the computer in a domain
(again, a different domain than the remote Exchange server) has the ability
to see the permissions tab on objects like Calendars, Mailboxes, Contacts,
Public folders etc. The Outlook 2003 at home (not in any domain) does not
show the permissions tab on any items (as in... right-click > Properties >
Permissions). So sharing my calendar, contacts etc.from my home computer is
not possible.
My best guess is that has something to do with the domain /non-domain
situation, missing AD attributes or something like that. (though it may be
unrelated and just a bug on my home pc)
What gives? Is this a known limitation? How can I give my home PC the
ability to set Permissions without joining a domain?
Ken