How to Create a Client Package for Configuration Manager OSD Deployment.
OSD (Operating System Deployment) is a feature of Configuration Manager (SCCM) that enables administrators to deploy operating systems to computers in an organization. SCCM OSD can be used to deploy Windows operating systems, applications, and software updates to computers.
Here are the steps involved in deploying an operating system using SCCM OSD:
- Create a boot image: A boot image is required to start the deployment process. The boot image can be created in the SCCM console and can be customized to include additional drivers or utilities.
- Create a task sequence: A task sequence is a set of instructions that defines how the operating system will be deployed. The task sequence can be created in the SCCM console and can include steps for partitioning the hard drive, installing the operating system, and installing applications.
- Import operating system image: The operating system image must be imported into SCCM before it can be deployed. This can be done in the SCCM console by importing a Windows image file (WIM).
- Deploy the operating system: Once the task sequence and operating system image are in place, the deployment can be initiated. This can be done through the SCCM console or by using PXE boot to boot the computer to the SCCM server.
- Monitor the deployment: The SCCM console provides real-time monitoring of the deployment process. This allows administrators to track the progress of the deployment and troubleshoot any issues that may arise.
SCCM OSD provides a powerful and flexible way to deploy operating systems to computers in an organization. It can save time and resources by automating the deployment process and ensuring consistency across all computers in the organization.
Create Client Package for OSD deployment
1. Start SCCM Console and navigate to Software Library\Application Management\Packages;
2. Click Create in the upper menu and click Create Package from Definition;
3. For Package Definition, Select Configuration Manager Client Upgrade and click Next;
4. For Source Files, select Always obtain source files from a source folder and click Next;
5. For Source Folder, enter the path to client installation files (I use Local folder C:\ Program Files\Microsoft Configuration Manager\Client). Click Next;
6. For Summary, click Next;
7. Click Close;
8. Package created;
9. Also, you may open Properties and enable the option Allow this package to be transferred via multicast (WinPE only) in the Distribution Settings tab;
10. Don’t forget to Distribute Content to the distribution point before creating an OSD task;
Hello,
Is this the only way the client package can be used for MultiCast in OSD ?
Hi. Not the only one (you can use powershell) but the simplest.
thanks
how to learn scripts?
Hi. In my vision you have 3 paths:
1. Online courses (paid or free)
2. Self-learning (books, manuals)
3. Take some simple task and break it to simple tasks. Then google each step and code it (StackOverflow help you, in some cases TechNet), this is the practice path
4. Combo of some steps