Not that it matters one whit, but my understanding is that the GPMC came out of the SBS group (SBS 2003) and was such a popular addition that it was adopted overall.
On Tue, Feb 9, 2010 at 10:00 PM, Brian Desmond <[email protected]>wrote: > Up until Windows 2008, there was a Group Policy tab on the properties of > OUs, Domains, and Sites in ADUC and dssites. This was how you accessed > policies and edited them. GPMC came out of band sometime after 2003 shipped. > > Thanks, > Brian Desmond > [email protected] > > c - 312.731.3132 > > Active Directory, 4th Ed - http://www.briandesmond.com/ad4/ > Microsoft MVP - https://mvp.support.microsoft.com/profile/Brian > ________________________________________ > From: Carl Houseman [[email protected]] > Sent: Tuesday, February 09, 2010 8:58 PM > To: NT System Admin Issues > Subject: RE: Reviewing my GPs, and found something I don't understand > > Why aren't you using Group Policy Management (GPMC)? That's the tool > intended for editing group policies that are applied to OUs. You can run > that on a DC, member server, or workstation and it always looks at domain > policies. > > By default, gpedit.msc views and modifies the local machine policy. I > don't see a way to make gpedit.msc access a domain policy or machine policy > on any other machine, because that's not its intended function. > > And you lost me when you talked about invoking gpedit.msc from ADU&C. > Editing group policies is not a function of ADU&C. > > Carl > > -----Original Message----- > From: Kurt Buff [mailto:[email protected]] > Sent: Tuesday, February 09, 2010 5:24 PM > To: NT System Admin Issues > Subject: Reviewing my GPs, and found something I don't understand > > Minor issue, but it caused me to fumble for a few minutes.... > > I was looking over my Group Policies, and couldn't find them. > > I tracked it down, but need some help understanding what I was looking at. > > Win2k3 R2 domain, FFL/DFL. > > I started gpedit.msc via Start/Run on my XP SP3 workstation, and > started hunting for my DisableAutoplay GP, which I show as being > linked to my Workstation OU. I just couldn't see it anywhere, despite > going back to the MSFT KB article - 967715. > > I finally logged into my DC, and gpedit.msc showed the GP exactly as > expected. I then went back to ADUC on my workstation, and invoked > Properties on the OU in question, and it gave me a version of > gpedit.msc that was connected to the domain, as expected. > > It's obvious that my local copy of gpedit.msc is pointing to my local > machine (if I start it from Start/Run), but if invoked from ADUC it > works as expected. > > Can anyone enlighten me on this difference? > > Kurt > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
