Failing software updates

  • Thread starter Thread starter Neil Shaw
  • Start date Start date
N

Neil Shaw

Hi

My network here consists of ~40 workstations. We then have one file server
and one Exchange server, which runs AD. All are Win2k/Win2k Server.

I have added a Group Policy for all computers to allow me to deploy software
(mainly service packs) to all machines automatically. Whilst this has worked
for the majority of workstations, there are 5 or 6 that are not picking up
this update. As far as I know, there are no differences in the setups of
these machines.

Any hints as to where I should be looking to resolve this problem?

Thanks,
Neil
 
Neil,

Could you logon to one of the failing machines and run a gpresult /v, and
then do the same on a working machine. If you paste the results back in
here, I can take a look.

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com
 
Are the machines in the same OU?

Check the Application Event viewer on the problem machines for
warnings/errors for application management.

Can you also send back the netlogon.log file from c:\windows\security\logs
on one of the problem boxes?

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com
 
Brian said:
Are the machines in the same OU?
Click to expand...

Yes. One of the machines was actaully renamed and went straight into the
correct OU, but still didn't pick up the update.
Check the Application Event viewer on the problem machines for
warnings/errors for application management.
Click to expand...

Lots of the same error:
Event: 1000
Source: Userenv
Details: Windows cannot determine the user or computer name. Return
value (1722).
Can you also send back the netlogon.log file from c:\windows\security\logs
on one of the problem boxes?
Click to expand...

There is no netlogon.log file in c:\winnt\security\logs\
There is, however, one in c:\winnt\debug\ but this is 0-sized, as is the
same file on my computer which had picked up the update as expected
 
Neil-

Can you try this:

"Value 1722 - "The RPC Server is unavailable" - Usually occurs when DNS
servers are not configured properly. There is connectivity but not at the
service level. See the Q260371 link below for troubleshooting such issues.
One note here, usually it may appear that DNS is set properly but one has to
double-check all the aspects of DNS registration/resolution as the problem
may not be that obvious. See also Q261007 - It says that this behavior can
occur if the address for the configured preferred DNS server on the client
is invalid or unreachable.
From a newsgroup post: "Do the following to ensure that the SRV records for
the AD servers are in DNS properly: (from the DOS prompt)

nslookup
set type=srv
set type=srv
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM
Server: dnsserver.yourdomain.com
Address: 192.168.100.2

you should see something like this:

_ldap._tcp.dc._msdcs.YOURDOMAIN.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server1.YOURDOMAIN.COM
_ldap._tcp.dc._msdcs.YOURDOMAIN.COM SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = server2.YOURDOMAIN.COM
server1.YOURDOMAIN.COM internet address = 1.1.1.2
server2.YOURDOMAIN.COM nternet address = 1.1.1.1

If you don't then you definately have a DNS problem.

I would also recommend running the dcdiag and netdiag utilities on
your domain controllers. If you find that the servers aren't in DNS,
then make sure dynamic updates are enabled on your DNS server and
restart the netlogon server on each of your DCs."

--
--
Brian Desmond
Windows Server MVP
(e-mail address removed)12.il.us

Http://www.briandesmond.com
 
Brian Desmond [MVP] wrote:
<snip "look at the DNS" sorta thing>

A-ha! :)
The machines affected weren't included in the server's DNS records.
They've been added and appear to be working.

Thanks for the help :)
 
Back
Top