Re: Removing Member Server?
- From: v-amanwa@xxxxxxxxxxxxxxxxxxxx (Amanda Wang [MSFT])
- Date: Thu, 16 Jun 2005 07:48:30 GMT
Hi John,
Thanks for your post.
For your current situation, you have performed DCPromo, transferred roles,
removed DNS, WINS, DHCP, RRAS and now it is only a member file server with
no shared directories or DFS shares on this original server. Please don't
worry about this and you can go head to just unplug it from the network.
In addition, I would like to explain why Exchange is not recommended to be
run on a DC.
The main reasons are as following:
The only valid business cases for installing Exchange Server on a DC that I
have ever encountered are (1) budget limitations in an environment too
large to use Microsoft Small Business Server, and (2) when deploying
Exchange servers in locations where reliable WAN links are difficult or
impossible to purchase and implement. Exchange 2003 on a domain controller
is supported by Microsoft as a valid configuration, provided you adhere to
the following restrictions and limitations:
?¡è Exchange and Active Directory are both resource-intensive applications.
There are serious performance implications that result from running them
both on the same system.
?¡è The domain controller must also be a global catalog server.
?¡è Several directory-related components of Exchange 2003, namely DSAccess,
DSProxy and the message categorizer will not load-balance or failover to
any other domain controller or global catalog server.
?¡è You should not take advantage of the /3GB switch in Windows, as it
could cause Exchange to consume all available memory, effectively choking
out Active Directory.
?¡è System shutdown will take longer due to the order in which components
are automatically shutdown. This problem can be overcome by shutting down
Exchange prior to shutting down the operating system.
?¡è This configuration is less secure because Exchange administrators will
have local administrative access to Active Directory, enabling them to
elevate their privileges. In addition, any security vulnerability found in
Exchange or Active Directory exposes the other to attack and compromise.
?¡è Once Exchange has been installed on a computer, its role (e.g., domain
controller or member server) cannot be changed. Do not demote or promote
an Exchange 2003 computer. Doing so will break several components,
including Outlook Mobile Access, and Microsoft Product Support Services
does not support this.
?¡è Running clustered Exchange servers on cluster nodes that are also
domain controllers is not supported by Microsoft and should never be done
under any circumstances.
For more questions about Exchange, you can address in
Microsoft.public.exchange or exchange2000 to get the most efficient and
professional support.
HTH!
Thanks & Regards
Amanda Wang [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================================
--------------------
>From: "John Riddle" <jriddleatsignwilsongroupnyperiodcom>
>References: <#HM9KTbcFHA.4040@xxxxxxxxxxxxxxxxxxxx>
<#zyBaxbcFHA.2664@xxxxxxxxxxxxxxxxxxxx>
>Subject: Re: Removing Member Server?
>Date: Wed, 15 Jun 2005 13:02:31 -0400
>Lines: 44
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>Message-ID: <OxacGwccFHA.3828@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: mail.wilsongroupny.com 216.211.198.130
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10680
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>I've already used DCPromo to successfully demote the server. Everything is
>fine. The server is listed as a member server. I simply want to finalize
it by
>physically removing it now without screwing up anything in AD or DNS. Am I
>safe to just unplug it from the network or is there something else to do.
>Again, this is no longer a DC, DNS Server, WINS server, DHCP Server, RRAS
>Server or anything else. Simply a member file server with no shared
>directories or DFS shares on it.
>
>Thanks,
>
>John
>
>"Michele Betelli" <michele.betelli@xxxxxxxxx> wrote in message
>news:%23zyBaxbcFHA.2664@xxxxxxxxxxxxxxxxxxxxxxx
>John Riddle wrote:
>> Hello,
>
>ciao
>
>> I had a Domain Controller that was also running Exchange. Last week
>> it had a hard drive crash and I knew that I wanted to replace the
>> server anyway, so I transferred all the Exchange Data to another
>> server, transferred all the Domain Controller and GC roles.
>> Everything is transferred to other servers now. I have removed it as
>> a domain controller and removed all other roles such as DNS, RRAS,
>> etc. It is now simply an empty member server doing nothing except
>> waiting to be removed. Is there a certain method to removing it from
>> the domain/AD? Do I just unplug it from the network and that's it? Or
>> are there any other necessary steps to take to make sure that this
>> server no longer exists in the domain or AD?
>
>look this:
>http://support.microsoft.com/default.aspx?scid=kb;en-us;216498
>
>> Thanks,
>>
>> John
>
>nulla,ciao
>--
>Mitch
>
>
>
>
.
- References:
- Removing Member Server?
- From: John Riddle
- Re: Removing Member Server?
- From: Michele Betelli
- Re: Removing Member Server?
- From: John Riddle
- Removing Member Server?
- Prev by Date: RE: Migrating NT PDC to AD Domain
- Next by Date: Re: In-place upgrade from NT to 2003, member server question
- Previous by thread: Re: Removing Member Server?
- Next by thread: NT4 to W2K3 Upgrade - Domain name Change?
- Index(es):
Relevant Pages
|
