'Pimping out' our Exchange Servers
Good morning.
I work for company with 15 employees and the 'higher ups' decided to implement EX2k10 internally. To keep costs down I was charged with the responsibility of implementing it; only because I knew some basic, and I do stress basic, networking and computer
skills. I'm loathed to call myself the Administrator. 1 TrainSignal follow through course later we have a functioning Exchange organisation.
We work on a small Enterprise zone that houses roughly 30 SMEs, 6 or 7 of whom have shown an interest in implementing an ExOrg but financially can not afford it.
During my course I observed the add Accepted Domains section.
My question is; can I 'pimp out' our servers to allow the same functionality for them, via OWA/Outlook Anywhere. If so, how do I create new websites in IIS, create new OWAs/ECPs etc to allow this to take place.
for example:
our AD and external domain is; toystest.com, owa being
https://mail.toystest.com/owa and the relevant SSLs relating to *.toytest.com
so, could our neighbour, AD and external name being sheepcutz.co.uk have
https://mail.sheepcutz.co.uk/owa and all relevant SSLs relating to *.sheepcutz.co.uk installed on our servers for a seamless experience?
if so, what would i need to do?
Thank you in advance
August 2nd, 2012 8:07am
Yes but it depends on your expectations. For example you can do all that with just DNS alias so that when someone goes to mail.sheeptcutz.co.uk/owa it will get redirected to mail.toytest.com, you don't have to mess with exchange. Now the mail.sheetpcutz.co.uk
will see that it got redirected to mail.toytest.com. If you don't like that than you can just create multiple DNS A records that go to the same IP for owa.
Now if you're trying to go more of a isolated hosted route than that'll take more work, GAL (address book segmentation) autodiscovery segmentation in IIS etc.
James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 2nd, 2012 10:24am
Yes but it depends on your expectations. For example you can do all that with just DNS alias so that when someone goes to mail.sheeptcutz.co.uk/owa it will get redirected to mail.toytest.com, you don't have to mess with exchange. Now the mail.sheetpcutz.co.uk
will see that it got redirected to mail.toytest.com. If you don't like that than you can just create multiple DNS A records that go to the same IP for owa.
Now if you're trying to go more of a isolated hosted route than that'll take more work, GAL (address book segmentation) autodiscovery segmentation in IIS etc.
James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
August 2nd, 2012 10:30am