WebDAV error when doing a client push ConfigMgr 2012 R2

Hi everyone, I am getting an error message when doing a client push, only on some DPs.

Here is the setup:

  • ConfigMgr 2012 R2 on Server 2012 R2.
  • DP are on Server 2008 R2 (for the most part).
  • DP are installed using the exact same way, adding the Primary Site Server to the local Admins group, then using the console to install the role, selecting BranchCache and Configure IIS.
  • No PXE.
  • Boundary groups are configured as appropriate.

When initiating a client push the following errors are displayed in the CCMSetup.log:

  • Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 401)
  • Failed to check url http://DPServerName.com/SMS_DP_SMSPKG$/S0100003. Error 0x80004005
  • Enumerated all 1 local DP locations but none of them is good. Fallback to MP.
  • GET 'HTTP://MPServerName.com/CCM_Client/ccmsetup.cab'

The installation is done but yet again, no local DP are used.

The same scenario is actually working on other DP that was configured using the same exact way.

Servers where not new installation and where used for other things:

  • MDT Deployment Share with PXE.
  • Other share.

As far as I can tell, IIS is well configured as I am able to deploy any other software on clients and they are using the local DP. Only the client installation is causing problem.

Anyone have any idea?

There is a lot of post about a similar problem on ConfigMgr 2007 but all solution are to configure WebDAV, which is not configured in ConfigMgr 2012.

Thank you guys for any tip and/or help!

Mathieu



  • Edited by mdesjardins Wednesday, March 25, 2015 12:28 PM
March 25th, 2015 12:27pm

Hi again, here are the logs from IIS from this morning:

2015-03-26 13:00:47 172.16.64.9 GET /selfupdate/iuident.cab - 80 - 172.16.64.9 - 200 0 0 17880 0
2015-03-26 13:00:47 172.16.64.9 GET /selfupdate/iuident.cab - 80 - 172.16.64.9 - 200 0 0 17880 0
2015-03-26 13:00:47 172.16.64.9 POST /reportingwebservice/reportingwebservice.asmx - 80 - 172.16.64.9 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5485) 200 0 0 1133 0
2015-03-26 13:00:47 172.16.64.9 POST /ApiRemoting30/WebService.asmx - 80 Test\CDLGHOST$ 172.16.64.9 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5485) 200 0 0 1226 0
2015-03-26 13:00:47 172.16.64.9 POST /ServerSyncWebService/serversyncwebservice.asmx - 80 - 172.16.64.9 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5485) 200 0 0 1133 0
2015-03-26 13:00:47 172.16.64.9 POST /ClientWebService/Client.asmx - 80 - 172.16.64.9 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5485) 200 0 0 1133 0
2015-03-26 13:00:47 172.16.64.9 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 172.16.64.9 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5485) 200 0 0 1133 15
2015-03-26 13:00:47 172.16.64.9 POST /DssAuthWebService/DssAuthWebService.asmx - 80 - 172.16.64.9 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.5485) 200 0 0 1133 0
2015-03-26 13:01:19 172.16.64.9 POST /ReportingWebService/ReportingWebService.asmx - 80 - 172.16.65.64 Windows-Update-Agent 200 0 0 636 218
2015-03-26 13:01:35 172.16.64.9 PROPFIND /SMS_DP_SMSPKG$/S0100003 - 80 - 172.16.65.25 ccmsetup 401 2 5 1509 1201
2015-03-26 13:01:35 172.16.64.9 PROPFIND /SMS_DP_SMSPKG$/S0100003 - 80 Test\C006232$ 172.16.65.25 ccmsetup 401 3 64 0 78
2015-03-26 13:01:44 172.16.64.9 POST /ReportingWebService/ReportingWebService.asmx - 80 - 172.16.65.43 Windows-Update-Agent 200 0 0 636 202
I can see the errors 401.2 and 401.3 but I am not able to know why they are in error and why they are not on some other computers having the same role.

Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 9:09am

So you definitely checked on the WIndows Auth IIS feature being installed *and* enabled in IIS?
March 26th, 2015 10:37am

Yes I did.

I am slowly running out of idea. The only thing that could be different on some servers is that the installation of the role was sent before the configmgr computer account was added to the admin group of local servers. But again, in that case, no connection should be even made to the server and no role should be installed.

Mat

Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 11:25am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics