locked
WSUS used to create te customized wim stays in a deployed Server RRS feed

  • Question

  • Hi,

    I use a specific WSUS server (pbcwsusmdtbuild) when I create my customized wim created with MDT.

    WSUSServer=http://PBCWSUSMDTBuild:8530

    When I deployed this wim I found references to this WSUS server in the WindowsUpdate.log

    2014-11-06	15:03:41:133	 780	22c	DnldMgr	BITS job {59481307-C57C-4568-9AF3-7B5AF5374E36} hit a transient error, updateId = {1A96FAF6-8554-4A77-8504-A97173E77D3A}.200, error = 0x80072EE7
    2014-11-06	15:03:41:133	 780	22c	DnldMgr	File: http://pbcwsusmdtbuild:8530/Content/F8/4F766A0F8E1CF9DA4EA7CAB0DB2FAEA5C0E7E7F8.cab
    2014-11-06	15:03:41:133	 780	22c	DnldMgr	  Will not attempt to resume the job as it has reached the maximum number of attempts.
    2014-11-06	15:03:41:133	 780	22c	DnldMgr	CUpdateDownloadJob::GetNetworkCostSwitch() Neither unrestricted or restricted network cost used, so using current cost
    2014-11-06	15:03:41:133	 780	22c	DnldMgr	Error 0x8024402c occurred while downloading update; notifying dependent calls.
    

    How can I clean my server (Windows 2012 R2) so it uses the server WSUS given by the GPO ?

    Thank you for your help.

    Ludovic.

    Thursday, November 6, 2014 2:16 PM

Answers

  • it appears that MDT *IS* using the specified WSUS server. The problem is that the BITS service is having problems resolving the correct name.

    C:\>err 0x80072EE7
    # as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x2ee7
    # for hex 0x2ee7 / decimal 12007 :
      ERROR_INTERNET_NAME_NOT_RESOLVED                              inetmsg.h
      ERROR_INTERNET_NAME_NOT_RESOLVED                              wininet.h
    # 2 matches found for "0x80072EE7"

    Did you configure WSUS to *NOT* hold files locally, instead redirecting clients to download from the internet?

    Check your WSUS server, if you are still having problems, you might try the WSUS TechNet Forums.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Thursday, November 6, 2014 5:54 PM

All replies

  • it appears that MDT *IS* using the specified WSUS server. The problem is that the BITS service is having problems resolving the correct name.

    C:\>err 0x80072EE7
    # as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x2ee7
    # for hex 0x2ee7 / decimal 12007 :
      ERROR_INTERNET_NAME_NOT_RESOLVED                              inetmsg.h
      ERROR_INTERNET_NAME_NOT_RESOLVED                              wininet.h
    # 2 matches found for "0x80072EE7"

    Did you configure WSUS to *NOT* hold files locally, instead redirecting clients to download from the internet?

    Check your WSUS server, if you are still having problems, you might try the WSUS TechNet Forums.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Thursday, November 6, 2014 5:54 PM
  • You are right.

    My problem is with WSUS and not with MDT.
    But my WSUS without MDT is good !
    So I think that more users of MDT could help me.

    My problem is that I create only one customized wim and deploy it in different environments where different WSUS are used.

    How to clean up my customized wim that all the new deployed windows think that it has never used WSUS ?
    Because they don't know who is pbcwsusmdtbuild !

    Ludovic.

    Friday, November 7, 2014 7:07 AM