WSUS 3.0 Clients are not showing in wsus admin console

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
(using the local group policy). 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.

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.

Forwarded to the WSUS NG for OP's convenience:

Web-based reader <for the kidz>
http://www.microsoft.com/communities...pdate_services

NNTP reader <for adults>
news://msnews.microsoft.com/microsof...pdate_services

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.

We had the same problem and support told us that if you image a server the
susclientid id would be a duplicate and would cause this problem. We needed
to delete the key which is located at:
Local Machine | Software | Microsoft | Current Version | Windows | susclientid
After deleteing the registry entry run the following command to regenerate
the key:
C:\wuauclt /detectnow /resetauthorization

Just want to clarify a few things about what support told you.

1. "if you image a server" I assume you're referring to the SUS server?
2. Where do you delete the key, on the SUS server or on the client computers?

I have a somewhat similar issue but I will create a new posting so that I don't hijack this thread.

Thank you.

One key issue I haven't seen answered for an issue like this with GPOs:

Where MUST the WSUS edits be done in the GPO?
Must is be the Computer- Default Domain Polcy?
Or can it be an =OU - sub GPO??

Try posting this issue to the WSUS newsgroup:
http://www.microsoft.com/communities...pdate_services

This one, Windows Update, deals with client-side issues.