The official blog of the Microsoft System Center Configuration Manager Product Group
The Configuration Manager console has been greatly improved in System Center 2012 Configuration Manager, which enhances its usability. In addition to improvements in performance and layout, the console now supports a quicker way to monitor the status of distribution point site system roles.
Using this new monitoring capability, you might see that the installation of a distribution point on a computer other than the site server (known as a remote distribution point) displays an error, with the message Failed to create virtual directory. This failure often indicates that the distribution point computer must be rebooted so that the IIS installation and configuration can complete. This might not be the only reason for this error, but try the following process to resolve the problem:
The following screenshot shows an example of this Failed to create virtual directory error:
Note: There is a known issue in the current release where the error might not always clear to return the distribution point status back to a success state. We hope to address this issue in a future release.
If you double-click this message, the following dialog box provides more detailed information:
To see whether you have resolved the problem, refresh the Configuration Manager console, and look for the new messages IIS was configured successfully and Content was distributed to distribution point:
For more information about managing the content library in System Center 2012 Configuration Manager, see Content Management in Configuration Manager in the System Center 2012 Configuration Manager Documentation Library.
This posting is provided "AS IS" with no warranties, and confers no rights.
thanks for the info. In my case the management point msi was failing to install. There were errors in the application log file to this effect. I manually ran the mp.msi file from \program files\Microsoft COnfiguration Manager\bin\x64\mp.msi and got error saying that IIS wasn't started. Turned out my default website was site ID=3. This can be checked using IIS Mgr and expanding the left tree down the Sites, then on the right side view the list of sites shows the ID column. Mine was 3, it seems that SCCM needs the default site to have an ID=1. To change it, run net stop was, answer Y to stop the listed services. Edit the file %WINDIR%\System32\inetsrv\config\applicationHost.config and search for ID="3" (or whatever your default site id currently is) and change it to 1. Save the file and then net start w3svc. Retry the installation of the management point (I ran the mp.msi file manually) and it should then be successful.
Hope it helps someone else.
So was this issue pre or post SP1 ?
We have this issue on a couple of remote DPs and even though they have successfully recieved content and the IIS dirs are there, the error has not cleared. Been over 2 months on one of the dps.