"Drew" <> wrote in message
news:...
> Ok, that makes sense. If I disable, "Remove access to use all Windows
> Update features." then it seems to look to Windows Update instead of our
> WSUS server.
That policy would not make any distinction between WSUS or Automatic
Updates.
Of course, if you're expecting to see a web-based client interface for WSUS,
that could be the source of the confusion.
WSUS works in the background, just like Automatic Updates has for the past
ten years.
> For instance, I set 10 updates to be pushed, if I disable that policy,
> then I get 15 updates to be installed.
This would suggest that the client isn't even using WSUS, but is still using
the default "Automatic Updates" methodology.
>Is it looking somewhere else besides my local WSUS?
Quite possibly!
1. Technical/semantical point -- the WSUS Server doesn't push updates, it
makes them available to clients who identify and request them.
2. In order for clients to identify and request them, they need to know
where the WSUS Server is. Have you configured Group Policy (or Local Policy
if no Active Directory) to correctly configure the clients to use the WSUS
Server? Of particular note, the one policy that impacts the WSUS vs AU
decision is the policy "Specific intranet Microsoft update services
location" which must be enabled to faciliate the use of a WSUS Server.
3. Once the policy is configured, to verify that the clients are properly
receiving the policy you can use any of the policy management tools, or you
can inspect the registry at HKLM\Software\Policies\Microsoft\WindowsUpdate,
and in the AU subkey the value "UseWUServer" should be = dword:0x1.
>
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website:
http://www.microsoft.com/wsus
My Websites:
http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin