Exchange 2007+Naming and domain names.

From: jj@xxxxxxxxxxxx
Date: Tue, 25 Mar 2008 21:53:39 -0400

Hello were embarking on installing Exchange 2007.

Our domain controller has a active directory name of
"companyname.local" Its a internal domain running windows
2008 server.

When Exchange is installed and exchange extends the AD Schema will
it be possible for our Outlook clients to log into exchange using our
real domain name and not the domain name of our internal AD server.

For example currently users log into our internal domain with

username@xxxxxxxxxxxxxxxxx from their desktop pc's

When exchange is deployed I would like our Outlook users to log in
to outlook using

Username@xxxxxxxxxxxxxxx

and not username@xxxxxxxxxxxxxxxxx

Is it possible to do this or will I have to use the same naming for
exchange as the active directory enabled domain name..

Thanks JJ

.

Follow-Ups:
- Re: Exchange 2007+Naming and domain names.
  - From: Ed Crowley [MVP]

Prev by Date: Re: created exchange box without creating a/d account
Next by Date: Re: Publish OWA help
Previous by thread: created exchange box without creating a/d account
Next by thread: Re: Exchange 2007+Naming and domain names.
Index(es):
- Date
- Thread

Relevant Pages

Re: Connection to a SAMBA Active Directory
... Keep in mind that you're trying to setup a NT4 style trust ... if you setup the Exchange as a resource forest model, ... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ...
(microsoft.public.exchange.connectivity)
Re: Connection to a SAMBA Active Directory
... domain and the Exchange server in another domain will work. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ...
(microsoft.public.exchange.connectivity)
Re: Home Network Dilemma
... You must understand Active Directory first, in order to implement Exchange. ... Matter of fact, Exchange must alter Active Directory prior to installation, to accomodate the changes. ... On top of that, an understanding of DNS is required, because AD will not work if DNS is not implemented properly for its internal use only, and on top of that, an understanding of DNS on the internet is required in order to manipulate public records so others in the world can 'find' your mail server on your network. ...
(microsoft.public.windows.server.networking)
Re: Connection to a SAMBA Active Directory
... I built a new Windows 2003 Server in a brand new domain. ... I am able to define a 2 way Realm trust using the Active Directory ... There is a bit of confusing on the SAMBA side. ... Active Directory components but not enough to deploy Exchange. ...
(microsoft.public.exchange.connectivity)
Re: Configuration / Protocols Missing
... and I removed the E55 server. ... the ADCConfigCheck deployment tool (Check Exchange ... The tool searches Active Directory by ... >> its endpoints are the Site Replication Service and a global catalog ...
(microsoft.public.exchange.setup)