Jump to content

Recommended Posts

Posted

Good evening,

 

A while ago I posted a thread on this forum regarding a server 2008 system I had which appeared to have a selection of permission problems resulting in it being unable to download or display installed updates.

It had not installed updates for years and was in a terrible state.

 

I have recently installed a new server 2012 system and have joined it as a DC so I can migrate the user accounts over.

 

1 hour ago, the 2012 system was fully up to date with all updates installed and working, and now, since it has become a DC, it is unable to check its updates and shows a white space in the View Update History section of windows updates.

 

What is the problem here?! I have never come across this anywhere else.

Posted
Try Netsh winhttp import proxy source=ie to import the windows update settings to the server

 

Thanks for your suggestion,

Here is the response I get:

 

Error writing proxy settings. (5) Access is denied.

 

Direct access (no proxy server).

 

 

If I try with cmd as administrator, I get:

 

Current WinHTTP proxy settings:

Direct access (no proxy server).

 

Unfortunately, after a bounce, same thing happens. This is exactly the same problem I have had with the FRDC server which is why I bought a new one so I could start moving things over (with the new one as a DC), but it has clearly picked some bad policy or something up when it joined as a DC. What can I do in this situation?!

Posted

I have been looking a little further and found this on the FRDC Default Domain Controller Policy in GP:

 

Administrative Templates

An error has occurred while collecting data for Administrative Templates.

 

 

 

The following errors were encountered:

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\CaptureWizard.admx (error = 2): The system cannot find the file specified.

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\MovieMaker.admx (error = 2): The system cannot find the file specified.

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\Search.admx (error = 2): The system cannot find the file specified.

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\WindowsCollaboration.admx (error = 2): The system cannot find the file specified.

 

User Configuration (Enabled)hide

Policieshide

Administrative Templateshide

An error has occurred while collecting data for Administrative Templates.

 

The following errors were encountered:

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\CaptureWizard.admx (error = 2): The system cannot find the file specified.

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\MovieMaker.admx (error = 2): The system cannot find the file specified.

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\Search.admx (error = 2): The system cannot find the file specified.

An appropriate resource file could not be found for file C:\Windows\PolicyDefinitions\WindowsCollaboration.admx (error = 2): The system cannot find the file specified.

Posted

Also, View Update History is completely blank, it was not like this before joining to domain.

 

Can anyone suggest some ideas, this is driving me up the wall?

Posted (edited)
Florian's Blog » GPMC Report error: An appropriate resource file could not be found

 

This seems to suggest it's linked to DNS, and not being able to download updates can point the same way. Can you access the internet at all from that machine? If so, try an nslookup on the Windows Update urls.

 

Thanks very much for your post.

I do have internet connectivity on the server, the brower works very well, no proxies and no proxies have mistakenly gone on to any of the policies.

 

I did an nslookup to windowsupdate.microsoft.com and got the following result:

 

> nslookup windowsupdate.microsoft.com

Server: http://www.update.microsoft.com.nsatc.net

Addresses: 65.55.50.157

191.232.80.55

Aliases: windowsupdate.microsoft.com

windowsupdate.microsoft.nsatc.net

 

DNS request timed out.

timeout was 2 seconds.

DNS request timed out.

timeout was 2 seconds.

*** Request to windowsupdate.microsoft.com timed-out

 

On a working server, at a totally different site, I get the following:

C:\Users\lmi123>nslookup windowsupdate.microsoft.com

1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa

primary name server = 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.

0.0.0.0.0.0.0.ip6.arpa

responsible mail addr = (root)

serial = 0

refresh = 28800 (8 hours)

retry = 7200 (2 hours)

expire = 604800 (7 days)

default TTL = 86400 (1 day)

Server: UnKnown

Address: ::1

 

Non-authoritative answer:

Name: http://www.update.microsoft.com.nsatc.net

Addresses: 65.55.50.157

191.232.80.55

Aliases: windowsupdate.microsoft.com

windowsupdate.microsoft.nsatc.net

 

 

C:\Users\lmi123>

 

 

Edited by talksr
Posted
your domain name isnt an internet routable one like school.town.sch.uk is it rather than school.local / school.internal?

 

No, it is just a .local on. In this instance, smsch.local. The working server has bgfiadm.local.

 

They both have an identical internet connection with the same provider; LGFL, so I know it can't be a ISP related issue.

Posted

I'd suggest looking at the DNS configuration on each server, and make sure that your misbehaving server can resolve local addresses.

 

Also worth looking at the routes for both to the windowsupdate service. You can use traceroute for this.

Posted
I'd suggest looking at the DNS configuration on each server, and make sure that your misbehaving server can resolve local addresses.

 

Also worth looking at the routes for both to the windowsupdate service. You can use traceroute for this.

 

hmm, ok local addresses resolve perfectly well. This is a FRDC server, so it there were local issues, no one would be able to log in.

 

In terms of a tracert:

 

Faulty server:

C:\Users\lmi123>tracert windowsupdate.microsoft.com

 

Tracing route to http://www.update.microsoft.com.nsatc.net [65.55.50.158]

over a maximum of 30 hops:

 

1 1 ms 1 ms <1 ms 172.30.150.173

2 1 ms 1 ms 1 ms 172.22.25.134

3 2 ms 2 ms 2 ms 172.18.159.205

4 3 ms 3 ms 3 ms 172.30.191.66

5 2 ms 2 ms 3 ms 172.30.191.29

6 3 ms 3 ms 3 ms 171.33.199.253

7 10 ms 11 ms 10 ms so-2-2-0.leed-sbr1.ja.net [146.97.40.85]

8 9 ms 9 ms 10 ms ae2.londtn-sbr1.ja.net [146.97.35.137]

9 27 ms 10 ms 10 ms po1.lond-ban4.ja.net [146.97.35.110]

10 11 ms 11 ms 11 ms 198.200.130.129

11 12 ms 11 ms 11 ms ae12-0.lon04-96cbe-1b.ntwk.msn.net [207.46.44.16

3]

12 79 ms 78 ms 79 ms ae4-0.nyc-96cbe-1a.ntwk.msn.net [204.152.141.191

]

13 86 ms 87 ms 85 ms ae15-0.blu-96c-1a.ntwk.msn.net [207.46.46.233]

14 87 ms 85 ms 85 ms ae7-0.was02-96cbe-1b.ntwk.msn.net [204.152.141.2

00]

15 85 ms 85 ms 85 ms ae1-0.was02-96cbe-1a.ntwk.msn.net [204.152.141.2

06]

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 134 ms 129 ms 134 ms ae2-0.cys01-96cbe-1a.ntwk.msn.net [204.152.140.1

16]

21 * * * Request timed out.

22 156 ms 155 ms 155 ms 191.234.82.247

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

 

Trace complete.

 

Good server:

C:\Users\lmi123>tracert windowsupdate.microsoft.com

 

Tracing route to http://www.update.microsoft.com.nsatc.net [65.55.50.158]

over a maximum of 30 hops:

 

1 <1 ms <1 ms <1 ms 172.30.137.161

2 1 ms 1 ms 1 ms 172.23.2.98

3 4 ms 4 ms 4 ms 172.18.159.205

4 4 ms 4 ms 4 ms 172.30.191.66

5 4 ms 4 ms 4 ms 172.30.191.29

6 5 ms 4 ms 5 ms 171.33.199.253

7 12 ms 12 ms 11 ms xe-11-0-0.manckh-ban1.ja.net [146.97.40.17]

8 11 ms 11 ms 11 ms ae11.manckh-sbr1.ja.net [146.97.35.49]

9 13 ms 13 ms 11 ms ae29.erdiss-sbr1.ja.net [146.97.33.41]

10 12 ms 12 ms 12 ms ae27.londtn-sbr1.ja.net [146.97.33.13]

11 12 ms 12 ms 12 ms po1.lond-ban4.ja.net [146.97.35.110]

12 13 ms 13 ms 13 ms 198.200.130.129

13 14 ms 13 ms 13 ms ae12-0.lon04-96cbe-1b.ntwk.msn.net [207.46.44.

3]

14 80 ms 80 ms 81 ms ae4-0.nyc-96cbe-1a.ntwk.msn.net [204.152.141.1

]

15 87 ms 93 ms 88 ms ae15-0.blu-96c-1a.ntwk.msn.net [207.46.46.233]

16 87 ms 87 ms 88 ms ae7-0.was02-96cbe-1b.ntwk.msn.net [204.152.141

00]

17 87 ms 87 ms 90 ms ae1-0.was02-96cbe-1a.ntwk.msn.net [204.152.141

06]

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 131 ms 133 ms 131 ms ae2-0.cys01-96cbe-1a.ntwk.msn.net [204.152.140

16]

23 * * * Request timed out.

24 159 ms 157 ms 157 ms 191.234.82.247

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

 

Trace complete.

 

Very similar traces by the looks of it.

  • 5 weeks later...
Posted (edited)

Are there any entries relating to Windows Update in the computer GPO for Domain Controllers or Default Domain Policy?

 

Probably not as it affects only one of your servers but...

 

Specifically (OU GPO) Computer Configuration/Policies/Administrative Templates/Windows Components/Windows Update

 

I remember when I started here Windows Updates hadn't been applying for some time and I found it was due to a policy making all clients look to a server (possibly WSUS) that had been replaced!

 

But seems DNS or something related due to your nslookup results, also your tracert never actually gets to Windows Update does it?

 

What is your actual set-up re: other servers, DC's etc?

Edited by Koldov

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...