Re: Network design involving an new exchange server



Are you asking if you could or should create the same architecture in the
target forest? If so, I can't think of a reason why not for that size of an
installation. In much larger I can think of reasons, but for 30 workstations
it would likely be a better use of resources to put Exchange on the DC.


"Darrell" <darrell_eddy@xxxxxxxxxxxxx> wrote in message
news:eAjE5FQSFHA.3156@xxxxxxxxxxxxxxxxxxxxxxx
> What if the domain controller is also the exchange server? Can it remain
> this way or should I separate the two . This small network with a low
> usage
> Exchange server with about 30 mailboxes.
>
> Darrell
>
>
> "Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx> wrote in message
> news:eMBEIBHSFHA.356@xxxxxxxxxxxxxxxxxxxxxxx
>> If that's the case, then likely it's best to introduce the new forest and
>> Exchange server and then migrate the users/mailboxes over.
>> Something like ADMT and or PFMIGRATE would be helpful there.
>>
>> Al
>>
>>
>> "Darrell" <darrell_eddy@xxxxxxxxxxxxx> wrote in message
>> news:uEuugKFSFHA.1528@xxxxxxxxxxxxxxxxxxxxxxx
>> > Yes. The applications are a client server app and exchange services
>> >
>> > Darrell
>> > "Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx> wrote in message
>> > news:ODpginESFHA.1528@xxxxxxxxxxxxxxxxxxxxxxx
>> >> What you're talking about sounds like you want to migrate to a new
> domain
>> >> altogether.
>> >> Is that possible with your applications and such?
>> >>
>> >> Al
>> >>
>> >>
>> >> "Darrell" <darrell_eddy@xxxxxxxxxxxxx> wrote in message
>> >> news:OvhBDeCSFHA.2788@xxxxxxxxxxxxxxxxxxxxxxx
>> >> > Current Network scenario
>> >> >
>> >> >
>> >> >
>> >> > FS1: Windows 2000 running DNS, and DHCP. It also houses the user
> home
>> >> > directories and Exchange 2000 for about 30 mailboxes, and is also
>> >> > the
>> >> > Domain
>> >> > controller
>> >> >
>> >> > FS2: Windows 2000 running SQL 2000, but not taxed at all.
>> >> >
>> >> >
>> >> >
>> >> > Plan
>> >> >
>> >> >
>> >> >
>> >> > Add a new server to replace FS1, upgrade to Exchange 2003, and
> possibly
>> >> > move
>> >> > the user home directories to FS2, or a third server.
>> >> >
>> >> >
>> >> >
>> >> > The current domain is the same as the registered public domain which
> is
>> >> > company.org; and I think I should move it to something like
>> > company.local.
>> >> > So, I believe that I also need to create a new domain and move all
>> > network
>> >> > resources from company.org, to company.local.
>> >> >
>> >> >
>> >> >
>> >> > I need to some guidance as to how to accomplish all of this, or some
>> >> > additional direction or suggestions.
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>


.



Relevant Pages

  • Re: Settinng Up exchange at a second site
    ... We are looking at placing the exchange server at the second ... Add VPN access for the new exchange server and add it as an ... The main reason is for moving exchange offsite (should have put this ...
    (microsoft.public.exchange.admin)
  • Re: not seeing exchange server
    ... > whatever reason, I still can't get it to work. ... I've got the exhange ... > hosts (one the exchange server name the other our domain name) but to ... > currently using Explorer 5 to view our mail. ...
    (microsoft.public.mac.office.entourage)
  • Re: Outlook 2000 POP3 Configuration
    ... One being the exchange server is hosted offsite and ... The other reason is the users travel a great deal and they need ... > Why are you using POP3 with Exchange? ... > | Is there a configuration in Outlook that will allow user B to know ...
    (microsoft.public.office.misc)
  • Re: Using isinteg for regular maintenance
    ... reason this idea got started is that in the early days of Exchange Server, ... With online maintenance running regularly, ... databases -- and really, a little white space is not a bad thing. ...
    (microsoft.public.exchange.admin)
  • [SBS03] iPhone/Blackberry Exchange Connectivity Lost
    ... my iPhone 3G and my bosses Blackberry Storm lost connectivity ... with the exchange server for some reason. ... And now for some reason we cant connect anymore. ...
    (microsoft.public.windows.server.sbs)

Loading