Thank you Steve, for your timely answer.
I was trying to figure out if I accidently put that computer under the DC
group policy or if it just ended up reading someting wrong. If I clicked on
Domain Controllers, it only showed my server, not that workstation.
I ran dcpromo wizard and it removed AD from the server. Glad I am still in
"playing" stage for the next month before I need this active.
Thanks again
"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
>A domain computer can have only one active account in the domain. If you
>run the support tool gpresult on the XP Pro computer in question it will
>tell you what container it is in. The other account can be deleted. If the
>active account is the domain controllers container you can then move it
>into whatever container you want. An XP Pro computer can not be a domain
>controller. Just because a computer is in the domain controller container
>does not make it a domain controller. The only relevance would be that the
>Domain Controller Security Policy would apply to any computer in the domain
>controller container which would mostly be user right assignments. With
>default policy any computer in the domain controller container does not
>allow regular domain users to logon to it. --- Steve
>
>
> "GreyhawkC&D" <(E-Mail Removed)> wrote in message
> news:OC%23H$(E-Mail Removed)...
>>I have Win Serv 2003 Ent Ed and three computers running XP Pro.
>>
>> I recently noticed that one of my three XP systems was showing in the
>> Domain
>> Controllers group, as well as in the Domain Computers.
>>
>> I do not want it as a controller. It seems to be affecting the way the
>> XP
>> systems interact. Since it ended up with this role, the other XP systems
>> cannot view the shared resources on this computer.
>>
>> Server 2003 tells me to change the primary function in the computer
>> properties in AD manager, but when I try it, it tells me it cannot.
>>
>> What is it that I am missing?
>>
>> Thanks in advance.
>>
>>
>
>
|