Re: Removing the ONLY Domain Controller?

From: Vagabond Software (carlfenley-X-_at_-X-san.rr.com)
Date: 01/26/05 

Date: Wed, 26 Jan 2005 00:26:32 -0800

"Mike Brannigan [MSFT]" <mikebran@online.microsoft.com> wrote in message news:%23VSat53AFHA.3492@TK2MSFTNGP12.phx.gbl...
>
> The impact of removing the only domain controller in the domain will be
> potentially extremely wide ranging.
>
> Examples of things that will break.
>
> no support for roaming user
> loss of server held profiles
> requirement to create local accounts for users on each machine they use
> loss of centralised account management
> loss of centralised desktop control and configuration (policy)
> loss of access to any resource secured on the domain accounts - such as
> cannot access any data on a file server where that data was owned by the
> domain account without administrator intervention
> loss of domain wide security
> loss of printer server security
> All machines will need to be "touched" to remove them from the domain and
> place them in a workgroup
> etc etc etc
>
> Are you really sure you want to do this and are you trained/qualified enough
> to be doing this task and understand the ramifications of your actions?
>
> --

No. I'm niether sure I want to do this nor am I prepared to do something like this in a true enterprise environment. However, this is only my personal home network. I have two choices; 1) remove the domain controller role from the server or 2) give the Internet access to IIS 6.0 on my Domain Controller through port 80.

I'll be opening up port 80 and serving some web pages from Windows Server 2003 machine to very light Internet traffic. I'm trying to avoid having IIS open to the Internet on the same machine as my domain controller, if reasonably possible.

carl