> "Jan" <Jan[ at ]discussions.microsoft.com> wrote in message
> news:28EC4051-0D7B-47EF-96C2-9BE2384197A0[ at ]microsoft.com...
>
> > In WSUS 2.0 I had the policies set to detect the server as
> >
http://S001-xx11:8530.> > I do lots of testing work and after installing a fresh image I always
> > IMMEDIATELY update it using:
> > 1) Put the client in the correct *organisational unit* in AD; same for the
> > appropriate *WSUS-group*
> > 2) Execute the client tool *ClientDiag.exe* to test if the server /
> > workstation can find the server,
> > 3) Run *gpupdate /force*
> > 4) Run *wuauclt.exe /resetauthorization /detectnow*
>
> I would have performed step #3 before step #2.
>
> > In most cases these combinations of actions (specifically last 2) make the
> > client detect the update server DIRECTLY and start updating IMMEDIATELY.
>
> When manually assigning a computer to a new OU (as in Step #1), it's
> probably pretty important to either perform Step #3 (and, preferably as Step
> #2 right after the OU change), or wait 2 hours for group policy to refresh.
>
> > Now I test drive 3.0 and changed policy setting to
http://VM100-xx11:8530 > > (I
> > also tested
http://VM100-xx11 and
http://VM100-xx11.xx11.LAN).> > Note: I run WSUS 3.0 on a Virtual Machine now.
> >
> > Then I run *gpupdate /force* on the client.
> > No computers appear in WSUS 3 (at least, and as expected, not quickly).
>
> The behavior has not changed with regard to Group Policy. Group Policy has
> absolutely nothing to do with WSUS operations.
>
> > Unfortunately *ClientDiag.exe* shows strange behaviour (it e.g. mentions
> > the
> > server is a WSUS 2 server) finds the server, but *Connection to server. .
> > . .
> > .* and *SelfUpdate folder is present.* do not "pass".
> > Apparently this version of *ClientDiag.exe* is incorrect.
> > Where can u find a newer version?
>
> No... the ClientDiag is *not* incorrect. It is true that it identifes the
> WUA v7.0 product as a "WSUS 2.0 client". That'll be updated in the next
> revision of the Client Diagnostic Tool, I imagine; but the part that says
> the connection to the server is failing. You can take that one to the bank.
> It's absolutely correct. It also explains why you're not seeing clients in
> the WSUS server.
>
> Since you've changed the location, and name, of the WSUS server. I'd venture
> a guess that you've not properly configured the DNS to provide the correct
> IP Address for machine 'VM100-xx11'.
>
> > In addition, could you inform if above mentioned sequence of commands is
> > the
> > same for WSUS 3 in order to quickly connect (detect) to the Server and to
> > enforce updates?
>
> Yes.
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> Independent WSUS Evangelist
> MVP-Software Distribution (2005-2007)
>
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E>
> Everything you need for WSUS is at
>
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx>
> And, almost everything else is at
>
http://wsusinfo.onsitechsolutions.com> .....
>
>
>