Re: Exchange 2 Domains
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 19 Sep 2006 18:20:37 -0400
In news:DBF782D3-9DFC-4FA9-B4A8-219F57803FB9@xxxxxxxxxxxxx,
The Master <TheMaster@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
No, they dont have anything at the mo, peer to peer.
But they are 2 seperate entities,
What does that actually mean - from both a business and technical side?
I thought of doing a child domain
for the second site,
Why?
but was unsure if I could put the exchange
server in the child domain, if thats ok?,
I think so, but I'm not sure why you'd want to set up a child domain rather
than a single AD domain. Then again, I don't know what you meant by
"separate entities" or what the relationship is to be, between them.
can i run forest prep from
there or does that need to be at the parent domain?
I'm honestly not sure; this isn't something I've done before (with a child
domain).
Problem I have with using 2 sites is that the current domian name
would be wrong even if I could go for a joint domain name of
siteA&B.com, I dont want to go thru renaming the domain, done that
once before and its a nightmare!
Well, nobody except internal users will ever see it, so maybe it doesn't
matter. Or, you could do the rename. It is not that big a deal when you
don't have Exchange in the picture yet. I don't know what problems you
had....
The connection is a VPN.
OK
Having a second server at the exchange site is out of the question for
Budget costs unfortuntely.
They'll really need a DC/DNS box there, though.
Why is the Exchange server supposed to go into *that* location and not your
main office network? Where is the official HQ of your company? Where is IT
support? Etc. Is there some reason you can't put this server on your
network, and have them connect into it from their side? Again, they really
ought to have their own DC if it's more than a small handful of users there.
On outlook if I setup a user on one PC can they then move to a second
PC in the same site that they have never logged onto before and go
straight into Oulook, with no setup using just a roaming profile??
Yes....but you don't want a user in one location dragging a roaming profile
over a WAN link, even if the profile is small. I'm not any expert with
Exchange profile creation tools, but there may be some you can use that will
make this bit easier, at least.
if
so is that the application data part of the roaming profile?
Yes, but this isn't in Application Data.....
I Do have the option of trashing the first domain i put in, and
starting from scratch as a last resort, and TBH it would not be the
end of the world if I had too, downtime is not an issue the data is,
and thats all intact, if its a clean slate what do you recken would
be the best model as well?
I would probably either leave the AD domain name as is, or rename it.
Who is responsible for planning this stuff? Just you, or is your company's
management working on it also?
"Lanwench [MVP - Exchange]" wrote:
In news:2A865548-1C36-4CCF-A249-04C0518BE022@xxxxxxxxxxxxx,
The Master <TheMaster@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
I have a 2003 domain setup in 1 site no exchange present, I have now
found out that we are connecting to another site,
What's in that other location's network right now? If the answer is
"not much", then "2 domains" isn't really the right phrase here -
you can, and really should, have a single AD domain, with two sites.
If they've already got an AD domain, and you have an entirely
separate one, you have quite a bit more work cut out for you.
we will be
installing a new 2003 server in this site and need to install
Exchange 2003 on this server, whats the best model for this,
Much depends on the answer to the above....
connectivity is available via Broadband,
Via VPN? Leased line between the two offices?
we have approx 50 users per
site, only 1 exchange server must be installed;
No problem there, but you ought to make sure you've got another
domain controller/DC/GC in the other location where the Exchange
server will be. It should be set up in its own AD site/subnet.
We must be able to accomplish the following;
Users need to be able to log into both sites, on different PC's and
be able to access exchange from both sites via outlook 2003.
OK - if you have a single domain (or a domain trust between two
different ones) this isn't that big a deal....however, roaming
profiles will not be very useful if a user in site A goes to site B
and wants to log into the domain from there. It'll probably take
ages to log in the first time, even with a small profile.
We need Outlook to automatically setup itself up for the users, with
the server name , username etc?
That's not an Exchange thing. You'd have to use a customized profile
tool for that. Search at www.slipstick.com for 'profile' .
Any questions fire away
I think I did!
.
- Follow-Ups:
- Re: Exchange 2 Domains
- From: The Master
- Re: Exchange 2 Domains
- References:
- Re: Exchange 2 Domains
- From: Lanwench [MVP - Exchange]
- Re: Exchange 2 Domains
- From: The Master
- Re: Exchange 2 Domains
- Prev by Date: Visual C++ Error in SP2
- Next by Date: Re: Can Exchange Enterprise coexist with Exchange Standard in same org
- Previous by thread: Re: Exchange 2 Domains
- Next by thread: Re: Exchange 2 Domains
- Index(es):
Relevant Pages
|
