Client doesn't register with New server


test client windows 8

new wsus server server 2012

i created test ou , applied gpo point test client new wsus server never appears in computers group.  i did check registry , seems gpo pointing new server.  i ran clientdiag tool , returns:

wsus client diagnostics tool

checking machine state
        checking admin rights run tool . . . . . . . . . pass
        automatic updates service running. . . . . . . . . . pass
        background intelligent transfer service running. . . pass

getfileversion(szenginedir,&susversion) failed hr=0x80070002

system cannot find file specified.

if wuauclt.exe /detectnow elevated command prompt see event 1001 containing following:

fault bucket -885597873, type 5
event name: windowsupdatefailure2
response: not available
cab id: 0

problem signature:
p1: 7.8.9200.16465
p2: 80244019
p3: 00000000-0000-0000-0000-000000000000
p4: scan
p5: 101
p6: managed
p7: 0
p8: 
p9: 
p10: 

attached files:

these files may available here:
c:\programdata\microsoft\windows\wer\reportarchive\noncritical_7.8.9200.16465_728c60ceccd3c3948938040b5a1236499fe2f_1c666e56

analysis symbol: 
rechecking solution: 0
report id: 16d17765-ca1c-11e2-be98-2c27d739bc6e
report status: 0
hashed bucket: fcb20221c6f78de9b8efbf2ae1cdce74

to untrained eye, seems there fault in server.  am correct?  is there tool or methodology troubleshoot server with?

thanks o reply.

2013-06-05 06:37:51:863 568 1534 agent * wsus server: http://emsrv-sysman1.emcc.edu

2013-06-05 06:37:56:184 568 11a4 agent * found 0 updates , 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities

looks here there =no= updates on wsus server!!!

2013-06-05 06:37:56:246 568 11a4 agent * serviceid = {117cab2d-82b1-4b5a-a08c-4d62dbee7782} third party service

2013-06-05 568 agent * found 15 updates , 23 categories in search; evaluated appl. rules of 68 out of 110 deployed entities

but finds 15 updates (which note have single digit revision numbers, indicating may locally published updates -- unless microsoft stopped using 3 digit revision numbers win8/ws2012 updates). note detection launched "third party service"... maybe should talk else installed on machine, , else might installed in environment leveraging windows update agent scan updates.

2013-06-05 06:37:57:538 568 11a4 ep got wsus selfupdate url: "http://emsrv-sysman1.emcc.edu/selfupdate"
2013-06-05 06:37:57:538 568 11a4 misc validating signature c:\windows\softwaredistribution\selfupdate\wuident.cab:
2013-06-05 06:37:57:550 568 11a4 misc microsoft signed: yes
2013-06-05 06:37:57:550 568 11a4 misc infrastructure signed: yes
2013-06-05 06:37:57:801 568 11a4 misc warning: winhttp: sendrequesttoserverforfileinformation failed 0x80190194

and failed selfupdate check http 404 error.

2013-06-05 06:37:57:802 568 159c au #############
2013-06-05 06:37:57:802 568 11a4 ep got 9482f4b4-e343-43b6-b170-9a65bc822c77 redir secondaryserviceauth url: "http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab"
2013-06-05 06:37:57:808 568 11a4 agent checking updated auth cab service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 @ http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab

and i've never seen windows update agent before ... redirect "secondaryserviceauth url". in fact, if think is, it's functionality introduced system center configuration manager 2012 service pack 1 .... have configmgr 2012 deployed?

also, should increase detection frequency @ least -2- hours. when using server side targeting, 1-hour detection frequency prevent clients getting target group changes when made wsus console.


lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
solarwinds head geek
microsoft mvp - software packaging, deployment & servicing (2005-2013)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
http://www.solarwinds.com/gotmicrosoft
the views expressed on post mine , not reflect views of solarwinds.



Windows Server  >  WSUS



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607