none
Windows 8 and Server 2012 WSUS

    Frage

  • Morning,

    I am running WSUS in a standalone environment.  My WSUS server is a 2012 x64 box. 

    Server version: 6.2.9200.16384

    This machine has synced with my upstream server successfully.

    On any of my clients Win7 or win8 I get Error 8024402C.

    -The machines appear to register with WSUS, but fail to download the files.

    -I have renamed the "SoftwareDistribution" folder (in an attempt to download a newer wuagent)

    -There is no proxy

    -Firewalls are turned off

    -Lan settings are check to "Auto detect"

    I am currently in the process of setting this up on a "non-standalone" system.  Has anyone got this working?  It appears to be very new, with mixed results.

    Thoughts?

    Thanks,

    Justin

    Dienstag, 13. November 2012 14:31

Antworten

  • Thanks for the Command, I decided to rebuild the server (I needed to make some other changes).

    The way I move data from the internet to my closed network is by utilizing wsusutil export on the internet connected machine to create a .cab file, and a log file. Then I move that data via removable media to my closed network and run wsusutil import.  I adjust the archive bit on the internet machine so I only move new update files.  I do this about once a week.  Sadly once the data moves to the closed network, it is there indefinitely. Data is not allowed to flow the other way.

    trucking on!  I'll let you know if my new configurations change my results.

    Freitag, 16. November 2012 14:01
  • Then I move that data via removable media to my closed network

    And you cannot use that same removable media to transport the logfile (or 100 lines thereof) out of the disconnected network in order to post it here?

    As for the small edited segment you did post... this line stands out pretty strongly:

    WinHttp: SendRequestUsingProxy failed for <http://ds.download.windowsupdate.com/w8/2/windowsudpate/redir.wuredir.cab> error 0x8024402c

    Looks like the client is trying to connect to Windows Update. No doubt that's a major fail on a disconnected network.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Montag, 19. November 2012 15:48
    Moderator
  • So I agree thats a fail on a closed network, but why the heck is it trying to connect?

    I couldn't say.  The obvious answer is that the client is not configured correctly.

    Otherwise, given the circumstances, I would suggest you search/review the historical posts in this forum. Every known scenario that can befall an isolated network has been discussed in this forum at least a dozen times over the past four years.

    Without the ability to get actual diagnostic data -- there's only so much we can do for you,


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Dienstag, 20. November 2012 22:22
    Moderator

Alle Antworten

  • On any of my clients Win7 or win8 I get Error 8024402C.

    It would be helpful to see the entire detection event with error code(s) in context.

    Please do the following on one of these client systems:

    1. Record the system time of the client.
    2. Reboot the client.
    3. After reboot, run this command: wuauclt /resetauthorization /detectnow.
    4. Wait 30 minutes.
    5. Post all of the entries from the WindowsUpdate.log starting at the time recorded in Step #1.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Dienstag, 13. November 2012 23:18
    Moderator
  • Ugh,  Of course this would not be easy.  I sadly cannot get the log from this "Standalone Network" to my internet computer.

    I will give you a few lines that I copy over by hand....  Let me know if I missed something you want to see (other than the entire log :-p)

    There are a bunch of these:

    DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.

    Followed by:

    Report CWERReporter Finishing event handling. (00000000)

    The services is ended then started up again

    It gives agent information (Endpoint provider is all Zero's) All other configuration information looks correct for my setup

    Then I get

    Report Warning: CserializationHelper::InitSerialize Failed : 0x80070002

    Report CWERReporter::Init succeeded

    Then it looks like it is restoring the existing download jobs (gives bits ID etc)

    It fails to restore with error 0x802400b (for all 15 downloads)

    Here are some other error I see listed (not sure what it is doing at this point)

    Failed to get WU Exemption info from NLM, assuming not exempt, error = 0x8007032

    Looks like the agent starts and looks for updates

    Misc WARNING: Send Failed with hr = 80072ee7

    Then I start getting these errors:

    WinHttp: SendRequestUsingProxy failed for <http://ds.download.windowsupdate.com/w8/2/windowsudpate/redir.wuredir.cab> error 0x8024402c

    WinHttp: SendRequestToServerForFileInformation MakeRequest Failed error 0x8024402c

    WinHttp: SendRequestToServerForFileInformation Failed with 0x8024402c

    WinHttp: ShouldFileBeDownloaded failed with 0x8024402c

    send request faild, hr = 80072ee7

    Later on,

    Warning: NWS Failure: errorCode=0x903d0013

    Warning: The body of the received message contained a fault

    Warning: Soap fault info

    Warning: detail: <detail><errorcode>RegistrationRequired</errorcode></detail><message>Need to call RegisterComputer</message>

    Fatal: oncallfailure(hrCall, m_error) Failed with hr=0x8024407

    Agent Warning: Failed to download eula file "url" silverlight file.....

    DnldMgr Warning :CheckIfDirExists returned error 0x80070002

    Mittwoch, 14. November 2012 17:37
  • Try running the below commands on one of the client machines and then let it check it again.

    • proxycfg -d
    • net stop wuauserv
    • net start wuauserv

    Also check this patch out.

    http://support.microsoft.com/kb/2734608

    • Bearbeitet Tim.Harris Mittwoch, 14. November 2012 19:18
    Mittwoch, 14. November 2012 19:07
  • What is it that you want me to look for?  proxycfg is not valid on vanilla windows 8

    The command was not found. Can I manually check?  I am not using a proxy, nor is there one set on the NIC or in IE.

    Thanks!!

    Mittwoch, 14. November 2012 19:22
  • Am 14.11.2012 schrieb jpsider:

    What is it that you want me to look for?  proxycfg is not valid on vanilla windows 8

    The command was not found. Can I manually check?  I am not using a proxy, nor is there one set on the NIC or in IE.

    http://msdn.microsoft.com/en-us/library/windows/desktop/aa384069%28v=vs.85%29.aspx
    Windows Vista and Windows Server 2008:  ProxyCfg.exe has been deprecated. It is replaced by the Netsh.exe
    http://technet.microsoft.com/de-de/library/cc731131%28v=ws.10%29.aspx

    Winfried


    http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx
    http://www.wsuswiki.com/Home

    Mittwoch, 14. November 2012 19:29
  • What is it that you want me to look for?  proxycfg is not valid on vanilla windows 8

    The command was not found. Can I manually check?  I am not using a proxy, nor is there one set on the NIC or in IE.

    Thanks!!


    Both of those are things I've done to fix previous issues.  I don't know if they will resolve yours or not.
    Mittwoch, 14. November 2012 19:32
  • Cool, so I ran

    netsh winhttp reset proxy

    -It said that the setting was direct

    I stopped the Winupdate service, then restarted the service

    Still getting the same errors in my previous (sad excuse of a copied log file) post.

    Great thought to look there! Thanks!

    Mittwoch, 14. November 2012 19:42
  • Digging further...

    On Server 2008 the WSUS content is located at c:\WSUS\WsusContent

    On Server 2012 the WSUS content is located at c:\Program Files\Update Services\WsusContent

    The permissions appear to be the same on both machines. 

    Is it normal for the location to be different?  if not, should I switch it? where is that setting/configuration?

    Donnerstag, 15. November 2012 15:34
  • Ugh,  Of course this would not be easy.  I sadly cannot get the log from this "Standalone Network" to my internet computer.

    How do you get the updates into the WSUS server of this 'standalone network'?

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Freitag, 16. November 2012 01:58
    Moderator
  • On Server 2012 the WSUS content is located at c:\Program Files\Update Services\WsusContent

    Is it normal for the location to be different?

    Yes. They screwed up a whole bunch of stuff when they recompiled WSUS for Win2012. This is but one of many.

    if not, should I switch it?

    I would. For starters, having the ~\WSUSContent folder on the SYSVOL is not a recommended practice; storing tens of GB of content in the %ProgramFiles% folder seems idiotic to me. I can only assume this is caused by more of the same stupid changes in the installation defaults that nobody was complaining about anyway.

    Sigh... "Windows Reimagined" is what this is.

    where is that setting/configuration?

    In %ProgramFiles%\Update Services\Tools you'll find a utility called wsusutil.exe.

    Create a root folder on some other drive (or on C: if that's all you have). Run this command: wsusutil movecontent rootFolderPath move.log.

    That will move the WSUSContent folder to rootFolderPath.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Freitag, 16. November 2012 02:05
    Moderator
  • Thanks for the Command, I decided to rebuild the server (I needed to make some other changes).

    The way I move data from the internet to my closed network is by utilizing wsusutil export on the internet connected machine to create a .cab file, and a log file. Then I move that data via removable media to my closed network and run wsusutil import.  I adjust the archive bit on the internet machine so I only move new update files.  I do this about once a week.  Sadly once the data moves to the closed network, it is there indefinitely. Data is not allowed to flow the other way.

    trucking on!  I'll let you know if my new configurations change my results.

    Freitag, 16. November 2012 14:01
  • Then I move that data via removable media to my closed network

    And you cannot use that same removable media to transport the logfile (or 100 lines thereof) out of the disconnected network in order to post it here?

    As for the small edited segment you did post... this line stands out pretty strongly:

    WinHttp: SendRequestUsingProxy failed for <http://ds.download.windowsupdate.com/w8/2/windowsudpate/redir.wuredir.cab> error 0x8024402c

    Looks like the client is trying to connect to Windows Update. No doubt that's a major fail on a disconnected network.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Montag, 19. November 2012 15:48
    Moderator
  • Yes, well my security folks would have a fit if I told them I wanted to move any data from my closed network out.  No matter if it was a log file or a picture of a smiley face.

    So I agree thats a fail on a closed network, but why the heck is it trying to connect?  I've told it to talk to my local WSUS box, not to go to the internet.

    Thoughts?

    Montag, 19. November 2012 19:30
  • So I agree thats a fail on a closed network, but why the heck is it trying to connect?

    I couldn't say.  The obvious answer is that the client is not configured correctly.

    Otherwise, given the circumstances, I would suggest you search/review the historical posts in this forum. Every known scenario that can befall an isolated network has been discussed in this forum at least a dozen times over the past four years.

    Without the ability to get actual diagnostic data -- there's only so much we can do for you,


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Dienstag, 20. November 2012 22:22
    Moderator