Step by Step on how to setup Exchange 2003 for Hosting

We have 4 small sister (10- 15 employees per ) company and would like to have them all on the same Exchange server. I need help with detail step by step on how to setup 1 Exchange 2003/Windows Server 2003 with 4 separate company domain. They should NOT be able to see each other and would like to use RPC over HTTP. I tried following the following instructions but each company is still able to view each other in the address book. I'm sure it's just something simple that I am doing incorrectly.

http://www.msexchange.org/tutorials/Shared_Hosting_Exchange_2003_Part1.html
http://www.msexchange.org/tutorials/Shared-Hosting-Exchange-2003-Part2.html

Also, I would like to keep each company on there own mail storage too and tighten any security hole from SPAM, SPOOFING and etc. One more thing can I use 1 SSL certificate for all 4 companies?

Thanks!
Tech_Me_MoreAsked:
Who is Participating?
 
SurajCommented:
Remove the allow inheritable permission from the All Global Address List Container from the advanced box and then select copy. Remove EveryOne, Anonymous Logon and authenticated users from the permissions.

Then add the authenticated users and allow only to list the contents.

You have to do the same security changes to the Offline Address Book container too.

Once this is done you would have to create new offline address book and the global address lists and allow listing contents for the global address list and the offline address book for the particular company.


Thanks,
x-sam
0
 
MrMintanetCommented:
I sincerely suggest that you split this question up.  Your question is so complicated, it would hardly be practical to have someone provide an answer.  I'll give what I can here... but I don't think you will find it of much use.

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21204755.html
0
 
MesthaCommented:
What you are talking about is address list segregation.
Microsoft no longer support that on Exchange 2003 except when using their own hosting solution due to its very high failure rate - permissions etc. The Microsoft articles on the process have been pulled etc. Your best option would be to move to Exchange 2007 where Microsoft have provided a procedure which they actively support.

When it comes to SSL certificates, that is a per server thing, not domain, so the same SSL certificate can be used to support all users on the machine.

Simon.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Tech_Me_MoreAuthor Commented:
I'm going redo the question(s) so it's only 1 that I'm asking as soon as I get back to the office.
0
 
Tech_Me_MoreAuthor Commented:
I'm not sure how to edit my original question... so I will update it here. I followed the following documents

http://www.msexchange.org/tutorials/Shared_Hosting_Exchange_2003_Part1.html
http://www.msexchange.org/tutorials/Shared-Hosting-Exchange-2003-Part2.html

and created 4 company domain on 1 exchange server. I'm having problem with part2 and not able to hide each company from each other. What am I missing?
0
 
Tech_Me_MoreAuthor Commented:
Hi! Sorry I have been really busy and hopefully have some time next week to try some recommendations!

Thanks!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.