We are doing a new install of ConfigMgr-sp1 on Server 2008-sp2-64bit with SQL Server 2008. We have successfully configured IIS, BITS, WebDAV, etc, as recommended in: http://technet.microsoft.com/en-us/library/cc431377(classic).aspx However, when the prerequisite check runs during install, it seems to give a false positive that reads: BITS installed - error - Management Point BITS enabled - error - Management Point WebDAV installed - error - Management Point WebDAV enabled - error - Management Point I have installed IIS, BITS, WebDAV with both a domain admin account, and the built-in local administrator account <runas /user:administrator> and still got the same errors. Server 2008 file permissions have changed with the <Local User Administrator (LUA) Security> feature. These features are installed and working, however it seems that the ConfigMgr Prerequisite Check doesn't see them. Any ideas or suggestions would be greatly appreciated.

may i know where this errors are apperaing...in the logs or in pre-requisites cheker....please paste your logs or inormation in wizard... Abhishek Joshi http://blogcastrepository.com/blogs/abi/default.aspx http://blogcastrepository.com/members/Abhishek.aspx

Hi Abhishek, thanks in advance for taking a look at this...The error message apears in the Prerequisite Check part of the install. In the ConfigMgrPrereq.log the errors are at the end.BITS and WebDAV was already configured and enabled before runing the Prerequisite Check,but it still shows as missing.I wonder if there is a security setting that could blockthe Prerequisite Checkfrom seeing the installed BITS and WebDAV?=============ConfigMgrPrereq.log=============<11-05-2009 22:08:51> Executing prereq functions...<11-05-2009 22:08:51> <<<RuleCategory: Access Permissions>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking access permissions...>>><11-05-2009 22:08:51> Server-001; Administrative rights on site system; Passed<11-05-2009 22:08:51> <<<RuleCategory: System Requirements>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>><11-05-2009 22:08:51> Server-001; Unsupported site server operating system version for setup; Passed<11-05-2009 22:08:51> Server-001; Domain membership; Passed<11-05-2009 22:08:51> Server-001; Schema extensions; Passed<11-05-2009 22:08:51> Server-001; Software updates KB911897; Passed<11-05-2009 22:08:51> Server-001; Software updates KB912818; Passed<11-05-2009 22:08:51> Server-001; Software updates KB913538; Passed<11-05-2009 22:08:51> Server-001; Software updates KB914389; Passed<11-05-2009 22:08:51> Server-001; Software updates KB925903; Passed<11-05-2009 22:08:51> Server-001; Software updates KB932303; Passed<11-05-2009 22:08:51> Server-001; FAT Drive on Site Server; Passed<11-05-2009 22:08:51> Server-001; Short File Name (8.3) Support (Site system); Passed<11-05-2009 22:08:51> <<<RuleCategory: Dependent Components>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>><11-05-2009 22:08:51> Server-001; Microsoft Management Console (MMC) version; Passed<11-05-2009 22:08:51> Server-001; Minimum .NET Framework version; Passed<11-05-2009 22:08:51> Server-001; Microsoft XML Core Services 6.0 (MSXML60); Passed<11-05-2009 22:08:51> Server-001; WSUS SDK on site server; Warning; Configuration Manager software update points require Windows Server Update Services (WSUS) version 3.0 SP1 or later. If using a remote software update point, the WSUS administration console must be installed on the site server. For more information on WSUS installation see http://go.microsoft.com/fwlink/?LinkID=79477.<11-05-2009 22:08:51> Server-001; WSUS 3.0 SP1 is required on site server; Passed<11-05-2009 22:08:51> Server-001; Windows Server 2003-based schannel hotfix; Passed<11-05-2009 22:08:51> Server-001; Windows Remote Management (WinRM) v1.1; Passed<11-05-2009 22:08:51> Server-001; Microsoft Remote Differential Compression (RDC) library registered; Passed<11-05-2009 22:08:51> Server-001; MMC updates for Configuration Manager (Software Updates); Passed<11-05-2009 22:08:51> Server-001; .NET update for Configuration Manager (Software Updates); Passed<11-05-2009 22:08:51> <<<RuleCategory: Access Permissions>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking access permissions...>>><11-05-2009 22:08:51> Server-001; SQL Server sysadmin rights; Passed<11-05-2009 22:08:51> Server-001; Site server computer account administrative rights; Passed<11-05-2009 22:08:51> Server-001; SQL Server security mode; Passed<11-05-2009 22:08:51> <<<RuleCategory: System Requirements>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>><11-05-2009 22:08:51> Server-001; Domain membership; Passed<11-05-2009 22:08:51> Server-001; Short File Name (8.3) Support (Site system); Passed<11-05-2009 22:08:51> <<<RuleCategory: Dependent Components>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>><11-05-2009 22:08:51> Server-001; SQL Server version; Passed<11-05-2009 22:08:51> <<<RuleCategory: Access Permissions>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking access permissions...>>><11-05-2009 22:08:51> Server-001; SMS Provider Communication; Passed<11-05-2009 22:08:51> <<<RuleCategory: System Requirements>>><11-05-2009 22:08:51> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>><11-05-2009 22:08:51> Server-001; Domain membership; Passed<11-05-2009 22:08:51> Server-001; Short File Name (8.3) Support (Site system); Passed<11-05-2009 22:08:52> Server-001; Installed version of WAIK (SMS Provider); Passed<11-05-2009 22:08:52> <<<RuleCategory: Dependent Components>>><11-05-2009 22:08:52> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>><11-05-2009 22:08:52> <<<RuleCategory: Access Permissions>>><11-05-2009 22:08:52> <<<CategoryDesc: Checking access permissions...>>><11-05-2009 22:08:52> Server-001; Administrative rights on management point; Passed<11-05-2009 22:08:52> Server-001; Site server computer account administrative rights; Passed<11-05-2009 22:08:52> Server-001; Administrative share (Site system); Passed<11-05-2009 22:08:52> <<<RuleCategory: System Requirements>>><11-05-2009 22:08:52> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>><11-05-2009 22:08:52> Server-001; Unsupported site server operating system version for setup; Passed<11-05-2009 22:08:52> Server-001; Domain membership; Passed<11-05-2009 22:08:52> Server-001; Short File Name (8.3) Support (Site system); Passed<11-05-2009 22:08:52> <<<RuleCategory: Dependent Components>>><11-05-2009 22:08:52> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>><11-05-2009 22:08:52> Server-001; Microsoft XML Core Services 6.0 (MSXML60); Passed<11-05-2009 22:08:52> Server-001; IIS service running; Passed <11-05-2009 22:09:52> Server-001; BITS installed; Error; Background Intelligent Transfer Service (BITS) is required for the management point and BITS-enabled distribution point site system roles. Background Intelligent Transfer Service (BITS) is not installed and/or IIS 6 WMI compatibility component for IIS7 is not installed on this computer or remote IIS host, or setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. ConfigMgr requires BITS be installed and enabled in Internet Information Services (IIS) before setup can continue. Setup cannot continue. <11-05-2009 22:10:52> BITSEXTS is not installed on Server-001. <11-05-2009 22:10:52> Server-001; BITS enabled; Error; Background Intelligent Transfer Service (BITS) is required for the management point and BITS-enabled distribution point site system roles. Background Intelligent Transfer Service (BITS) is not configured properly and/or IIS 6 WMI compatibility component for IIS7 is not installed on this computer or remote IIS host, or setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. ConfigMgr requires BITS to be installed and enabled in Internet Information Services (IIS) before Setup can continue. Setup cannot continue. <11-05-2009 22:11:22> Server-001; WebDAV installed; Error; Web-based Distributed Authoring and Versioning (WebDAV) is required for the management point and distribution point site system roles. If you have selected to install a site role requiring WebDAV, and it is not installed, this rule will fail. Web-based Distributed Authoring and Versioning (WebDAV) is not installed and/or IIS 6 WMI compatibility component for IIS7 is not installed on the computer specified for management point installation or setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. ConfigMgr requires WebDAV to be installed and enabled in Internet Information Services (IIS) for management point site systems. Setup cannot continue. <11-05-2009 22:11:52> WebDAV is not installed on Server-001. <11-05-2009 22:11:52> Server-001; WebDAV enabled; Error; Web-based Distributed Authoring and Versioning (WebDAV) is required for the management point and distribution point site system roles. If you have selected to install a site role requiring WebDAV, and it is not enabled, this rule will fail. Web-based Distributed Authoring and Versioning (WebDAV) is not enabled and/or IIS 6 WMI compatibility component for IIS7 is not installed on the computer specified for management point installation or setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. ConfigMgr requires WebDAV to be installed and enabled in Internet Information Services (IIS) for management point site systems. Setup cannot continue.<11-05-2009 22:11:52> ***************************************************<11-05-2009 22:11:52> ******* Prerequisite checking is completed. *******<11-05-2009 22:11:52> ***************************************************<11-05-2009 22:11:52> Updating Prerequisite checking result<11-05-2009 22:11:52> Connecting to Server-001 registry<11-05-2009 22:11:52> Setting registry values=========================================================================================================================ConfigMgrSetup.log===================== << Starting SMS V4 SP1 Setup >> =====================<11-05-2009 21:20:03> Commandline :"E:\SCCM07sp1\SMSSETUP\BIN\I386\SETUP.EXE" /prereq /input<11-05-2009 21:20:03> This is 64 bit.<11-05-2009 21:20:03> Verifying the Reg for AssetIntelligence Installation<11-05-2009 21:20:03> Setting the default CSV folder path<11-05-2009 21:20:04> SMS Build Number = 6221<11-05-2009 21:20:04> SMS Version = 4.0<11-05-2009 21:20:04> SMS Minimum Build Number = 800<11-05-2009 21:20:04> Verifying SMS Active Directory Schema Extensions.<11-05-2009 21:20:04> DS Root:CN=Schema,CN=Configuration,DC=AD,DC=DLA,DC=MIL<11-05-2009 21:20:04> Verifying SMS Active Directory Schema Extensions.<11-05-2009 21:20:04> DS Root:CN=Schema,CN=Configuration,DC=AD,DC=DLA,DC=MIL<11-05-2009 21:20:04> The command line options are /PREREQ <11-05-2009 21:24:56> IsValidNetBIOSName validation of 'Server-001' succeeded<11-05-2009 21:24:56> IsValidFQDN validation of 'Server-001.USE6.xyz.myCompany.com' succeeded<11-05-2009 21:24:56> IsValidNetBIOSName validation of 'Server-001' succeeded<11-05-2009 21:24:56> Registered type Server-001 MASTER for Server-001 master<11-05-2009 21:24:56> Registered type SMS Master for Server-001 master<11-05-2009 21:24:56> Registered type Server-001 SMS_ for Server-001 SMS_<11-05-2009 21:24:56> Registered type SMS ACCESS for Server-001 SMS_<11-05-2009 21:24:56> Start prerequisite checking.<11-05-2009 21:24:56> This is not cluster SQL.<11-05-2009 21:24:56> The prereq rules for primary site fresh installation are being run.<11-05-2009 21:24:56> Verifying SMS Active Directory Schema Extensions.<11-05-2009 21:24:56> DS Root:CN=Schema,CN=Configuration,DC=xyz,DC=myCompany,DC=COM<11-05-2009 21:24:56> NtfsDisable8dot3NameCreation is set to 0.<11-05-2009 21:24:56> Success in GetMMCVersion. Version is 3.0.<11-05-2009 21:24:56> .NET Framework Version: 50727<11-05-2009 21:24:56> NtfsDisable8dot3NameCreation is set to 0.<11-05-2009 21:24:56> Sql version is 10.0, 10.0.2531.0.<11-05-2009 21:24:56> NtfsDisable8dot3NameCreation is set to 0.<11-05-2009 21:24:56> This is a local site system. It does not check Admin$.<11-05-2009 21:24:56> NtfsDisable8dot3NameCreation is set to 0.<11-05-2009 22:08:51> The prereq rules for primary site fresh installation are being run.<11-05-2009 22:08:51> Verifying SMS Active Directory Schema Extensions.<11-05-2009 22:08:51> DS Root:CN=Schema,CN=Configuration,DC=xyz,DC=myCompany,DC=COM<11-05-2009 22:08:51> NtfsDisable8dot3NameCreation is set to 0.<11-05-2009 22:08:51> Success in GetMMCVersion. Version is 3.0.<11-05-2009 22:08:51> .NET Framework Version: 50727<11-05-2009 22:08:51> NtfsDisable8dot3NameCreation is set to 0.<11-05-2009 22:08:51> Sql version is 10.0, 10.0.2531.0.<11-05-2009 22:08:51> NtfsDisable8dot3NameCreation is set to 0.<11-05-2009 22:08:52> This is a local site system. It does not check Admin$.<11-05-2009 22:08:52> NtfsDisable8dot3NameCreation is set to 0.<11-06-2009 00:28:17> Completed prerequisite checking.===================== <<End >> =====================

Hi,Have you installed IIS 6 WMI compatibility component for IIS7?Jie-Feng Ren - MSFT

Here is the fix for our problem: Our work-a-round was Not to select and install the MP during the ConfigMgr setup. But to wait and install the MP after the setup was done. This also gives you better troubleshooting if needed where only one thing is happening at a time, and you can review the MP log files if needed. Surprisingly, we had no problems with installing the MP after the initial setup was done...Our best guess is that the Prerequisite Check part of the install was being blocked by some unknown security setting in our environment, and it could not see nor read the configuration settings for BITS and WebDAV. Both of which are required for a MP to install and work. Later, we also found out the Task Schedule we disabled by group policy, and we had to get an exception for that because it is also need to the MP. So the take-away from this is that the Prerequisite Check part of the ConfigMgr can give false positives. BITS and WebDAV were installed and setup correctly, but the Prerequisite Check could not see it. I work in a very secure and locked down environment where we run into situations that prevent default settings from working even when following best practices.

I am running the prerequisite checker on windows server 2003 which comes with IIS 6.0, the false error has do with BITS as stated above, but by your statement do I have to install IIS 7, if not were where can one download IIS 6 WMI compatibility component for IIS7.

This worked for me! I was trying to install SCCM 2007 on Windows Server 2008 R2, and got the same errors above related to Bits and Webdav. I installed SCCM with excluding the MP installation, and then later configured the MP. It looks like there is an issue with the logic in the installer. Great work around. Thanks!

I was trying to install SCCM 2007 on Windows Server 2008 R2, and I also got the same errors above and did not do the work around but added IIS 6 WMI role and prerequisite checker passed.

I had the exact same issue. Was about to move down to Windows 2003 as someone else posted that as the only fix. Thanks for posting this! It saved me about 8 hours unneeded work.

In Server MAnager, click on Roles in the left column, and scroll down to Web Server (IIS) in the right column. Check to see if you have IIS 6 WMI compatibiliity role installed. If not click Add Role Services and install it. This will fix all 4 messages.

Hello Everyone, I was encountering the same issue installing SCCM 2007 on Win2K3. After days of searching the resolution in Google with no results, I decided to try out something on my own and note this resolution is not there on any site. This is something that I tried and helped. RESOLUTION FOR ENABLING BITS in IIS is below. However, Web-based Distributed Authoring and Versioning (WebDAV) Can be enabled via the Add/Remove Windows Components Open ISS Manager -> Drill down to and click on Web Service Extension-> Add a new Web Service Extension name the Extension Name as "BITS Server Extension" -> Click Add -> Browse to C:\Windows\System32\bitsmgr.dll Click Add. Note in the System32 folder you will find bitsprx2.dll, bitsprx3.dll and bitssrv.dll .. Add all 4 of them. Once done close IIS and reboot. Then try to deploy Sccm and it should work. Hope this helps all those who have been searching for this crap as it took 6days for me to figure it out.. Rengi George

I followed this: http://technet.microsoft.com/en-us/library/cc431377.aspx and still had a problem - then did what b-ris did (add the iis 6 WMI compatibility role) and it seems to have worked.

I Had the same problem it got fixed after I installed the IIS 6 WMI compatibiliity role. Thanks

Hi, I tried your solution but no resolution, still the problem is there, just to confirm if we are on the same page. Once I create the extension do I run the Pre-Req Checker again or just install SCCM 2007 ( i am on WIN2k3) Thanx Kash