WSUS 3.0 SP2 - Problem with SSL : Error 80072f0c.

-

hello people,

i becoming nuts.
i have brand-new wsus 3.0 sp2. i'm trying setup ssl on it, , i've been stuck same issue 3 days.

the server name toto.child.rootdomain.ext, , i've configured gpo accessed via https://wsus.rootdomain.ext.
the need https need use wsus software update point in sccm native mode.

i had first tried set directly wsus sccm sup, client updates fail error still encountering.
to make troubleshooting simpler, trying set ssl on wsus, still getting same error in clients' windowsupdate.log.

i created certificate on our ca (with certificate name = wsus.rootdomain.ext), confiured iis it, enabled ssl on adequate virtual directories, ran wsusutil configuressl wsus.rootdomain.ext.
still client fail 80072f0c error. i've seen many people having error on web, did not find solution.

please find log below. may add without ssl, wsus works charm.

#############           
## start ##  au: search updates           
#########           
<<## submitted ## au: search updates [callid = {de2b0ed0-b6b2-4871-8fae-1a4bd4f8b8ba}]           
*************           
** start **  agent: finding updates [callerid = automaticupdates]           
*********           
"  * online = yes; ignore download priority = no"           
"  * criteria = ""isinstalled=0 , deploymentaction='installation' or ispresent=1 , deploymentaction='uninstallation' or isinstalled=1 , deploymentaction='installation' , rebootrequired=1 or

isinstalled=0 , deploymentaction='uninstallation' , rebootrequired=1"""           
  * serviceid = {3da21691-e39d-4da6-8a4b-b43877bcb1b7} managed           
  * search scope = {machine}           
checking agent selfupdate           
client version: core: 7.4.7600.226  aux: 7.4.7600.226           
validating signature c:\windows\softwaredistribution\selfupdate\wuident.cab:           
 microsoft signed: yes           
validating signature c:\windows\softwaredistribution\selfupdate\wuident.cab:           
 microsoft signed: yes           
validating signature c:\windows\softwaredistribution\selfupdate\wsus3setup.cab:           
 microsoft signed: yes           
validating signature c:\windows\softwaredistribution\selfupdate\wsus3setup.cab:           
 microsoft signed: yes           
determining whether new setup handler needs downloaded           
validating signature c:\windows\softwaredistribution\selfupdate\handler\wusetupv.exe:           
 microsoft signed: yes           
selfupdate handler update not required: current version: 7.4.7600.226, required version: 7.4.7600.226           
"evaluating applicability of setup package ""wuclient-selfupdate-activex~31bf3856ad364e35~x86~~7.4.7600.226"""           
"setup package ""wuclient-selfupdate-activex~31bf3856ad364e35~x86~~7.4.7600.226"" installed."           
"evaluating applicability of setup package ""wuclient-selfupdate-aux-toplevel~31bf3856ad364e35~x86~~7.4.7600.226"""           
"setup package ""wuclient-selfupdate-aux-toplevel~31bf3856ad364e35~x86~~7.4.7600.226"" installed."           
"evaluating applicability of setup package ""wuclient-selfupdate-core-toplevel~31bf3856ad364e35~x86~~7.4.7600.226"""           
"setup package ""wuclient-selfupdate-core-toplevel~31bf3856ad364e35~x86~~7.4.7600.226"" installed."           
selfupdate check completed.  selfupdate not required.           
+++++++++++  pt: synchronizing server updates  +++++++++++           
  + serviceid = {3da21691-e39d-4da6-8a4b-b43877bcb1b7}, server url = https://wsus.rootdomain.ext/clientwebservice/client.asmx           
warning: cached cookie has expired or new pid available           
initializing simple targeting cookie, clientid = 51d3ff3f-2f60-459a-b54e-ea8b9eb78ede, target group = , dns name = testwin7img.child.rootdomain.ext        

   
  server url = https://wsus.rootdomain.ext/simpleauthwebservice/simpleauth.asmx           
warning: send failed hr = 80072f0c.           
warning: sendrequest failed hr = 80072f0c. proxy list used: <(null)> bypass list used : <(null)> auth schemes used : <>           
  + last proxy send request failed hr = 0x80072f0c, http status code = 0           
  + caller provided credentials = no           
  + impersonate flags = 0           
  + possible authorization schemes used =            
warning: getauthorizationcookie failure, error = 0x80072f0c, soap client error = 5, soap error code = 0, http status code = 200           
warning: failed initialize simple targeting cookie: 0x80072f0c           
warning: populateauthcookies failed: 0x80072f0c           
warning: refreshcookie failed: 0x80072f0c           
warning: refreshptstate failed: 0x80072f0c           
warning: sync of updates: 0x80072f0c           
warning: syncserverupdatesinternal failed: 0x80072f0c           
  * warning: failed synchronize, error = 0x80072f0c           
  * warning: exit code = 0x80072f0c           
*********           
**  end  **  agent: finding updates [callerid = automaticupdates]           
*************           
warning: wu client failed searching update error 0x80072f0c           
>>##  resumed  ## au: search updates [callid = {de2b0ed0-b6b2-4871-8fae-1a4bd4f8b8ba}]           
  # warning: search callback failed, result = 0x80072f0c           
  # warning: failed find updates error code 80072f0c           
#########           
##  end  ##  au: search updates [callid = {de2b0ed0-b6b2-4871-8fae-1a4bd4f8b8ba}]           
#############           
successfully wrote event au health state:0           
au setting next detection timeout 2009-12-14 20:38:40           
setting au scheduled install time 2009-12-14 16:00:00           
successfully wrote event au health state:0           
successfully wrote event au health state:0           
report event: {0d434a75-5412-46fb-8bb7-4da344c4f5b2} 2009-12-14 16:38:40:259+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072f0c automaticupdates failure 

software synchronization windows update client failed detect error 0x80072f0c.
cwerreporter::handleevents - wer report upload completed status 0x8           
wer report sent: 7.4.7600.226 0x80072f0c 00000000-0000-0000-0000-000000000000 scan 101 managed           
cwerreporter finishing event handling. (00000000)           

after night sleep, found out was. dumb.
ssl settings on virtual directories set "accept client certificates". setting "ignore" fixed it.
can't figure out why, i'll think later.

i wasn't aware sccm/sup required ssl . . .  hmmmm
--> doesn't in native mode ?



Windows Server  >  WSUS



Comments

Post a Comment

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

-
hello, i'm getting error when trying add print services role in windows 2012 standard. i'm getting same error whether use gui or powershell. this new server install. the powershell error follows: add-windowsfeature : request add or remove features on specified server failed. installation of 1 or more roles, role services, or features failed. the referenced assembly not found. error: 0x80073701 at line:1 char:1 + add-windowsfeature print-services + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : invalidoperation: (@{vhd=; credent...name=localhost}:psobject) [install-windowsfeature],     exception     + fullyqualifiederrorid : dismapi_error__failed_to_enable_updates,microsoft.windows.servermanager.commands.addwind    owsfeaturecommand success restart needed exit code      feature result ------- ------...
Read more

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL

-
Image
i'm attempting setup windows 2016 rds standard deployment session hosting.  layout follows: rds01 - rds connection broker , web access ts02 - rds session host ts03 - rds session host domain these servers part of has (1) windows 2008 server , (2) windows 2016 servers acting dcs.  domain running @ windows 2003 functional level. servers on single routed network no firewall between them.  dns , ptr records servers exist , resolve on hosts.  servers can pinged each other. in other words, there no network connectivity issues. i've setup rds deployment several times w/ same results. the issue can login via rdweb interface on rds01 win10 desktop , connect published rdp desktop without issue (i.e. no error messages user) , no errors in logs.  when try directly rdp rds01, authenticate user (per event log) error stating user doesn't have access system.  in event log event id 1306 message of "remote desktop connection broker client faile...
Read more

Como saber quien entro a mi PC por la Red

-
quisiera saber si es posible, o existe forma de auditar quien accedió a mi pc vía red, es decir se que hay software que perminten auditar el file server para saber quien entro y modifico y/o borro un archivo... pero si alguien entro mi pc \\pcname\c$ hay forma de determinar que usuario entro al disco c de una pc en especifica y copio, modifico o borro un archivo...   y la otra pregunta cuales son las mejores herramientas para auditar la red y el file server   gracias una forma de detectar quien esta conectado tu pc es través del comando net user entra en cmd y escribes net user eso muestra los usuarios que están conectados en tu equipo en un momento determinado, se que no es lo que pides pero puede servir para descubir alguien en determinado momento. para que no este compartido le dan clic derecho sobre mi pc>propiedades>remoto y le desmarcan donde dice ''permitir que este equipo envíe invitaciones ...
Read more