Dear all
Greetings! Would like to know the pros and cons of Windows provisioning packages over a traditional imaging(SCCMOSD/MDT).
Regards
Aravinth M
Hi, @AravinthMathan-3183
Thank you for posting in Microsoft Q&A forum.
The benefits of provisioning packages：
1.Quickly configure a new device without going through the process of installing a new image.
2.Save time by configuring multiple devices using one provisioning package.
3.Quickly configure employee-owned devices in an organization without a mobile device management (MDM) infrastructure.
4.Set up a device without the device having network connectivity.
For the disadvantages, it is suited for small- to medium-sized businesses with deployments that range from tens to a few hundred computers. For larger companies, they will want to use SCCM,MDT or some type of network based deployment where you can do multiple machines at once.
Here is a discussion about this topic for your reference:
https://community.spiceworks.com/topic/2080870-provisioning-vs-imaging-windows-10
(Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.)
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hello,
SCCM is an on premise tool that performs many functions in addition to Operating System Deployment (OSD) however
1.Boot Media
This is a Light Touch deployment requiring physical access to each device. It is well suited to small remote offices or a small staging area without OSD infrastructure (Distribution Points etc.).
SysAdmin creates a custom Windows Image, driver package(s) and task sequence
SysAdmin either creates boot media
Boot media is distributed to required locations
Each device is booted with the boot media and the task sequence builds the device
Applications can be added in the task sequence or post OSD through SCCM’s Software Deployment functionality
Pros
Minimal network impact
Minimal infrastructure requirements
Cons
Requires visiting each device (Light Touch)
Boot media management overhead
PXE Boot
This is a Light Touch deployment requiring physical access to each device to enter PXE boot – This can be made Zero Touch if the boot order is set to PXE first however, this is not a sustainable configuration. It is well suited to a large staging are or small remote offices with OSD infrastructure (Distribution Points etc.).
SysAdmin creates a custom Windows Image, driver package(s) and task sequence
Sysadmin deploys task sequence to a collection of devices
Devices are booted and forced into network boot
The device finds a boot image from the SCCM Distribution Point and
Each device is booted with the boot media and the task sequence builds the device
Applications can be added in the task sequence or post OSD through SCCM’s Software Deployment functionality
Pros
No media management
Easy modification of task sequences, boot images and driver packages
Cons
Requires visiting each device (Light Touch)
Requires complex infrastructure
Deployed Task Sequence
This is a true Zero Touch deployment that can be used a Self-Service option as well as a scheduled mandatory deployment. It can even be coupled with Wake-on-Lan to target devices that are powered off (but still connected to the network. This is well suited to upgrading or refreshing large numbers of devices currently in use as it requires that each device is already managed with SCCM.
SysAdmin creates a custom Windows Image, driver package(s) and task sequence
Sysadmin deploys task sequence to a collection of devices
Task sequence is executed on device (Self-serve or scheduled)
Required files are copied to the device and the device reboots and the task sequence deploys the operating system
Applications can be added in the task sequence or post OSD through SCCM’s Software Deployment functionality
Pros
No requirement to visit each device (True Zero Touch)
No media management
Easy modification of task sequences, boot images and driver packages
Supports Self Service
Supports Scheduling
Cons
Requires complex infrastructure
Only available to existing SCCM clients
--If the reply is helpful, please Upvote and Accept as answer--
24 people are following this question.
