Recently Microsoft has released Configuration Manager update 1910 and It should take few weeks of time to reflect in the console. Until then we can either wait for the update to be globally available or we run the EnableEarlyUpdateRing 1910 script to enable fast ring for 1910 update package available in ConfigMgr Current Branch.

EnableEarlyUpdateRing 1910 script

Download the Powershell script from Technet . This script will allow us to enable fast Update-ring in ConfigMgr Current Branch.
On your SCCM server, run the PowerShell as administrator and run the script. Enter the site server name and script gets the update 1910 in console for you.

Before running the Script ,

After executing the Script , Configuration Manager update 1910 available to download in Console.

This guide provides step by step instructions to install PXE role, Creation of boot image, Creation of OS image, Creation of OSD task sequence and deploying Windows 10 OS via PXE boot on SCCM 1902 lab environment.

Enable SCCM PXE Role

First we need to prepare environment for configuration manager OSD. we have to create Network Access account in Active Directory and this account is used by the client to access the Configuration Manager Distribution point when booted under WinPE so make sure the account has the necessary permission for this action. Then we have to Enable PXE role on our SCCM server.

Follow the Below Steps to Enable PXE support,

Open the SCCM Console
Go to Administration / Site Configuration / Servers and Site System Roles
Select your distribution point and right-click on the Distribution point role on the bottom, select Properties

Select the PXE tab
Enable the Enable PXE support for Clients check-boxandanswer Yes when prompted about firewall ports (UDP ports 67, 68, 69 and 4011 )

Check the Allow this distribution point to respond to incoming PXE requests check box
Check the Enable unknown computer support check box
Ensure that the Respond to PXE request on all network interfaces is selected Click OK

Go to Monitoring / Distribution Status / Distribution Point Configuration Status
Click your distribution point on the top and select the Details tab on the bottom
We will see that the distribution point PXE settings has changed

BOOT Image Distribution

Here we are going to use the default SCCM boot image,
Open the SCCM Console, Go to Software Library / Operating Systems / Boot Images, Right-click Boot Image (X64) and distribute to DPs.

Add Operating System Image

Launch the Configuration Manager console, click on Software Library, click Operating Systems, right click on Operating systems images and click on Add Operating System Image.

Specify the path where the install.wim is present. Click Next.

Provide details for the operating system image. Click Next.

Click Next and click close.

Distribute the image into DPs

Select the Distribution Point

Click Next and Close

Configure Network Access account and this account is used by the client to access the Configuration Manager Distribution point when booted under WinPE

Specify Network Access account

Task Sequence Creation

Launch the Configuration Manager console, click on Software Library, expand Overview, expand Operating Systems, right click Task Sequences and click Create Task Sequence.

Type Task sequence Name

Select Boot Image

Select Operating System Image

Select Image Index ,type the Product Key ,type Local Administrator password and Next

Configure Domain Join Account

Select Join a Domain and browse the Domain OU and Click Next

Select Configuration Manager Client Package

Click Next since we are not using State Migration here

Select the Appropriate Software Update option, here i have selected Do not install any software updates

Select the Application Which we want to install during the task sequence

Click Next and Close

Task sequence has been created successfully, below is our basic win 10 task sequence view

Deploy task sequence into Unknown Computer Collection

Select task sequence right click and Click Deploy

Select All unknown Computers collection

And Select Pupose & Make available to PXE and Click Next

Select the Deployment schedule and click Next

Select User experience Option as per below and Click Next

Select deployment options as download locally and click Next

Verify the Summary and click Next

The Deploy task sequence wizard completed Successfully

Deploying Windows 10 via PXE boot

Here I have prepared another hyper V host and deploying windows 10 via configured PXE boot

Press F12 to boot from the network and the machine will get IP from DHCP, Contacting PXE server,Downloading and initiating the Boot Image

Task sequence wizard will appear and type task sequence password

Click Next

Task sequence variable will appear and Type the OSDComputerName

Click Next

Partition Disk stage Running

Applying Operating system stage Running

Setup Windows and Configuration Manger Stage Running

Setup Windows completed and Auto reboot initiated

Post Reboot, System Initiating

Imaging Completed and type the Administrator password to login,

Verify the same from smsts.log

Windows 10 deployment completed Successfully.

Thank You:-)

Configuring SCCM Discovery

Configure discovery methods to find resources to manage from from network and Active Directory. Discovery creates a discovery data record (DDR) for each discovered object and stores this information in the SCCM database. When a resource is discovered the information about the resource is put in a file that is referred to as a discovery data record (DDR).
For More Info:- https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/configure-discovery-methods

Discovery Methods

Active Directory Forest Discovery – This method discovers Active Directory sites and subnets.
Active Directory Group Discovery – This method discovers groups from the defined location in the Active Directory.
Active Directory System Discovery –This method discovers the computers in your organization from specified AD locations.
Configuration Manager Active Directory User Discovery – This Discovery process discovers the user accounts from your Active Directory domain.
HeartBeat Discovery – This is the only discovery method that is enabled by default. The HeartBeat Discovery runs on every SCCM client and is used by Active Configuration Manager clients to update their discovery records in the database. Furthermore the records are sent to the management point in specified duration of time.
Network Discovery – The Network Discovery searches your network infrastructure for network devices that have an IP address. It can search the domains, SNMP devices and DHCP servers to find the resources. This includes printers, routers, and bridges.

Below is the discovery methods from Console

Enable Active Directory Forest Discovery

  In the Configuration Manager console, click on Administration and select Hierarchy Configuration, click on Discovery Methods. The first discovery method listed is Active Directory Forest Discovery. To discover Active Directory network locations and convert those locations into boundaries right click Active Directory Forest Discovery for the primary site and right click, choose Properties. Enable Active Directory Forest Discovery

 

Review the discovery of objects via ADForestDisc.log file located in <InstallationPath>\LOGS path

Enable Active Directory Group Discovery 

In the ConfigMgr console, in the Administration workspace, select Hierarchy Configuration, then select Discovery Methods and right click Active Directory Group Discovery and choose properties.  The Active Directory Group Discovery Properties window appears. Select the option to Enable Active Directory Group Discovery and click on Add to see two more choices, Groups and Location. Select Location and select the previously created windowsnoob Organizational Unit (OU) which will contain your servers, users, computers and devices.

Review the discovery of objects via ADsgDis.log file

Enable Active Directory System Discovery 

In the ConfigMgr console, in the Administration workspace, select Hierarchy Configuration, then select Discovery Methods and right click Active Directory System Discovery and choose Properties, place a check mark in Enable Active Directory System Discovery. Click on the yellow starburst to add Active Directory containers. For path click on browse and browse to the location you want to discover systems in.

Review the discovery of objects via ADsysDis.log file

Enable Active Directory User Discovery 

In the ConfigMgr console, in the Administration workspace, select Hierarchy Configuration, then select Discovery Methods and right click Active Directory User Discovery and choose Properties. Place a checkmark in Enable Active Directory User Discovery  and click on the yellow starburst to add active directory locations to discover users.

Review the discovery of objects via ADusrDis.log file

Review discovered resources in the console

Discover enabled view from Console

Discovered System resources

Discovered User resources

Configure SCCM Boundaries

As per Microsoft, a boundary is a network location on the intranet that can contain one or more devices that you want to manage. Boundaries can be either an IP subnet, Active Directory site name, IPv6 Prefix, or an IP address range.
To use a boundary, you must add the boundary to one or more boundary groups. Boundary groups are collections of boundaries. By using boundary groups, clients on the intranet can find an assigned site. In addition to that they can locate content such as applications, software updates, and operating system images. Active Directory Forest Discovery discovers boundaries automatically.

To create boundries in SCCM,
Open the SCCM Console-Go to Administration / Hierarchy Configuration / Boundary-Right-click Boundaries and select Create Boundary

Here i have used Active Directive Site

Here boundary has been created and reflected in Console

Create Boundary Group

We need to add the Boundary to the Boundary groups. To do so Select Boundary Groups, right Click and create a boundary group. Provide a name as First Boundary Group. Click Add. Select the boundary which we created Vcloud.com AD Site and Click OK. Click on references tab, check Use this Boundary group for site assignment. To add the site system servers, click Add and select the Site System Server. Click OK.

Newly Created Boundary group reflected in Console