none
WSUS can't download updates using proxy with credentials from Windows Update in Windows Server 2012 R2.

    Question

  • There is the same issue in Windows Server 2012. To resolve it, Microsoft published hotfix KB2838998. But this hotfix not upplicable to 2012 R2.

    Is there a hotfix for Windows Server 2012 R2 like one in http://support.microsoft.com/kb/2838998 ?
    Friday, January 17, 2014 10:41 AM

All replies

  • Hi Bogdan, Wsus on Server 2012 is Wsus 6.2 and, on Server 2012R2 it's 6.3, so I suppose that Microsoft have include the bug fix into Wsus 6.3. So I assume there have no 6.3 version of the KB2838998. The issue you're experiencing is certainly another one bug.

    I assume you have try to set up the Wsus server to go to Internet directly without passing through the proxy, and then wsus has start to download updates ? Am I Right ?


    David COURTEL
    IT Technician
    Wsus Third-Party Softwares Publishing : http://wsuspackagepublisher.codeplex.com

    • Edited by DCourtel Friday, January 17, 2014 10:57 AM
    Friday, January 17, 2014 10:57 AM
  • Hi David.

    It's seems that Microsoft forgot to include fix for this bug in WSUS 6.3, because in my new installation of 2012 R2 with WSUS role and all updates the problem still exists.

    I assume you have try to set up the Wsus server to go to Internet directly without passing through the proxy, and then wsus has start to download updates ? Am I Right ?

    Yes, you're right. But this is not an option.

    Friday, January 17, 2014 12:47 PM
  • Ok, as your wsus server can download on Internet without passing through the proxy, this is not a NTFS permissions issue.

    How do you know your wsus server don't download updates ? What kind of error message you have ? Can you look into :

    C:\Program Files\Update Services\LogFiles\SoftwareDistribution.log

    and into the Windows Event log of the Wsus server.


    David COURTEL
    IT Technician
    Wsus Third-Party Softwares Publishing : http://wsuspackagepublisher.codeplex.com

    • Edited by DCourtel Friday, January 17, 2014 3:18 PM
    Friday, January 17, 2014 3:18 PM
  • David, no offence, but I don't understand what your questions are for.

    I have exact situation as discribed in KB2838998 article but on Windows Server 2012 R2.

    The WSUS synchronization performs successfully. However, the WSUS server cannot connect to Windows Update to download the required updates.

    And, to answer your question, I see on my proxy that wsus don't use credentials while trying to download updates.

    Friday, January 17, 2014 3:58 PM
  • I have ask these questions to ensure you had the right conclusion in regards of facts.

    You can not imagine how many people drawn false conclusions in regards of clues.


    David COURTEL
    IT Technician
    Wsus Third-Party Softwares Publishing : http://wsuspackagepublisher.codeplex.com


    • Edited by DCourtel Monday, January 20, 2014 5:12 PM
    Friday, January 17, 2014 4:24 PM
  • The WSUS synchronization performs successfully. However, the WSUS server cannot connect to Windows Update to download the required updates.

    It would be very helpful to see the actual Application Event Log entry for the Download Failure that confirms this is a Proxy Authentication issue, and not, perhaps, some other issue not related to proxy authentication.

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, January 17, 2014 8:39 PM
  • Lawrence,

    I spend more than 24 hours to discover this issue and I assure you that this is exact the same situation as discribed in KB2838998.

    Also, I've read your posts in the threads related to the same problem in Windows Server 2012 and they weren't very helpful.

    So, please, if you don't have answer to my initial question, don't  post here.

    Tuesday, January 21, 2014 8:55 AM
  • So, please, if you don't have answer to my initial question, don't  post here.

    Then you're on your own Bogdan, because you just blew off the only two people likely able to help you with your issue.

    I'm inclined to agree with David -- that you have likely misdiagnosed your issue.

    Your arrogance and unwillingness to cooperate doesn't do anything to dispel my inclinations.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Tuesday, January 21, 2014 11:04 PM
  • I'm inclined to agree with David -- that you have likely misdiagnosed your issue.

    Please, please, tell me that you have confirmation (real one, not just from documents) of WSUS on 2012 R2 successfully downloading updates through proxy with authorization - and I will cooperate.

    I asked a question in this forum because, I think, there are a lot Microsoft professionals. And, for me, this profesionals are masters of Microsoft products that is tested them in different scenarios.

    I hope someone among professionals of Microsoft stuff came on or will came on this issue and than I'll have my answer.

    Wednesday, January 22, 2014 6:45 AM
  • I've have the exact same issue. I saw the Hotifix and realized that was a match, but I'm also on 2012 R2, so it was a no go. After contacting Microsoft support with the issue they assigned a SCCM support engineer and he's been working on the issue through a remote assistance connection for the last couple of hours. No success yet. I did put in to have the server exempted from the proxy server and firewall but that may not happen. I'll let you know if SCCM support gets things resolved
    Thursday, January 23, 2014 5:33 PM
  • Hi, slavertycoc.

     Thanks for your post.

     I'll let you know if SCCM support gets things resolved
    I'll wait.

    Friday, January 24, 2014 6:28 AM
  • Hi.

    I've solved this:

    1. Update server via Internet and restart

    2. Stop WSUS service

    3. Delete all folders in wsuscontent

    4. C:\Program Files\Update Services\Tools> .\WsusUtil.exe reset

    5. Profit!

    Friday, January 31, 2014 10:21 AM
  • Hi, dexter82.

    Are you sure that this steps help with issue we are talking about in this thread?

    Friday, January 31, 2014 3:36 PM
  • I came across exactly like this!

    Current environment SCCM 2007 R3 SP2 PROD and test environment.

    Now, I just started this SCCM 2012 R2 project in test environment.

    My work environment with PROXY Enable (required this for browsing and Windows updates):
    1. Windows Server 2012 R2 Standard (fully patched) installed SCCM 2012 R2 Standard with these hotfixes applied: Installed Hotfix KB2905002, Installed Hotfix KB2907591, Installed Hotfix KB2907566, Installed Hotfix KB2916611

    2. Windows Server 2012 R2 Standard (fully patched) installed SQL 2012 SP1 for my SCCM 2012 R2 (separate box/remote), SCCM and WSUS on this box

    Please make sure that you check these log files below

    Go to: Drive Letter\Program Files\Microsoft Configuration Manager\Logs

    Make sure that you check these log files with CMTrace.exe:
    wsyncmgr.log (check this first!)
    WCM.log
    WSUSCtrl.log

    And also this location C:\Program Files\Update Services\LogFiles
    Check log file:
    SoftwareDistribution.log

    I encountered the same error (from wsyncmgr.log):
    STATMSG: ID=6703
    Sync failed

    I Google this error and came across with this page! But there's no real answer and I ended up calling Microsoft Support and they are very helpful!

    Here's the trick to make it work (there's no document so far out there (trust me on this):
    1. Open Update Services (WSUS) Console, run Synchronize Now

    2. Monitor wsyncmgr.log, you will see STATMSG: ID= 6703 went away! That means, it's working!!! (see my screenshots)

    NOTE: Hopefully, Microsoft will create a hotfix for this (If it more users are experiencing the same issue on Windows Server 2012 R2)

    Site note:

    I know that I configured my WSUS on SCCM 2012 R2 properly at work (because I got stuck before and learned the hardway) and follow this link below *** NO PROXY is working properly (at home), the problem seems only for people who are using PROXY! ***

    http://www.windows-noob.com/forums/index.php?/topic/9030-how-to-configure-wsus-on-sccm-2012-win-server-2012/?p=36633

    Here's two of my screenshots (there's a limit to upload - 2 max :( ):

    WSUS on SCCM 2012 R2

    WSUS on SCCM 2012 R2


    Thursday, February 20, 2014 7:31 AM
  • Here's two more of my screenshots:

    WSUS on SCCM 2012 R2

    WSUS on SCCM 2012 R2

    Thursday, February 20, 2014 7:34 AM
  • Sorry, I forgot to mention as well.

    You must Stop SMS_EXECUTIVE (service)

    and Start SMS_EXECUTIVE (service)

    Then on your SCCM 2012 R2 Console, go to Software Library, Software Updates, All Software Updates, run Synchronize Software Updates

    See my screenshots below:

    WSUS on SCCM 2012 R2

    WSUS on SCCM 2012 R2

    Thursday, February 20, 2014 6:47 PM
  • Just in case if you can't see my screenshots (new one that I just posted), here's the link:

    http://social.technet.microsoft.com/Forums/getfile/422567

    http://social.technet.microsoft.com/Forums/getfile/422568

    Thursday, February 20, 2014 6:48 PM
  • Here's the trick to make it work (there's no document so far out there (trust me on this):

    1. Open Update Services (WSUS) Console, run Synchronize Now

    2. Monitor wsyncmgr.log, you will see STATMSG: ID= 6703 went away! That means, it's working!!! (see my screenshots)

    I think not!

    WSYNCMGR.LOG is a Configuration Manager logfile. If you launch a Synchronization event from the WSUS console, Configuration Manager KNOWS NOTHING ABOUT that event, ergo it absolutely will be absence from WSYNCMGR.LOG.

    It's absence from WSYNCMGR.LOG is not conclusive of anything and does not suggest that you've found any type of fix.

    HOWEVER.. what it does demonstrate is that this is NOT a WSUS problem, because the sync works perfectly when launched from the WSUS console, rather this is a Configuration Manager R2 problem, because that's the only scenario in which it fails.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, February 20, 2014 7:28 PM