Re: Machine role is domain controller
From: ptwilliams (ptw2001_at_hotmail.com)
Date: 01/18/05
- Next message: Remind-IT: "Lan implemantation"
- Previous message: Umesh Thakur: "RE: Should I create a new GPO or use the existing one?"
- In reply to: Marsha: "Re: Machine role is domain controller"
- Next in thread: Marsha: "Re: Machine role is domain controller"
- Reply: Marsha: "Re: Machine role is domain controller"
- Reply: Marsha: "Re: Machine role is domain controller"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 18 Jan 2005 12:26:12 -0000
I'd say yes - install the hotfix onto your XP workstation. If it does fix
the problem, I suggest you submit this information to Microsoft (via the
submit section of that KB) and advise them to update the KB to reflect that
this also applies to any machine (XP and 2003 are the only ones at the
moment) with the 2003 adminpak.msi.
If it doesn't work, you can uninstall the hotfix using add/ remove programs.
-- Paul Williams http://www.msresource.net http://forums.msresource.net "Marsha" <Marsha@discussions.microsoft.com> wrote in message news:E5A32626-6E30-4C4A-955D-1B77F346F7A4@microsoft.com... Yes, I understand the cause as stated in the hotfix. I however, do not understand why it is happening to me since I am not running the tools on a Windows 2003 server. As Paul stated below, it appears that it applies to Windows XP as well. I am using Windows XP. That is not stated in the article. I was wondering if anyone knew if this had to do with the domain functional level or something else. It appears to be unrelated to the domain. Also, should this hotfix then be applied to my Windows XP machine as well as all Windows 2003 servers in my organization? This may seem like an obvious question, but it is not always wise to assume when it comes to hotfixes and patches. Thanks in advance for any help! Marsha "ptwilliams" wrote: > I assume that this also applies to XP boxes running the original 2003 > adminpak.msi then. > > -- > > Paul Williams > > http://www.msresource.net > http://forums.msresource.net > > > "Glenn L" <the.only(delete)@gmail dot com> wrote in message > news:edi9QbR$EHA.3236@TK2MSFTNGP15.phx.gbl... > According to the fix this is a bug in the 'find computers tool' of ADUC on > Windows 2003 Server. > So any W2K3 server where you use ADUC to find computers will need this > fix. > It's happening because of the 'cause' section of the KB883480 > It has nothing to do with the domain functional level. > > -- > Glenn L > CCNA, MCSE 2000/2003 + Security > > "Marsha" <Marsha@discussions.microsoft.com> wrote in message > news:26D5CD70-119A-49C9-8FBF-514BDBBB72ED@microsoft.com... > >I noticed a problem when searching for a computer in AD. It shows all > > 'machine roles' as domain controllers when they are not. I found this > > hotfix > > for Windows 2003 (http://support.microsoft.com/?kbid=883480).My question > > is...I have a native Windows 2000 environment with a few Windows 2003 > > member > > servers. Does this hotfix only apply to Windows 2003 domains or should > > I > > apply it to my Windows 2003 member servers? As I read it, it appears to > > address Windows 2003 domains, so I am a little confused as to why its > > happening in my environment. Any input would be helpful. Thanks! > > > >
- Next message: Remind-IT: "Lan implemantation"
- Previous message: Umesh Thakur: "RE: Should I create a new GPO or use the existing one?"
- In reply to: Marsha: "Re: Machine role is domain controller"
- Next in thread: Marsha: "Re: Machine role is domain controller"
- Reply: Marsha: "Re: Machine role is domain controller"
- Reply: Marsha: "Re: Machine role is domain controller"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
