MSExchangeStudent wrote:
> I have a win2003 DC and XP SP 2 clients. I did install WSUS 3.0 and try to
> change a GP setting through GP on the DC. On the DC i do the following :
> Right click DC OU in AD >
Do you mean the Domain Controllers OU? Any group policy set on this OU will
only affect the domain controllers, not the client machines - unless you've
moved the client machines into the Domain Controllers OU, which is probably a
bad idea.
Also, it is recommended that you install the Group Policy Management Console,
which provides a much superior interface for managing group policy.
> > right click "new" > give it a name "WSUS 3.0 policy" > right click > edit
> > computer config > admin templates > windows components > windows update >
> disable "automatic update" setting
If this is disabled none of the other settings will have any effect. I don't
believe you meant to do this.
> enable "sepcifiy intranet micrsoft
> update location > put the servername like this in both dialogue boxes
> http://ctt-3rd_server:8530 > OK > file > exit.right click "users" in the top
> window and select "enforce" > in the bottom Security Filtering window i did
> add the domain users group > OK
This is wrong. You're applying a computer policy, not a user policy, so if you
must use security filtering you would want to add one or more computers or
computer groups. However, best practice is not to configure security filtering
unless you have a specific need for it. Normally you want group policy to apply
to all users/computers that are in the OU you assign it to.
> IF i ask someone to log off and on again their gpedit still say "not
> configured" under "sepcifiy intranet micrsoft update location" - why is the
> setting not taking effect?
Are you using gpedit on the client machines to look at the local policy? This
doesn't show policy assigned from the domain. If you want to determine what
group policy is being applied from the domain, use the gpresult command-line tool.
Harry.