SCCM 2007 R2 on Server 2008 Weird WebDAV errors on MP installation
I was messing about with installing SCCM 2007 R2 on a Windows Server 2008 box. Everything went nice and smooth up to the point where my Windows PE for building and capturing an image would just Initialize and then spontaneously reboot…
So I decided to dive into the smsts.log (located in x:\SMSTSLOG or c:\smstslog, depending if your task-sequence was able to format the c:\ drive allready 
)
In there I found some errors relating to my MP ( No MP Certificates found). From there on I decided to check out my Site and Component status in the SCCM Console and found out that my Management point was having issues with the WebDAV configuration, so I zoomed in on the MPSetup.log (located in %programfiles%\Microsoft Configuration Manager\logs) and there were the following lines:
<06-24-2009 19:53:49> checking WebDAV configurations <06-24-2009 19:53:52> WebDAV settings is not setup appropriately <06-24-2009 19:53:52> [Allow property queries with infinite depth] should be true (true) <06-24-2009 19:53:52> [Allow Custom Properties] should be false (true) <06-24-2009 19:53:52> [Allow anonymous property queries] should be true (true) <06-24-2009 19:53:52> Allow [All users read access to All content] authoring rule should exist (exist)
Which was really strange, because according to my IIS Manager>WebDAV Authoring Rules>WebDAV Settings, Allow Custom Properties was set to false…. eeeh what the hell?
I googled around and found out the following, the IIS console doesnt always update the webDAV configuration file correctly…. so I edited the config file manually.
C:\Windows\System32\inetsrv\config\schema\WEBDAV_schema.xml
I found the following lines:
<element name="properties"> <attribute name="allowAnonymousPropfind" type="bool" defaultValue="true" /> <attribute name="allowInfinitePropfindDepth" type="bool" defaultValue="true" /> <attribute name="allowCustomProperties" type="bool" defaultValue="true" />
and changed them to:
<element name="properties"> <attribute name="allowAnonymousPropfind" type="bool" defaultValue="true" /> <attribute name="allowInfinitePropfindDepth" type="bool" defaultValue="true" /> <attribute name="allowCustomProperties" type="bool" defaultValue="false" />
Then I restarted the IIS service, and after that I restarted the SMS_SITE_COMPONENT_MANGER service from within the ConfigMgr Service Manager (located under the Tools node). After that my Management Point played nicely 
November 28th, 2009 - 22:08
Just stumbled across this, solved my issue. Damn wonky tools…
Thanks!
December 23rd, 2009 - 07:39
This fixed my MP install failure. For me, I had to uninstall WebDav, edit the file, then reinstall WebDav.
Thanks!
December 30th, 2009 - 18:23
DUDE!! Thank you a million times over. I’ve been scratching my head on SCCM2007 issues for days now. Turns out I had the exact same problem you had. Now most of my client based issues are fixed and after recreating my MP, things are working much better now.
January 26th, 2010 - 17:04
Thanks man! Was on this issue for hours. The properties just would not update when changing them in the server console. Manually it worked just fine.
February 12th, 2010 - 16:24
YES, Me happy too
February 22nd, 2010 - 12:46
my 2008 system won’t allow me to update the file XML file as it required elevated permissions that i don’t seem to be able to grant even when logged on as the local and/or domain admin. Any ideas?
February 22nd, 2010 - 12:46
You should take ownership of that file first….
February 23rd, 2010 - 09:59
Something else to point out:
I made a copy of the XML file before editing it (WEBDAV_Schema – Copy.xml) and it still didn’t work. You need to change the extension to something other than XML. It would appear that the MP installer catches the first file (in my case the copy / original) and reads that… renaming to WEBDAV_Schema – Copy.xml.OLD did the trick…
March 2nd, 2010 - 05:55
Gods be praised for good internet techs fixing the endless must be known and undocumented issues of Microsoft. The day I dont have to consult internet community to get a major MS product working will be a rare one indeed.
This one (being so common as above) must be known internally by anyone in this area. Like all the issues fixed in TAM and not released to anyone else working with a pre-release. See it all the time (even get the odd, yes we will update the document three months from now).
I guess when you are that big you just dont care.
Anyway, you da man and I’m loving it because that just worked and probably no MS document exists on the issue.
March 12th, 2010 - 14:43
I was took ownership with the local administrators group and then gave that group full rights to the file. I was then able to remove the read only attribute. I then edited the file and made the changes.
June 28th, 2010 - 20:04
Yep edit the XML and away we go! Same issue with WebDav different symptoms. It boils down to who has permissions to edit the XML. In the GUI the changes appear persistent but not so
August 5th, 2010 - 01:34
I have the problem with the “read only”-part. I can not edit the file and then reload it. It is owned by “trustedInstaller”
Please Help me! I have tried so long with this problem
August 5th, 2010 - 08:38
Well, try taking ownership of the file as a domain admin or local admin on the box.
Right-mouse button > Properties > go to the Security tab > press the advanced button > go to the Owner tab > press the edit button > select either your username or the administrators group in the Change owner to: field and press ok. Close all dialogs with Ok and you should be able to edit the file.
September 9th, 2010 - 16:46
thank you so much fixed my problems
September 28th, 2010 - 23:13
wooooe, quite strange and hard.
The last part that I missed and caused me a whole day was what “Wayne” mentioned. This damn IIS would still use the old xml file eventhough I completely changed the name! only when I changed the extention it worked properly!!!
Thanks all, specially Wayne.
October 5th, 2010 - 10:05
Yes…the solution is correct hit to the problem. It did resolved my issue.
But the question here is why Microsoft have not catched this bug till now?
Anyways thanks a ton for the perfect solution.
October 31st, 2010 - 21:32
There’s always a different problem with each SCCM 2007 installation. I’ve installed SCCM 2007 6-7 times until now. Always with WebDAV stand alone. This was my first 2008 R2 installation and then I bumped into this problem. Thanks for the fix. Crazy weird problem.
November 10th, 2010 - 22:08
Lovley.
I removed my MP
Then uninstalled and reinstalled WebDAV 7.5, on my Server 2008.
Made the changes into the WebDAV_Schema.xml file directly
then I added the MP again.
Works like a charm.
November 11th, 2010 - 12:30
I’d been right through a couple of long posts on this issue and still couldn’t get this issue to work. Eventually discovered that looking at the WebDev Authoring section at the root of IIS was not good enough. You ALSO need to go the the default web site section in IIS, and click on the WebDev Authoring section. This showed up on my installation as ‘disabled’ – even though the root one was enabled. Changed this one to enabled too, restarted component and finally the management point installed correctly!
January 30th, 2011 - 00:04
Heya,
If you get the MP unknown error (comes up with blue question mark) at setup / install phase that is caused by WebDav and either because the wrong version of webdav is used (different for 2008 R2 and SP2 for example)and / or cause it is misconfigured. Correct the installation by re-installing webdav and remember to configure webdav ONLY at the default web site level NOT at the IIS root level.
Another workaround is to install the site without selecting install MP and do it manually after the initial site server install.
Cheers;
J
May 13th, 2011 - 19:51
This fixed our error as well. Good job!
May 25th, 2011 - 13:34
Wonderful!
Resolved my problem, i was 2 weeks with this problem. thank you very much!
Now i will migrate forefront client security for forefront endpoint protection here in Brazil!
June 2nd, 2011 - 22:57
Thanks for posting this – tried several other solutions but this is the only one that worked. Really annoys me that MS dont just provide an option to automatically correct the settings that it is complaining about instead of us manually having to mess about editing config files.
July 13th, 2011 - 09:17
Thanks dude. You really saved my day. I was already three days into troubleshooting this issue. I cannot believe how crappy some of the MS tools are, and can there not be ANY information on MS website about this.
October 16th, 2011 - 04:01
This worked for me as well! Thank you for taking the time to explain this unusual corner-case. This fix means that I get to go home tonight.
November 1st, 2011 - 22:45
This worked perfectly, and after removing and re-installing WebDav, the authoring rules, IIS Resets, BITS. Manually editing the WebDav xml file did the trick! I wonder how or why this happened. Either way, Thank you very much!!!
Robert
November 13th, 2011 - 12:54
As so many have said on here spent many hours checking logs and back to IIS console, scratching head as to what I was doing wrong! Thought I was config the wrong site / place!!Thanks for this and thanks to all the other comments … makes me feel better that I was not the only one stumped for the same reason! Why is this not fixed MS..? running 2008 R2 with SP1 earliest comment Nov 2009!
November 30th, 2011 - 03:13
Just as an aside to this…my WebDAV_SCHEMA file was locked as owned by the TrustedInstaller account and I couldn’t do anything to it to modify contents. I tried uninstalling webdav and reinstalling, but it seemed to be the file was still there after uninstall because the system didn’t have permissions on the file??? So I took ownership, removed the readonly, and everything is working as it should now. Thanks for the help.