Ah. That's interesting. I wondered what that was about. I so rarely do anything with GP that I tend to forget a lot of this stuff.
Makes it hard to keep up with it. Thanks, Kurt On Tue, Feb 9, 2010 at 19:03, Richard Stovall <rich...@gmail.com> wrote: > You used to get to the editor by right clicking on an object in ADUC where a > GPO could be linked, choosing properties from the context menu, and > selecting the Group Policy tab. Or something like that. The link now takes > you to the GPMC. > > On Tue, Feb 9, 2010 at 9:58 PM, Carl Houseman <c.house...@gmail.com> wrote: >> >> 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:kurt.b...@gmail.com] >> 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/> ~
