Exchange 2010 Server Databases
I am looking into setting up an Exchange 2010 server for testing in my production environment. Is it possible to configure the Exchange such that it has its own database and does not replicate the users in that database to the production environment?
The idea behind this is that test users should not be seen in the Global Catalog by production users. I know there is an option to hide the user but unfortunately my customer has told me that this is not an option.
Thanks in advance
The idea behind this is that test users should not be seen in the Global Catalog by production users. I know there is an option to hide the user but unfortunately my customer has told me that this is not an option.
Thanks in advance
Hendrik Wiese
The normal setup should work fine, you just don't setup any legacy exchange. Then all should work fine without interruption.
If you install exchange 2010 into your production environment the. It remains seperate till you move a mailbox to it. You can't really seperate address lists (yet this is coming in sp2) if you want to teat exchange 2010 then make a seperate test lab in hyper-v or vmware using your ad as a copy.
ASKER
Thanks for your replies. Unfortunately seperating the test and production environments is not an option :(
I am thinking along the lines of creating a child domain. Would mailboxes created in the exchange (not moved) and the address lists remain seperate in this situation?
I am thinking along the lines of creating a child domain. Would mailboxes created in the exchange (not moved) and the address lists remain seperate in this situation?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When you say seperate domain, do you mean a completely seperate domain (as in domain x and domain y) or does this also pertain to a child domain?