Machines not showing up

I am using an AD policy to apply these settings. When I run gpresult on one
machine, I get an error that gpresult is not a recognized command or batch
file. On the other machine the policy is not lited under gpresult. I logged
in as a user which ran the policy on other machines and it still does not
run. The machine is in the Default group, the same as all other machines.
Can I manually run the policy?

"JeffG" wrote:

> I don't think both are updating though - there isn't a WSUS server
> assigned so it would be hard to figure out how they could be updating
> - or from where...
>
> Are you using an AD policy to apply the settings to your computers for
> WSUS? If so, this is most likely a policy application error on the
> two problem machines, run the command gpresult on both and see if you
> can see your policy and if it's being applied.
>
> If you're manually setting the registry keys, you need to change these
> two machines as well...
>
> HTH
> JeffG
>
>
> On Tue, 26 Jul 2005 06:03:03 -0700, "Kendall"
> <Kendall.DeleteThis@discussions.microsoft.com> wrote:
>
> >I have WSUS installed on a W2k Server and everything seems to be running fine
> >except for two machines. The server that has WSUS installed on it is not
> >shown in WSUS admin and a W2k workstation that is used only for backup is not
> >shown. I have checked the windowsupdate log in both and have the following
> >entry. Both are presently update. Any suggestions?
> >
> >2005-07-26 07:48:49 544 254 Agent * WSUS server: <NULL>
> >2005-07-26 07:48:49 544 254 Agent * WSUS status server: <NULL>
> >2005-07-26 07:48:49 544 254 Agent * Target group: (Unassigned Computers)
> >2005-07-26 07:48:49 544 254 Agent * Windows Update access disabled: No
>
>
 >> Stay informed about: Machines not showing up 

On Tue, 26 Jul 2005 07:39:07 -0700, "Kendall"
<Kendall RemoveThis @discussions.microsoft.com> wrote:

>I am using an AD policy to apply these settings. When I run gpresult on one
>machine, I get an error that gpresult is not a recognized command or batch
>file.

What windows version (including SP level) is this machine?

>On the other machine the policy is not lited under gpresult. I logged
>in as a user which ran the policy on other machines and it still does not
>run. The machine is in the Default group, the same as all other machines.

Are other domain policies being applied to this machine?

>Can I manually run the policy?
>

Not exactly - you could make the changes to the registry manually,
and/or run a script, or even use the policy editor on the client to
make the changes. I wouldn't suggest any of those - if this policy is
not applying, probably *no* policies are applying. And even if others
are, you should probably figure out why this one is not...
 >> Stay informed about: Machines not showing up 

The machine that will not run gpresult is W2k SP4.

The other machine is is Server 2000 and the only policy shown running is the
default domain policy.

"JeffG" wrote:

> On Tue, 26 Jul 2005 07:39:07 -0700, "Kendall"
> <Kendall DeleteThis @discussions.microsoft.com> wrote:
>
> >I am using an AD policy to apply these settings. When I run gpresult on one
> >machine, I get an error that gpresult is not a recognized command or batch
> >file.
>
> What windows version (including SP level) is this machine?
>
> >On the other machine the policy is not lited under gpresult. I logged
> >in as a user which ran the policy on other machines and it still does not
> >run. The machine is in the Default group, the same as all other machines.
>
> Are other domain policies being applied to this machine?
>
> >Can I manually run the policy?
> >
>
> Not exactly - you could make the changes to the registry manually,
> and/or run a script, or even use the policy editor on the client to
> make the changes. I wouldn't suggest any of those - if this policy is
> not applying, probably *no* policies are applying. And even if others
> are, you should probably figure out why this one is not...
>
>
>
 >> Stay informed about: Machines not showing up 

>The machine that will not run gpresult is W2k SP4.

Er? That command should be installed - or I should say, all my W2KSP4
machines have it and I didn't install it manually. It's almost
certainly a policy application issue, but without the policy tools I'm
not sure how to make it apply.

Can you run the group policy editor on this machine? (gpedit.msc)
There might be something whacked out in the OS on this one, or it may
not be set up on the domain correctly. But you would think you would
get some errors in the event logs if that were the case...

>
>The other machine is is Server 2000 and the only policy shown running is the
>default domain policy.

Hm. And you've already said that the server exists in the same OU
container as the rest of the machines that are picking up the policy -
although note that the default group for DC's is not the default group
for all machines, if that applies.

So there are no errors or filter warnings at all, it just isn't
listed? And yet the default domain policy IS listed... Hrm..
Interesting. Your best bet, if neither one of these ramblings has
helped shed any light, is to take the question to the Group Policy
newsgroup and see if you get any help there, they'll be able to ask
more pertinent questions on troubleshooting the policy.

Always more words than help
JeffG

>
>"JeffG" wrote:
>
>> On Tue, 26 Jul 2005 07:39:07 -0700, "Kendall"
>> <Kendall DeleteThis @discussions.microsoft.com> wrote:
>>
>> >I am using an AD policy to apply these settings. When I run gpresult on one
>> >machine, I get an error that gpresult is not a recognized command or batch
>> >file.
>>
>> What windows version (including SP level) is this machine?
>>
>> >On the other machine the policy is not lited under gpresult. I logged
>> >in as a user which ran the policy on other machines and it still does not
>> >run. The machine is in the Default group, the same as all other machines.
>>
>> Are other domain policies being applied to this machine?
>>
>> >Can I manually run the policy?
>> >
>>
>> Not exactly - you could make the changes to the registry manually,
>> and/or run a script, or even use the policy editor on the client to
>> make the changes. I wouldn't suggest any of those - if this policy is
>> not applying, probably *no* policies are applying. And even if others
>> are, you should probably figure out why this one is not...
>>
>>
>>
 >> Stay informed about: Machines not showing up