Link to home
Start Free TrialLog in
Avatar of rdavis104
rdavis104

asked on

Domain Rename

We have the old problem of a different outside domain name vs inside name.  It wasnt a problem until we migrated to Exchange2007.  Now we get the nasty certificate error when starting Outlook and the MOC client.  Our environment is small and includes 2 Windows 2003 domain controllers, 2 DNS servers, Exchange 2007, Exchange 2003 (not yet decommissioned and sitting on a domain controller and the global catalog), OCS2007 R2 (not yet deployed), Sharepoint WSS 3.0, SQL 2003&&.  Our inside domain name belongs to another company so we cannot obtain a cert from a commercial CA.  
My questions are:
What are our options besides performing a domain rename operation?
If a rename is the only option can we migrate Exchange users back to 2003 even though the server is on a domain controller?  I understand Exchange 2007 does not support the rename.  What are our options with OCS?  How will this affect other applications  CRM40, Great Plains etc?
We have downloaded the rename tools and documentation and are in the process of creating a test lab.  Still, I read horror stories about the renaming process.
Avatar of Exchange_Geek
Exchange_Geek
Flag of India image

"We have the old problem of a different outside domain name vs inside name.  It wasnt a problem until we migrated to Exchange2007"

This is very much normal in scenario across the globe - there should not be a problem in it.

"Our inside domain name belongs to another company so we cannot obtain a cert from a commercial CA"

Ideally, if your internal domain is not exposed to outside internet world - have your internal root CA create certificates to be installed on all CAS servers and Outlook and MOC clients will download the same information - if it cannot download dispatch certificates and have the users installed locally on their boxes.

Problem, would begin if users start accessing information outside their domain - such as availability service (Rpc over Http) from OL and MOC.

Why are you thinking on terms of renaming the entire AD domain - remember this task is not simply and would have its own complications.


Avatar of rdavis104
rdavis104

ASKER

One of the reasons we are using OCS is for the development of a new service product for our customers who will be using MOC outside the corporate firewall.  We didnt want them to see the certificate warning so we purchased a UC cert from a commercial CA.
I am trying to have a better understanding of certificates.  We did generate an internal certificate from our CA and applied to the servers but we still get the certificate errors.  Should this have resolved our internal Outlook and MOC issues?  
From what I have been reading if we perform the rename we will need to uninstall Exchange 2007 and our entire OCS system prior to pulling the trigger, do the rename and reinstall everything.  If there is any option other than the rename I will gladly try it.
I think we have decided to go another direction with our solution but in the long run will be the best option.  We are looking into creating a whole new AD forest \ domain and rebuild the Exchange and OCS environment.  We are pretty confident in the OCS setup but I am concerned about the Exchange users.  What is the best way to move\copy Exchange 2007 users from one domain to another?  In the old days we used exmerge.  Is it still around in 2007?
ASKER CERTIFIED SOLUTION
Avatar of Exchange_Geek
Exchange_Geek
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial