Next you will need to add that webproxy URL to your internal DNS zone pointing to the LAN IP of your exchange server. You will need to have ported your Exchange 2013 server already to 443 on your firewall and that WebProxy URL will need to be in place in your external DNS zone pointing to the WAN IP of the firewall that is ported on 443 to the Exchange 2013 server. Most, if not all of this is via Exchange PowerShell so get your command line hat on.Įxchange Online steps bit different but still mostly the same as On_Premise You will need to enable internet calendar publishing, (enabled by default in Exchange 2013, just need to set the proxy URL) to allow the external world to see that calendar via that proxy url over port 443.įor Exchange 2010 but a good writeup explaining the steps in detail. Sorry I did not fully understand your goal. Microsoft Exchange Server 2007 star 4.1.Microsoft Exchange Server 2010 star 4.2.
ROOM MAILBOX EXCHANGE 2010 UPDATE
ics calendar, but still that's no use for us as a) it doesn't update and b) the external users cannot edit. The only thing we have managed is to publish an. Secondly, how? We have tried to shared calendars externally but to no avail. These external users will also require permissions to modify/add/etc events in the room mailbox calendars.įirstly, in an Exchange 2010 environment, is this even possible? This works seamlessly for internal users.īut we now need to shared the calendars of these room mailboxes with some external users outside of our organization.
These are shared with a number of internal users in order for them to add the rooms as a "Location" when creating an event, as well as to see the room mailbox calendar. We have a few room mailboxes, one for each of our meeting rooms.
End users use OWA and Outlook 2010 to access their mailboxes. We are using Exchange 2010 on Windows Server 2008 R2.
0 kommentar(er)
