See inline answers.
Also if you are having problems it is usually better to post the full output
from the Client Diag. There are people here who can tell a lot of detail from
that output that most miss completely.

On Thu, 24 Jul 2008 10:42:32 -0700, "MowGreen [MVP]" <mowgreen@nowandzen.com>
wrote:

>Forwarded to the WSUS NG for OP's convenience:
>
>Web-based reader <for the kidz>
>http://www.microsoft.com/communities... date_services
>
>NNTP reader <for adults>
>news://msnews.microsoft.com/microsof...pdate_services
>
>
>----------------------------------------------------------------------------------------------------
>Rock41 wrote:
>
>> Let me also add that I ran the Client Diagnostic utility and received the
>> message that useWUServer is disabled. The command prompt also states this
>> version is WSUS 2.0.
This need to be enabled int the GPO for the client to use WSUS

>>
>> "Rock41" wrote:
>>
>>
>>>My WSUS 3.0 clients are not showing in the wsus admin conosle. My
>>>configuration is by Active Directory (Group Policy Management Console). I
>>>have verfied that BITS are running. I tried the wuauclt.exe /detectnow
>>>command but I believe this only works if your using client-side targeting
Incorrect, it is not related to client side targeting. It won't do anything
though if the above police does not enable WSUS on the client.

>>>(using the local group policy).
You would not use local policy if you have a GPO.

>Also the automatic updates service is running
>>>on the local machine. I also waited for at least 24 hours to verify if the
>>>computers would show in the console. Any help would be appreciated. Thanks.
>-----------------------------------------------------------------------------------------------------
>
>
>MowGreen [MVP 2003-2008]
>===============
> *-343-* FDNY
>Never Forgotten
>===============
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.