Re: Ask your opinion on this
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Jan 2008 23:25:18 -0500
John <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Thanks for your help.
Sorry for the confusion.
The remote site does not access any resource from this company.
Well, if there's going to be a DC there on your domain, you'll have to set
up some form of connectivity - leased line or VPN - between. So, they will
be accessing resources!
They
just manage and set up exchange server and second domain controller
for this company as there is no technician at this company. (there
is only one DC at this company now) Will this situation still follow
your suggestion?
I can't really answer that. I think it's more common for a company to
consolidate its servers wherever its headquarters is, which is usually where
the IT support is. Your company may not operate this way.
Should I purchase small business server?
You might look into it, but you will still need IT support....and you may
have a tough time integrating it into an existing domain. It can be done,
but it isn't uncomplicated. Try posting in
microsoft.public.windows.server.sbs. for more SBS help.
I can not
install exchange on DC and it's not supported?
It is supported, but is not recommended.
Thank you.
"Lanwench [MVP - Exchange]" wrote:
John <John@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
This company has very small environment (currently 6 people) with
one domain controller windows 2003 standard. Now, they get remote
site to host their exchange server and second domain controller in
remote site. Instead of getting two physical boxes at remote site,
I think to purchase one box with enough RAM and disk spaces.
Install exchange 2003 on it. and inside exchange 2003 server,
create one virtual server or virtual PC for secon domain
controller. Any suggestions or concerns?Should I create two
virtual for exchange and domain controller?
Thank you.
I'd reverse that, if I were going to do it at all. You could run
Exchange in a virtual server on your DC, though, if the box had
sufficient firepower. Personally, as decent server hardware isn't
that expensive, and you'd have to buy a license for Windows &
Exchange anyway, I'd put it on two boxes.
I do also wonder why you aren't putting Exchange in your main office,
putting only a low-end server as a DC in the remote office, & having
the remote users connect to Exchange using RPC over HTTP . Even if
the remote office will have more users in it, it seems to make more
sense to consolidate your backups/etc in your company's
headquarters. Perhaps I misunderstand your setup.
.
- References:
- Re: Ask your opinion on this
- From: Lanwench [MVP - Exchange]
- Re: Ask your opinion on this
- Prev by Date: Re: AD 2003 time synchronization from linux ntp server
- Next by Date: Re: Old, Deleted Printers Still Appear in Printers and Faxes Menu on Clients
- Previous by thread: Re: Ask your opinion on this
- Next by thread: Re: Ask your opinion on this
- Index(es):
Relevant Pages
|
