Sunday, January 10, 2016

Step by step guide to setup SCCM 1511 Distribution Point

Microsoft System Center Configuration Manager uses distribution points to store files needed for packages to run on client computers.
The client computers will access the distribution point share for source files when a deployment is received.
in order to clients to access the source files from the distribution point, the source files must be copied to distribution points.

To use a server as a distribution point for providing packages to distribute packages to client computers, we must first designate a site system as a distribution point.
We can designate a distribution point either when creating a new site system or by adding the distribution point site role to an existing site system.

Additional configuration is required when we use the distribution point as a PXE point to deploy operating system (OSD).

Prerequisites for distribution Point:
Windows Features:

·         .NET Framework 3.5: Including
.Net Framework 3.5 (Includes .NET 2.0 and 3.0)
·         .NET Framework 4.5.2: Including


•  IIS configuration:
•Application Development:
ISAPI Extensions
Windows Authentication
•IIS 6 Management Compatibility:
IIS 6 Metabase Compatibility
IIS 6 WMI Compatibility
•Common HTTP Features:
HTTP Redirection
•IIS Management Scripts and Tools
• Remote Differential Compression
• Windows Deployment Services (WDS) (If PXE enabled)

Firewall exceptions:
·         TCP 135
·         TCP 445
·         UDP 135
For PXE:
·         UDP Port 67
·         UDP Port 68
·         UDP Port 69
·         UDP Port 4011

Open the Config Manager console, then go to \Administration\Overview\Site Configuration\Servers and Site System Roles, then Right click on Servers and Site System Roles then select Create Site System server;

Select desired server under Select a server to use as site system.
Enter the FQDN of the server name or use the browse option to browse the server name in AD.
Select Use the site server’s computer account to install this site system then click next;

Specify internet Proxy server details if applicable then click next;

Select Distribution Point role under specify roles for this server then click next;

On Specify distribution point settings;
Under A distribution point contains source files for clients to download
-          Select Install and configure IIS if required by Configuration Manager
Under Specify how client computers or mobile devices communicate with this distribution point
-          Select HTTP
Under Create a self-signed certificate or import a PKI client certificate
     -       Select Create self-signed certificate (this is the default selection when selected HTTP option)

On drive settings for this distribution point window, use the default values unless you want to specify a particular size and drive then click next;

Click next on Specify settings to configure a Pull Distribution Point without making any changes as we are not using the pull distribution point;

On Specify settings to install operating systems by using PXE boot;
-          Select PXE support for clients (do not select this option if you want to enable PXE on this DP)
NOTE: Enabling PXE on a DP will install WDS on the server
-          Select Allow the distribution point to respond to incoming PXE requests
-          Select Enable unknown computer support
-          If you want to enable password on the task sequence, then select Require a password when computers use PXE
-          Select Respond to PXE PXE requests on all network interfaces

Select desired option on specify multicast settings for operating system deployment. 
NOTE: Before enable multicast option review the multicast requirements and supporting infrastructure

On Specify the content validation settings page select desired option.
If content validation is enabled, then setup schedule how frequently you want to run content validation. 
NOTE: Content validation may generate high network traffic and may cause network congestion on slower links 

Specify a boundary group to associate with this site system by using Add option. 
Also specify desired option for Allow fallback source location for content then click next;

Confirm all the settings before we proceed with adding the Distribution Point role.

If everything configured correctly, the Add site system role wizard will complete successfully.

Verify distmgr.log for detailed installation status. Also you can review the status of the distribution point is Distribution Point Configuration Status under Monitoring node.

In some occasions, you may see below error under Distribution Point Configuration Status soon after you complete the installation of the new distribution point.

Error:Failed to create virtual directory on the defined share or volume on distribution point "["Display=\\<DP server name FQDN>\"]MSWNET:["SMS_SITE=SCB"]\\<DP server name FQDN>\".

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 that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server.

When you see the above error under the DP configuration status node, none of the packages will distribute to the distribution point.

What  noticed was, even though the distribution point creation completed, the system is still in the process of creating and configuring the required components. 
So leave the server running for few hours then check the status. Eventually the error msg will disappear and all the failed packages will redistribute successfully.

Click here for complete SCCM 1511 Current Branch setup step by step guide.

Click here for complete SCCM 1511 Current Branch step by step guide, step by step migration guide, step by step monitoring and health check guide and step by step SCCM Current Branch servicing guide.

No comments:

Post a Comment