Install IIS Base Components on SCCM Distribution Point
This post shows the steps to install IIS base components on SCCM distribution point. I could also say it helps you fix the error “Failed to create virtual directory” on distribution point. When you install SCCM distribution point role, sometimes it doesn’t install well. Today when i was installing distribution point role on a remote server I experienced an error. Listed below are the troubleshooting steps that helps you to fix the issue.
Error – Failed to create virtual directory on the defined share or volume on distribution point.
Possible cause: Distribution Manager requires that IIS base components be installed on the local Configuration Manager Site Server in order to create the virtual directory. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS).
Solution: Verify IIS base components installed on the local Configuration Manager Site Server, IIS Web Services installed on the Distribution Point Server.
Install IIS Base Components on SCCM Distribution Point
Troubleshooting :-
- If you are looking to install the missing IIS base components, then you can use the below command. Run the PowerShell as administrator and copy the below command and run it. This will install the IIS components required for setting up distribution point. For me running the below command fixed the issue. Without any reboot the DP status changed to green (healthy).
dism.exe /online /norestart /enable-feature /ignorecheck /featurename:"IIS-WebServerRole" /featurename:"IIS-WebServer" /featurename:"IIS-CommonHttpFeatures" /featurename:"IIS-StaticContent" /featurename:"IIS-DefaultDocument" /featurename:"IIS-DirectoryBrowsing" /featurename:"IIS-HttpErrors" /featurename:"IIS-HttpRedirect" /featurename:"IIS-WebServerManagementTools" /featurename:"IIS-IIS6ManagementCompatibility" /featurename:"IIS-Metabase" /featurename:"IIS-WindowsAuthentication" /featurename:"IIS-WMICompatibility" /featurename:"IIS-ISAPIExtensions" /featurename:"IIS-ManagementScriptingTools" /featurename:"MSRDC-Infrastructure" /featurename:"IIS-ManagementService"
2. Reboot the distribution point server and then try distributing the content again. However before the content is distributed, check the distribution point status. Click on Monitoring and click Distribution Point Configuration Status. Click the distribution point server and you should see status of server as green.
3. Finally check the message to see IIS configuration is successful. Check the message to see the content is distributed to the distribution point. Also here is a good link to verify successful DP installation.
Was having this same issue with my distribution point after upgrade to 1811. Ran the script and restarted the server and Distribution Point Status returned to healthy. Thank you for publishing this solution and it probably saved me many hours of troubleshooting.
Thank you. Glad to hear that.
Hello Prajwldesai
I ‘m using Windows server 2008 SP2 As a DP.
I my SCCM version si 1702.
As we now dism.exe does not work with windows server 2008 SP2
I think that I must use this commande :
pkgmgr /norestart /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS-ISAPIExtensions;IIS-WindowsAuthentication;IIS-ManagementScriptingTools;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-ManagementService;WAS-ProcessModel;WAS-WindowsActivationService;WAS-NetFxEnvironment;WAS-ConfigurationAPI;MSRDC-Infrastructure;IIS-HttpLogging;IIS-LoggingLibraries;IIS-HttpTracing;IIS-CustomLogging;IIS-ODBCLogging
But unfortunately it does not work
Hello Prajwldesai
I ‘m using Windows server 2008 SP2 As a DP.
I my SCCM version si 1702.
As we now dism.exe does not work with windows server 2008 SP2
I think that I must use this commande :
pkgmgr /norestart /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS-ISAPIExtensions;IIS-WindowsAuthentication;IIS-ManagementScriptingTools;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-ManagementService;WAS-ProcessModel;WAS-WindowsActivationService;WAS-NetFxEnvironment;WAS-ConfigurationAPI;MSRDC-Infrastructure;IIS-HttpLogging;IIS-LoggingLibraries;IIS-HttpTracing;IIS-CustomLogging;IIS-ODBCLogging
But unfortunately it does not work
Received the exact same error when setting up a new distribution point. Noticed that IIS was stopped (on the new dist point) but I couldn’t start it. Ran this PS script and could then start the “Default Web Site” in IIS. Everything is working now – Green lights in SCCM (Distribution Point Configuration Status)! I spent hours researching this issue and trying things – this solution saved me many more hours of pain! Thank you so much!!
Thank you Ed.
Thank you for this, it worked perfectly on my issue.
Thank you Shane
Thank You Sir,
Now issue has been resolved.
Thank you
Thanks Sir, Now issue has been resolved.
Thank you Santosh
Hi Praj,
You saved my time lot !! Thanks
Thank you Arun.
if i want to install the base components on a windows server 6.0.6002 which don`t have powershell..
can you give me a similarly cmd command instead
Thank you…this little tidbit helped avoid any additional headaches.
Thank you George
Hi Prajwal,
Is there any advantage of using dism over add-windowsfeature native powershell command ?
Good question. Here is the answer – https://peter.hahndorf.eu/blog/WindowsFeatureViaCmd.html
Thank you nice to know…