В этой статье мы рассмотрим, как автоматически развертывать Windows 10 по сети с помощью SCCM (System Center Configuration Manager) и PXE. С помощью данной методики вы можете существенно сократить время на установку ОС рабочих станций и использовать для массового развертывания Windows 10 на новых компьютерах.
Одна из функции SCCM — возможность сетевой установки операционной системы Windows системы на большое количество компьютеров вместе с драйверами, программами, обновлениями. Предполагаем, что у вас уже имеется настроенная инфраструктура SCCM.
Содержание:
- Настройка PXE роли на SCCM сервере для сетевой установки Windows
- Создание настроенного эталонного образа Windows 10
- Создаем загрузочный образ для захвата эталонного образа Windows 10
- Создаем последовательность задач (Task Sequence) для сетевой установки Windows
- Добавление драйверов в загрузочный образ Windows
- Настройка PXE на компьютерах
- Установка приложений на новый компьютер с помощью SCCM
Настройка PXE роли на SCCM сервере для сетевой установки Windows
Функционал PXE (Preboot Execution Environment) в современных компьютерах позволяет выполнить сетевую установку операционной системы без применения каких-либо носителей. В SCCM его настройка происходит в окне свойств роли точки распространения (в контекстном меню вам нужно выбрать пункт Properties) и установить флажки:
- Enable PXE support for client;
- Allow this distribution point to respond to incoming PXE request;
- Enable unknown computer support;
- Require a password when computers use PXE.
Также желательно выбрать из выпадающего списка Allow user device affinity with automatic approval.
После включения этих настроек на сервере будет установлена роль Windows Deployment Services, интегрированная с SCCM.
Создание настроенного эталонного образа Windows 10
Следующий этап – подготовка эталонного образа с Windows 10, который будет устанавливаться на другие компьютеры. Проще всего взять типовой компьютер, установить на него Windows 10. Установите последние обновления безопасности, отключите ненужные службы, удалите встроенные приложения, установите драйвера. Настройте Windows 10 в соответствии со своими требованиями. Это компьютер не нужно вводить в домен AD.
Создаем загрузочный образ для захвата эталонного образа Windows 10
По умолчанию SCCM содержит образы Windows PE (среда предустановки Windows, это загрузочные файлы Boot image x86.wim и Boot image x64.wim), которые необходимы для настройки операционной системы во время “захвата”.
Сначала нужно добавить образ Boot image x64.wim в вашу точку распространения SCCM. Для этого зайдите в Software Library-> Operation System-> Boot Images, в контекстном меню выберите пункт Distribute Content, затем точку распространения и ОК. Цветовой окрас состояния сменится с серого на жёлтый, а по окончанию – на зелёный.
Теперь нужно создать иметь загрузочные файлы для “захвата” эталонной операционной системы по сети. Для их создания перейдите в Software Library-> Operation System -> Task Sequences и в контекстном меню выберите Create Task Sequence Media. В появившемся окне предлагается 4 варианта создания образа:
- Stand-alone media — создание автономного образа для установки ОС (локальная установка, без использования сетевой загрузки);
- Bootable media – создание загрузочного образа, для распространения которого используя инфраструктура центра конфигураций;
- Capture media – создание загрузочного образа для захвата эталонного образа компьютера;
- Prestaged media – создание предварительного образа для нового жёсткого диска, который включает образ операционной системы. Используется для старых карт, не поддерживающих PXE загрузку.
Выберите пункт Capture media, следуйте подсказкам мастера установки. Укажите место сохранения iso-файла, выберите Boot image x64.wim и точку распространения, Next->Next->Close. Процесс длится около 1 минуты.
Далее созданный полученный образ для захвата ОС нужно подключить и запустить на подготовленном ПК (файл LaunchMedia.cmd). Укажите место сохранения полученного образа Windows 10.
Весь процесс захвата длится примерно 40 минут. По окончании получаете эталонный wim-образ размером примерно 4.5 Гб, который нужно скопировать на сервер SCCM. Далее вам необходимо его добавить в точку распространения. Для этого заходите в Software Library -> Operation Systems -> Operation System Images, в контекстном меню выберите пункт Add Operation System Images, в мастере настроек укажите UNC путь к месту хранения созданного wim-файла с эталонным образом.
В контекстном меню выберите Distribute Content для копирования образа на вашу SCCM Distribution Point.
Создаем последовательность задач (Task Sequence) для сетевой установки Windows
Последовательность задач SCCM (task sequence) обеспечивает пошаговое выполнение команд и действий по установке ОС, ПО, драйверов, обновлений. Для её создания зайдите в Software Library -> Operation System -> Task Sequences и в контекстном меню выберите Create Task Sequence. В появившемся окне мастер предлагает несколько вариантов:
- Install an existing image package –создание очереди задач для имеющегося wim образа;
- Build and capture a reference operating system image –захват эталонного образа;
- Create a new custom task sequence – создание нового пустого задания (настройка выполняется вручную). Отсутствует очередь задач по умолчанию.
Так как эталонный образ wim образ у вас уже есть, выберите первый пункт. Далее мастер предлагает поэтапно произвести большое количество настроек, но можете указать только минимально необходимые параметры:
- Укажите название задачи и выберите загрузочный PXE образ Boot image x64.wim;
- Выберите созданный ранее эталонный образ Windows 10;
- Установите пароль локального администратора (можно автоматически сменить пароль после добавления компьютера в домен с помощью LAPS);
- Настройте параметры автоматического присоединения в домен AD, выбрав домен и OU, в которую нужно поместить новый компьютер;
- Выберите пользователя, под которым будет осуществляться добавление в домен;
- На шаге State Migration убрать все флажки (Capture user settings and files, Capture network settings, Capture Microsoft Windows settings).
Последовательность задач создана, но она требует от вас корректировки и проверки. Перейдите в режим редактирования Task Sequence, выбрав в контекстном меню пункт Edit.
В дереве справа указан список действий, которые автоматически будут выполнены с компьютером при установке Windows 10 по сети. На 2 и 3 шаге указываются параметры разбиения дисков на разделы. На шаге 2 вы можете удалить все разделы жёсткого диска, созданные по умолчанию, если вы их не используете для восстановления Windows. Далее создаёте новый раздел, называете “C:”, выбираете тип Primary, устанавливаете фиксированный размер 50 Гб (или другой объём), выбрав опцию Use specific size. Выберите что диск нужно отформатировать в файловой системе NTFS (флажок Quick format).
Далее создаёте второй диск, называете “D”, выбираете тип Primary. Чтобы он занял все оставшееся неразмеченное пространство выберите опцию Use a percentage of remaining free space, выберите значение 100, файловую систему NTFS и флажок Quick format.
Таким образом у вас будет создан диск С: с фиксированным размером, а всё оставшееся место уйдёт диску D: (если объём жёсткого диска большой, то можно разбить его на большее количество разделов), которые будут отформатированы автоматически.
3й шаг в нашем примере удаляется, т.к. у нас компьютеры с BIOS. Для компьютеров с UEFI – нужно настраивать дисковые разделы именно в 3 пункте.
На следующем шаге – Apply Operating System – нужно выбрать раздел для установки операционной системы. Проверяете наличие эталонного образа, а внизу окна выбираете установку Windows на:
- Specific disk and partition — конкретный номер диска и номер раздела;
- Specific logical drive letter – указанный логический диск;
- Logical drive letter stored in a variable —
Например, будет второй пункт и диск С: .
Остальные шаги проверяете на отсутствие ошибок. На шаге Apply Windows Settings нужно указать лицензионный ключ (можно указать ключ KMS активации), пароль администратора и часовой пояс. Корректировка доменных (сетевых) настроек происходит в Apply Network Settings, а Apply Device Drivers позволяет добавить драйвера в установку.
Далее новое задание нужно опубликовать. Для этого в контекстном меню выберите пункт Deploy, на первом шаге мастера выбираете коллекцию устройств All Unknown Computers, на 2м шаге параметру Purpose присваиваете значение Available (Available – доступно для выбора, Required – принудительная установка), в параметре Make available to the following выберите Configuration manager clients, media and PXE, остальные шаги можно оставить по умолчанию.
В SCCM коллекцию All Unknown Computers попадают все компьютеры, о которых в SCCM нет никакой информации. Такими ПК могут быть новые или не подключенные к домену.
На этом основные действия по подготовке эталонного образа и настройке SCCM завершены.
Добавление драйверов в загрузочный образ Windows
Рассмотренных выше действий будет достаточно для автоматической установки Windows 10 на новые современные миниатюрные системные блоки или моноблоки. В случае с классическими системниками и внешними сетевыми картами загрузка по сети может не заработать. В этом случае необходимо в загрузочный образ добавить драйвера для используемых моделей сетевых адаперов.
Для добавления драйвера в базу сайта SCCM перейдите в Software Library -> Operation Systems -> Drivers и в контекстном меню выберите Import Driver. Далее мастер поможет заполнить необходимые поля. Нужно UNC путь к каталогу с драйвером и установить для параметра Specify the option for duplicate drivers значение Do not import the driver.
Затем нужно зайти в свойства загрузочного образа Boot image x64.wim и на вкладке Drivers добавить драйвера.
Настройка PXE на компьютерах
На компьютерах, которые вы хотите деплоить по сети нужно включить в BIOS поддержку сетевой загрузки. У разных производителей материнских плат такие настройки будут находится в разных местах и называться по-разному. Скорее всего в названии параметра сетевой загрузки должно быть что-то вроде PXE Boot, Network Boot, Network Card.
Например, активация PXE в UEFI моделях HP Pro 3520 и HP Pro 6300 происходит в разделе Security -> Network Boot установкой параметра Enable.
Теперь для старта всё готово. При начальной загрузке ПК происходит определение его параметров (POST). Затем DHCP сервер назначает IP-адрес сетевой карте. Для начала сетевой установки ОС в течение 5 секунд нужно нажать клавишу F12 (означает PXE-подключение), после чего SCCM копирует на ПК загрузочные файлы (в моделях HP нужно нажимать на F9, возможно дополнительно ещё выбрать пункт Network Controller для загрузки по сети).
Далее появляется окно для выбора задачи, после чего начинается поэтапное развёртывание операционной системы, то есть выполнение тех действий, которые указаны в вашем Task Sequence. Ход установки отслеживается при помощи индикатора. Примерно за 20 минут ваш эталонный образ Windows 10 будет установлен на новый ПК и компьютер введен в домен. Если одновременно запустить сетевую установка Windows с SCCM на 10-20 компьютерах, время установки может немного увеличиться.
По окончанию установки ОС компьютеру по умолчанию присваивается имя MININT-<7символов>, например, MININT-5EFG9DR. Это можно увидеть в консоли SCCM в разделе Assets and Compliance -> Devices. Вы можете изменить имя компьютера на более запоминающееся, например, BUH-OLGA. Для этого нужно зайти в Свойства компьютера -> Изменить параметры -> Изменить, указать новое имя компьютера и перезагрузить ПК. Вскоре изменения отобразятся как в DNS, так и в SCCM.
Установка приложений на новый компьютер с помощью SCCM
Следующие этап установка на новый компьютер необходимых приложений. Программы можно устанавливать в виде пакета (Package) или как приложение (Application). Приложения – программы, имеющие установочные файлы с расширениями msi, appx, xap, ipa, apk и прочее. У Application возможностей больше, плюс пользователи тоже могут принимать участие в работе. Package – это специальный контейнер (обёртка), который может включать в себя несколько файлов (дистрибутивов). Используются exe-, vbs-, cmd-, cab-файлы и другие. Он проще в настройках.
Мы не будем подробно описывать особенности развертываний программ в SCCM, т.к. эта получится отдельная большая статья. Для ознакомления вы можете посмотреть пример развертывания Office 2016 с помощью SCCM.
После создания пакетов установки программ, вы можете добавить из в последовательность задачи развертывания Windows 10 (task sequence)/
Здесь создаёте группу Software Install, в меню Add -> Software -> Install Package добавьте созданные пакеты программ.
This is a complete guide to deploy Windows 10 21H2 using SCCM or ConfigMgr. We will use SCCM task sequence to deploy Windows 10 21H2 to laptops.
To deploy Windows 10 21H2 using ConfigMgr, you first need to have the Windows 10 21H2 ISO file with you. You can either download the ISO from Visual Studio subscriptions or Microsoft VLSC portal.
As you know the Windows 10 21H2 OS is released by Microsoft. The Windows 10 21H2 update, also known as November 2021 update is the latest Windows 10 OS that you can deploy.
The main reason why you should use SCCM to deploy Windows 10 21H2 OS is it makes your task easier. Whether it’s a new laptop or existing one, you can wipe existing OS and freshly deploy Windows 10 21H2.
In short, we will create a new task sequence, define the steps for deployment, add the drivers, apply customization and deploy the Windows 10 21H2 task sequence.
Table of Contents
Upgrading to Windows 10 21H2
There are many ways to upgrade to Windows 10 21H2. For example, home users can upgrade to Windows 10 21H2 directly via Windows update. Feature update to Windows 10, version 21H2 upgrades Windows 10 to version 21H2 with a single reboot.
On devices running Windows 10, versions 2004, 20H2, and Windows 10 21H1, you can install Windows 10, version 21H2 update using an enablement package. You can refer to the following guide to upgrade to Windows 10 21H2 using SCCM or ConfigMgr.
You can also use SCCM servicing plans to upgrade to Windows 10 21H2. Servicing plans are recommended for deploying the upgrades whereas you can use task sequence for bare-metal deployment.
Before you Deploy Windows 10 21H2 using ConfigMgr
When new laptops arrive at your workplace, you should avoid installing an older version of Windows 10 when there is a newer version available. If you do that, you have more computers that you need to upgrade in the future. Instead, deploy Windows 10 21H2 using SCCM task sequence.
You should not deploy Windows 10 21H2 using SCCM without proper testing. Before you deploy Windows 10 21H2 using ConfigMgr, you must test the deployment and have a proper plan for the roll-out. Be it a bare-metal deployment or an in-place upgrade to 21H2, a proper planning is required. Deploy it to a limited group and test all your business applications before broad deployment.
Windows ADK requirement for Windows 10 21H2
Big Question – What version of Windows ADK should I use to deploy Windows 10 21H2 using SCCM? The ADK for Windows 10, version 2004 should be used for deploying Windows 10, version 21H2 with SCCM.
Refer the following post to find out all the Windows 10 ADK versions, it includes the ADK download links as well. Moreover, there is no new ADK version released separately for Windows 10 21H2.
Windows 11 ADK version is out, and you can use it along with ConfigMgr to deploy Windows 10 21H2. If you have an older version of ADK installed, you can use the step-by-step guide to update Windows ADK on SCCM Server.
Supported SCCM version for Windows 10 21H2
Before you deploy Windows 10 21H2 using SCCM task sequence, ensure you are using ConfigMgr 2107 and above in your setup.
The following table by Microsoft lists the versions of Windows 10 that you can use as a client with different versions of Configuration Manager.
Windows 10 21H2 and Enterprise LTSC 2021 is supported by ConfigMgr 2107. If you are still running ConfigMgr 2103, you can use the following guide to upgrade to SCCM 2107.
Prerequisites for Windows 10 21H2 Deployment using SCCM
Before you plan to deploy Windows 10 21H2 using SCCM, here are some of the prerequisites.
- You require Configuration Manager version 2107 to deploy and manage Windows 10 21H2.
- Latest version of Windows 10 ADK should be installed.
- Download the Windows 10 21H2 ISO media from VLSC or Visual Studio Subscriptions.
- You must have installed and configured the PXE on the distribution point.
- Add required drivers to the SCCM boot image and ensure they are distributed to all distribution points.
Download Windows 10 21H2 ISO
Before you deploy Windows 10 21H2 using ConfigMgr to new laptops or VM’s, let’s download the Windows 10 21H2 ISO file. To download Windows 10 21H2, you can download it from Microsoft VLSC or Visual Studio.
Normally, enterprise edition of Windows 10 are deployed to new laptop in organizations. So, I am going to download Windows 10 21H2 (business editions). Click the Download button and save the Windows 10 21H2 ISO file on SCCM server.
This multi-edition Business media includes the following editions:
- Windows 10 Pro
- Windows 10 Pro N
- Windows 10 Pro for Workstations
- Windows 10 Pro N for Workstations
- Windows 10 Pro Education
- Windows 10 Pro Education N
- Windows 10 Education
- Windows 10 Education N
- Windows 10 Enterprise
- Windows 10 Enterprise N
You have to extract the Windows 10 21H2 files to a folder before you could use it for to deploy. You can either mount it and copy the files to a folder or use a software to extract it. I have placed the OS setup files inside a folder called W1021H2.
Import Windows 10 21H2 OS in SCCM
Use the following steps to import Windows 21H2 operating system image in SCCM.
- Launch the Configuration Manager console.
- Navigate to Software Library\Overview\Operating Systems\Operating System Images.
- Right click Operating System Images and click Add Operating System Image.
Now you see Add operating system image wizard. On the Data Source window, click Browse and specify the path of Windows 10 21H2 install.wim file.
Select the checkbox Extract a specific image index from the specified WIM file. Next to Image Index, select the Windows 10 edition that you want to extract. For example, I am going to extract Windows 10 21H2 enterprise edition from the WIM file.
Click Next.
On the General window, specify the name of the OS image as Windows 10 21H2 Enterprise. Click Next.
Verify the settings on Summary page and on Completion window, click Close.
Distribute Windows 10 21H2 content to Distribution Points
When you import any content into SCCM, you must distribute the content to the distribution points.
In the SCCM console, go to Software Library > Overview > Operating Systems > Operating System Images. Right click Windows 10 21H2 enterprise image and click Distribute content.
On the Content Destination window, click Add button and select the distribution points to send Windows 10 21H2 content. Click Next.
On the Completion window, click Close.
When you distribute the content to distribution points, you must ensure it is successful. Select the Windows 10 21H2 operating system image and look for Content Status. If it’s green, it means the content is distributed successfully.
Create Windows 10 21H2 SCCM Task Sequence
You can create a new SCCM task sequence for Windows 10 21H2 using the following steps.
- In the ConfigMgr console, go to Software Library\Overview\Operating Systems\Task Sequences.
- Right click Task Sequences and click Create Task Sequence.
Select Install an existing image package. Click Next.
Specify the task sequence name as Deploy Windows 10 21H2 Enterprise, and you may also provide task sequence description. Click Browse and select a 64-bit boot image. Click Next.
In this step, you specify the Windows 10 21H2 image package, product key. In addition, you may specify a local administrator password instead of a randomly generated one. Click Next.
On the Configure Network window, select Join a domain. Click Browse and specify the destination OU. Next, select an account that permissions to join the machine to the domain. Click Next.
You may specify additional client installation properties. Click Next.
Uncheck all the options as we are not going to use state migration. Click Next.
You don’t have to add any software updates here as we can manage and deploy the updates using ADR’s. So select Do not install any software updates and click Next.
On the Install Applications window, if you wish to add applications to the deployment you can click the yellow star icon and select the Applications. Otherwise, you can just skip it and later deploy the applications. Click Next.
Finally, on the Completion window, click Close. Our task sequence in ready and in the next step we will deploy Windows 10 21H2 using SCCM or ConfigMgr.
Add Drivers for Windows 10 21H2 in Task Sequence
Along with Windows 10 21H2 deployment, deploying the latest Windows drivers is also important. Otherwise, you will have just the Windows 10 21H2 with no drivers installed. There are multiple ways to deploy drivers and manage driver updates in SCCM. Each organization has their own way to deploy drivers for laptops and computers and driver updates.
If I have to recommend a commonly used method to deploy drivers, that is via the task sequence again. You must first import the drivers into SCCM and then edit the task sequence and add Drivers > Apply Driver Package step. You can use the WMI to detect the laptop model and apply the right drivers.
After adding the drivers, you may add more steps to the task sequence and customize it based on your requirements. Once the task sequence is ready, go to the next step.
Deploy Windows 10 21H2 using SCCM (ConfigMgr)
Perform the below steps to deploy Windows 10 21H2 using SCCM task sequence.
- Launch the ConfigMgr console.
- Go to Software Library\Overview\Operating Systems\Task Sequences.
- Right click Deploy Windows 10 21H2 task sequence and select Deploy.
On the General page, specify the target collection to which you want to deploy Windows 10 21H2 task sequence. Click Next.
Select the task sequence purpose as Available and choose the TS deployment available to only media and PXE. Click Next.
If you wish to schedule the deployment, you may do it here. Otherwise, click Next.
Specify the user experience settings for the deployment. Click Next.
On the Completion window, click Close. This closes the deploy software wizard.
Test Windows 10 21H2 Task Sequence Deployment
In the above step we deployed the Windows 10 21H2 ConfigMgr task sequence to device collection. we will now test the Windows 10 21H2 task sequence deployment. You can either connect a laptop to the network or create a new VM to test Windows 10 21H2 deployment.
In my lab I am going to create a new Virtual Machine with no operating system. We will test the Windows 10 21H2 deployment on this VM. I have enabled ConfigMgr PXE responder service and the boot images are distributed to DP’s. Power on the VM and press F12 for network boot.
The VM downloads the boot image from the distribution point.
On Welcome to the task sequence wizard, enter the password if you have configured or just click Next.
On Select a task sequence to run window, select Deploy Windows 10 21H2 SCCM task sequence and click Next.
Once the task sequence completes it’s execution, check the Windows 10 version. Login to the computer with your domain credentials. Click Start > type About your PC and launch it. Under Windows specifications, we see the edition as Windows 10 Enterprise and version as 21H2. You will see Windows 10 Version 21H2 (OS Build 19044.1348) is installed successfully.
This completes the steps to deploy Windows 10 21H2 using SCCM or ConfigMgr. You can now create SCCM Windows 10 21H2 device collection to group all Windows 10 21H2 devices.
Troubleshooting Windows 10 21H2 Task Sequence Failures
When you deploy Windows 10 21H2 using SCCM, the task sequence could fail due to several reasons. Remember that you must always review smsts.log file for troubleshooting operating system deployment issues.
The location of smsts.log file changes during the OSD. So ensure you pick the smsts.log file from the correct location in case the OSD fails.
Still Need Help?
If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.
Deploying Windows 10 with System Center Configuration Manager (SCCM)
There are a number of different ways Configuration Manager can be used to Deploy Windows 10.
- In-place Upgrade: Windows 7, 8, 8.1, or 10 to the latest version. The upgrade process retains the applications, settings, and user data on the computer.
- Refresh an existing computer (Wipe and Transfer Settings): Wipe an existing computer and installs a new operating system on the computer. You can migrate settings and user data after the operating system is installed.
- Bare Metal Install on a New Computer: Install Windows on a new computer.
- Replace an existing computer and transfer settings: Install Windows on a new computer. Optionally, you can migrate settings and user data from the old computer to the new computer.
In-place Upgrade
This method is used to upgrade Windows 7, 8, 8.1 to 10. You can also do build-to-build upgrades of Windows 10 such as 1607 to 1709. Additionally, starting in Configuration Manager 1802, the Windows 10 in-place upgrade task sequence supports deployment to internet-based clients managed through the cloud management gateway (CMG). This method is the most robust and has no external dependencies, such as the Windows ADK
With the in-place upgrade you:
- CANNOT change domain membership
- CANNOT change disk partitions
- CANNOT change architecture (x86 to x64)
Preparing the Upgrade Package
-
Add operating system upgrade packages to Configuration Manager (the extracted ISO path)
- Distribute operating system images to a distribution point
-
Apply software updates to an operating system upgrade package
Create an In-place Upgrade Task Sequence
- Create a New Task Sequence -> Upgrade an operating system from upgrade package
- Select he Upgrade Package from the previous step
- Set Product key, Include Updates and Install Applications preferences
- Complete the wizard
-
Add steps to get the previous OS in an upgrade state, such as
- Battery checks
- Network/wired connection checks
- Remove incompatible applications
- Remove incompatible drivers
- Remove/suspend third-party antivirus.
Pre-Cache Content on Client
You can optionally pre-deploy the Upgrade Package to clients so that they do not have to download it if they click to install it in Software Center. This is called pre-cache of the content.
Download Package Content Step
You can also use the Add Download Package Content step to customize such things as detect the client architecture, hardware type for each driver package.
Deploy the Task Sequence to Computers
There are two ways in which you can deploy this task sequence to computers
- Use Software Center to deploy over the network
- Use USB drive to deploy without using the network
- Cloud Management Gateway (1802 and above)
Deploy with Software Center
- Task Sequence -> Deploy
- Set Deployment Settings, Scheduling, User Experience, Distribution Points
- With 1802 you can now also choose to save this deployment as a template.
Deploy with USB Drive
- Select your task sequence and choose Create Task Sequence Media
Deploy with Cloud Management Gateway (CMG)
Starting with Configuration Manager 1802, you can use a CMG to deploy a task sequence.
- Ensure all of the content referenced by the in-place upgrade task sequence is distributed to a cloud distribution point.
-
When deploying the task sequence, check the additional options:
- Allow task sequence to run for client on the Internet, on the User Experience tab of the deployment.
- Download all content locally before starting task sequence, on the Distribution Points tab of the deployment.
- Other options such as Download content locally when needed by the running task sequence do not work in this scenario.
- Pre-download content for this task sequence, on the General tab of the deployment
Refresh an Existing Computer (Wipe and Transfer Settings)
Let’s look at how we can partition and format (wipe) an existing computer and install a new operating system onto it and transfer the settings as well. We need to install a state migration point to store and restore user settings on the new operating system after it is installed. This is called a Refresh
Prepare for a Refresh Scenario
There are several infrastructure requirements that must be in place before we can deploy operating systems with Configuration Manager.
Dependencies External to Configuration Manager
- Windows ADK for Windows 10
- User State Migration Tool (USMT) (transfer user settings)
- WinPE images (PXE boot media)
- Windows Server Update Services (WSUS) (for updates during deployment)
-
Windows Deployment Services (WDS) (PXE boot environment)
- Also DHCP enabled
- Internet Information Services (IIS) on the site system server
- Device drivers ready
Configuration Manger Dependences
- OS Image
- Driver catalog (import the device driver, enable it, and make it available on a distribution point)
- Management point
- PXE-enabled distribution point
- Install a State Migration Point and configure it
Prepare WinPE Boot Image
- Two default images are provided by Configuration Manager in \\servername>\SMS_<sitecode>\osd\boot\<x64> or <i386>
- Add Boot Image (Operating Systems -> Boot Images)
- Distribute Boot Images to Distribution Points
- Boot Image Properties -> Data Source tab, select Deploy this boot image from the PXE-enabled distribution point
Prepare an Operating System Image
- Decide to use the default install.wim or capture a reference computer and make your own .wim file.
- Add the Operating System Image to Configuration Manager (Operating Systems -> Add Operating System Image)
- Distribute the Operating System to a Distribution Point
- Schedule Software Updates to the Operating System Image
Create a Task Sequence
- Create a New Task Sequence -> Install an existing image package
- Choose setting such as Image package (and image), partitions, product key
- Choose to Join A Domain
- Choose to install the Configuration Manager Client
-
Choose Under State Migration
- Capture user settings: capture the user state.
- Capture network settings: Captures network settings
- Capture Microsoft Windows settings: Capture the computer name, registered user and organization name, and the time zone settings.
Deploy the Task Sequence
You have a few different options to choose when deploying the task sequence.
- Use PXE to deploy over the network
- Use Multicast to deploy over the network
- Use Software Center to deploy over the network
-
Create an image for an OEM in factory or a local depot
- Create Task Sequence Media
- Use USB Drive to deploy Windows over the network
Bare Metal Install on a New Computer
Let’s look at how we can partition and format (wipe) a new computer and install a new operating system onto it.
Prepare for a Bare Metal Scenario
There are several infrastructure requirements that must be in place before we can deploy operating systems with Configuration Manager.
Dependencies External to Configuration Manager
- Windows ADK for Windows 10
- User State Migration Tool (USMT) (transfer user settings)
- WinPE images (PXE boot media)
- Windows Server Update Services (WSUS) (for updates during deployment)
-
Windows Deployment Services (WDS) (PXE boot environment)
- Also DHCP enabled
- Internet Information Services (IIS) on the site system server
- Device drivers ready
Configuration Manger Dependences
- OS Image
- Driver catalog (import the device driver, enable it, and make it available on a distribution point)
- Management point
- PXE-enabled distribution point
Everything else here is the same as a Refresh. Follow the directions above, skipping the sections where we would use the State Migration Point.
Replace an existing computer and transfer settings
Let’s look at how we can partition and format (wipe) a destination computer and install a new operating system onto it and transfer the settings as well from a source computer. We need to install a state migration point to store and restore user settings on the new operating system after it is installed. This is called a Refresh
Prepare for a Replace Scenario
There are several infrastructure requirements that must be in place before we can deploy operating systems with Configuration Manager.
Dependencies External to Configuration Manager
- Windows ADK for Windows 10
- User State Migration Tool (USMT) (transfer user settings)
- WinPE images (PXE boot media)
- Windows Server Update Services (WSUS) (for updates during deployment)
-
Windows Deployment Services (WDS) (PXE boot environment)
- Also DHCP enabled
- Internet Information Services (IIS) on the site system server
- Device drivers ready
Configuration Manger Dependences
- OS Image
- Driver catalog (import the device driver, enable it, and make it available on a distribution point)
- Management point
- PXE-enabled distribution point
- Install a State Migration Point and configure it
Configure State Migration Point
The scenario for a replace is similar to a restore. The exception is we need to configure the State Migration Point with settings to assure we have a spot to store our migration data that is not on the computer.
We must specify:
- The drive on the server to store the user state migration data.
- The maximum number of clients that can store data on the state migration point.
- The minimum free space for the state migration point to store user state data.
- The deletion policy for the role. Either specify that the user state data is deleted immediately after it is restored on a computer, or after a specific number of days after the user data is restored on a computer.
- Whether the state migration point responds only to requests to restore user state data. When you enable this option, you cannot use the state migration point to store user state data.
This post will cover all the steps to deploy Windows 11 23H2 using SCCM. You will also get to know more details, If you are planning to deploy and manage Windows 11 version 23H2 using SCCM, including downloading Windows 11 23H2 ISO, importing Windows 11 into SCCM, and deploying from task sequence.
The new Windows 11 Version 23H2, also known as October 2023 Update, is available for all users as a free update. This update introduces a new bunch of features to the user regarding security, visibility, and many more.
The bare metal deployment method helps you when you have a blank machine you need to deploy or an existing device you want to wipe and redeploy without preserving any existing data. In simple steps, you can install the latest Windows version on a new computer (bare metal) using sccm.
To install an operating system on a new computer. You can choose from many different deployment methods, such as PXE, OEM, or stand-alone media. The fresh installation of the OS doesn’t include any settings or user data migration. The Windows 11 23H2 deployment process for the new machine scenario is as follows:
- Start the setup from boot media (CD, USB, ISO, or PXE).
- Wipe the hard disk clean and create the new volume.
- Install the operating system image.
- Apply device drivers by detecting device manufacturers.
- Install applications.
- Apply Customization and additional settings if needed.
- After taking these steps, the computer is ready for use.
Windows 11 23H2 Deployment Prerequisites
Before you deploy Windows 11 version 23H2, You need to ensure you are running the supported SCCM version, the latest version of Configuration Manager 2309 production release. The support matrix is expected to be updated soon for Windows 11 23H2.
YouTube Video – Easiest Windows 11 23H2 Upgrade Process – YouTube
Windows 11 Hardware Requirements
The devices should meet the Windows 11 minimum requirements for a Windows 11 upgrade. Using the PC Health Check app, you can check for compatibility to see if your current PC meets the minimum system requirements to run Windows 11. You have to download the Windows 11 PC Health Check App from the Microsoft site.
- Make sure that you are running a supported version of the Windows ADK. The ADK for Windows 10, version 2004, and Windows 11 (Version 21H2, 22H2 or 23H2) will work with Windows 11, 23H2.
- Add the required Network and Storage drivers to the boot image.
- Configured the boot image to deploy from a PXE-enabled distribution point.
Download Windows 11 23H2 ISO
You can download Windows 11 23H2 ISO from MSDN or VLSC (Volume Licensing Service Center). Here you will find Windows 11 (business editions) version 23H2. Select the architecture and language. Click on Download.
How To Download Windows 23H2 ISO
Mount and Extract Windows 11 23H2 ISO
Before importing the Windows 11 23H2 Operating System into SCCM, mount and extract or copy Windows 11 23H2 ISO contents to a folder. Create a shared folder, and Mount the ISO using File Explorer or any other available options.
Copy the downloaded ISO to the SCCM site server, Double-click an ISO file to mount it, or Right-click an ISO file in File Explorer. Select the Mount option.
You will notice that Windows 11 23H2 ISO will create a disc drive that you can use to access content. Select all contents and copy them to a shared source folder in SCCM Server. The content-copying process might take some time. Wait to complete the process.
Note! You can locate the default OS image in the Windows source folder \Sources\install.wim. Grab a file off of this ISO and Copy it to the shared directory to make use of it.
Import Windows 11 23H2 Operating System Image
The Windows 11 operating system image contains the files necessary to install the operating system on the destination computer. Use the following to prepare the operating system image
- In Configuration Manager Console, Go to Software Library > Operating Systems > Operating System Images.
- Right click on Operating Systems Images and click on Add Operating System Image.
In Data Source, click Browse and specify the network shared path to the install.wim from the Windows 11 23H2 Source directory where you extracted the source of an ISO file. Accept the licensing terms, and select the Windows edition you would like to install. Here, I selected “Windows 11 Enterprise” from the drop-down list.
Note! Extract a specific image index from the specified WIM file – You can now automatically import a single Image index rather than all image indexes in the file. Using this option results in a smaller image file.
On the Pre-cache settings page, select Architecture as x64 and Language English (United States), and click Next. You can leave this option as default.
It is best to provide all the information for OS Image. On the General page, Enter the Name, Version, and Comment for the Task Sequence. Click Next.
Once you have done, Review the provided information, and click Next to complete the wizard.
Wait for a moment while exporting is in progress. After successful completion, click Close to exit the wizard. The Windows 11 23H2 Operating System Image now appears in the Operating System Images node of the SCCM console.
Distribute Windows 11 23H2 Operating System Image
After the creation of the OS Image Package, it will appear in the Operating System Images Node. To begin with, the distribution right-click on the Windows 11 Image and click on Distribute Content.
Here you have selected Windows 11 Image for distribution, Review the selected content for distribution. Click Next.
Add the Distribution Point to distribute the content, Review the selected distribution points, groups. Click Next.
On the Summary page, review the settings. Click Next. Click Close to complete the Distribute Content wizard.
You can monitor the content status. If it’s showing a yellow colour, that means distribution is in progress. If the content distribution were successful, it would appear with Green color, as shown.
- Create Windows 11 23H2 SCCM Device Collection
- SCCM Collection Best Practices while Creating a Dynamic Collection
Create Task Sequence to Deploy Windows 11 23H2
In the Configuration Manager console, Go to the Software Library workspace, expand Operating Systems, right-click Task Sequences, and select Create Task Sequence.
Select Install an existing image package. This option creates a task sequence that installs the OS, migrates user settings, applies software updates, installs applications, and then selects Next.
On the Task Sequence Information page, specify the following settings and click Next.
- Task sequence name: Specify a name that identifies the task sequence.
- Description: Optionally specify a description
- On the Boot Image, Click Browse and select the available boot image package. Select Run as high performance power plan check box.
On the Install Windows page, specify the following settings and click Next.
Image package: Click on Browse to select the image. Select Partition and format the target computer installing the operating system.
- Unchecked Configure task sequence for use with BitLocker – Since we don’t want to add the Bitlocker step to the task sequence,
- Product key: you can specify the Windows product key for the OS to install.
Specify how to handle the administrator account for the new OS. Enable the account and specify the local administrator password – Windows uses the same password for the local administrator account on all computers where the task sequence deploys the OS image.
On the Configure Network page, specify the following settings to join the device to the workgroup or domain and click Next.
Join a workgroup: Add the destination computer to a workgroup.
Join a domain: Add the destination computer to a domain. In Domain, click Browse to specify the name of the domain. You can also specify an organizational unit (OU) in the Domain OU field. This setting is optional—Account: The user name and password for the account have permission to join the specified domain.
On the Install Configuration Manager page, specify the Configuration Manager client package is selected automatically. If required, you can specify additional SCCM client installation properties. Click Next.
On the State Migration page, you can leave it to default or Uncheck all the options if you do not want to capture settings.
These steps are condition-based in a task sequence that is not going to run automatically. Click Next.
On the Include Updates page, you can specify whether to install the required software updates or all software updates. Here I’m not installing any software updates, leaving the option default and Clicking Next.
On the Install Applications page, specify the applications to install, or later you can add in task sequence steps. Click Next.
Review the task sequence details, Click Next. Here you can see the message, Create Task Sequence Wizard completed successfully. Click Close to complete the wizard.
Edit Windows 11 23H2 Task Sequence
Let’s follow the steps to modify an existing Windows 11 23H2 task sequence in the Configuration Manager console.
Under Software Library – Operating Systems – Task Sequences. Right-click on the task sequence and select Edit.
Edit the Windows 11 23H2 Task Sequence to add or remove settings – The Task Sequence uses these phases to determine which tasks must be completed. You can use the task sequence editor to
- Add or remove steps and groups from the task sequence
- Change the order of the steps of the task sequence
- Set step options like whether the task sequence continues when an error occurs
- Add conditions to the steps and groups of a task sequence
Add Drivers
Let’s check the steps to Add Apply Driver Package Step to SCCM Task Sequence. Review drivers and applications that will be installed with the task sequence.
Before you deploy the task sequence, make sure the drivers are compatible. To Import Drivers, Create Driver packages, and Process to Integrate Driver package into Task Sequence.
You can refer to the following post to modify an existing task sequence
- Add Install Application Step to SCCM Task Sequence
- Add Run PowerShell Script Step to SCCM Task Sequence
- Add Run Command Line Step to SCCM Task Sequence
Important⚠️Review other settings added in Task Sequence. Make sure to apply all changes. Click Apply and OK, and close the task sequence editor.
Use the following procedure to deploy a task sequence to the computers in a collection.
In the Task Sequence list, select the task sequence you have created, Right-click, and select Deploy.
On the General, click Browse to select the device collection where you wish to perform the deployment.
Deploy to All Unknown Computers – Computers that are not managed by Configuration Manager or a computer not imported into Configuration Manager.
On the Deployment Settings, select the Purpose of the deployment.
Available – Available deployments require that the user is present at the destination computer. A user must press the F12 key to continue the PXE boot process. If a user isn’t present to press F12, the computer boots into the current OS, or from the next available boot device.
Required – Required deployments use PXE without any user intervention.
To use a PXE-initiated OS deployment, For the Make available to the following setting, select one of the following options –
Configuration Manager clients, media, and PXE
Only media and PXE
Only media and PXE (hidden)Note – Use the Only media and PXE (hidden) setting for automated task sequence deployments. To have the computer automatically boot to the deployment without user interaction, select Allow unattended operating system deployment and set the SMSTSPreferredAdvertID variable as part of the media.
On the Scheduling tab, you can specify the schedule for this deployment. Click Next.
On the User Experience tab, leave the default selected options. Click Next.
On the Alerts page, leave it as default. Click Next. Next, on the Distribution Points page, you can specify how clients interact with the DPs to retrieve content from reference packages. Click Next.
To understand the available options in the Distribution Points tab during task sequence deployment – SCCM Task Sequence Available Deployment Options in Distribution Points Tab | ConfigMgr
Review the selected settings and click Next. The deployment was targeted successfully to the collection. Click Close to exit the wizard.
- Easy Steps to Copy SCCM Task Sequence for Deployment
- How to Disable SCCM Task Sequence Deployment
Results – Windows 11 23H2 Deployment
Different hardware models have different experiences for PXE. To boot to the network – UEFI-based devices typically use the key, and BIOS-based devices use the key.
After the device successfully boots via PXE, the task sequence wizard appears. If you password-protect the media, the user has to enter the password on this welcome page. Click Next.
Select a task sequence to run: If you deploy more than one task sequence to the device, you see this page to select a task sequence.
Make sure to use a name and description for your task sequence that users can understand. Complete the Task Sequence Wizard by selecting the deployed task sequence.
Click Next. The task sequence begins when the policy for the task sequence is downloaded and the content location is verified.
Once you complete the Wizard, the deployment of the new operating system begins. When the task sequence runs, it displays the Installation progress window. Check more about How to Improve SCCM Task Sequence Progress Bar End User Experience.
Please wait to complete the task sequence deployment. Sign in to the device with your domain or local credentials. Click Start, Type Winver, and Press Enter. You will see Windows 11 version 23H2 (OS Build 22631) was installed successfully.
Let’s quickly look at the Windows 11 build numbers and version numbers. The Windows 11 version build number starts at 22000, Windows 11 22H2 version is 10.0.22621 and Windows 11 23H2 starts with 10.0.22631.
Troubleshooting – Deploy Windows 11 23H2 using SCCM
The SMSTS.log is one of the important log files that will help you troubleshoot installation issues related to Operating System Deployment (OSD) and fix those.
Learn how to read SMSTS.log effectively for troubleshooting SCCM OSD Task Sequence. You can also check SCCM OSD SMSTS Log File Reading Tips with the built-in log reader tool CMTrace.
- OSD Known Issues Troubleshooting Guide | SCCM | ConfigMgr
- ConfigMgr OSD Troubleshooting Known Issues Guide Part 2 | SCCM
We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.
Author
About Author – Jitesh, Microsoft MVP, has over six years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus is Windows 10/11 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.
Created On
Last Updated On
If your organization uses SCCM to manage Windows machines, you can use the SCCM tools to create and deploy SCCM WinPE (Prestaged) media to Windows 10 on a Mac with Winclone 8. This process is different from deploying Windows on standard PC hardware, since the Mac boots up differently from standard PCs. This process works with all Macs that support EFI booting (including new Macs with the T2 coprocessor).
Overview
After completing the process for deploying Windows 10 to Macs with SCCM, you will have a Winclone package that you can deploy to your Macs. The Winclone package will create a Boot Camp partition as needed and deploy WinPE to that partition. When the Mac is rebooted to the WinPE environment, you will then select the a Task Sequence to install Windows 10 and any associate software and configurations, just as you would on a task sequence run on a standard PC. The Mac will then install Windows and the other items defined in the Task Sequence. Windows will be installed on the same partition that WinPE was installed on. Windows 10 will then be full-installed and available for use on the Mac.
The Winclone package is created from a Winclone image imported from the Prestaged WIM that was exported from SCCM. A Prestage media is required, since the WinPE environment is installed on the internal disk (fixed disk); other methods (such as Stand-alone Media, Bootable Media, or PXE boot) do not work. Prestaged media contains a cached version of the resources required, but any updates of these resources will be downloaded directly from SCCM if they are different from the Prestaged media.
Configuration
The steps below are for an example setup of SCCM; your environment may be different. Adjust the step accordingly to match your environment.
Software Used
- Windows Server 2109
- SCCM 2016
- SQL Server 2016
- Windows 10 (1909)
- Winclone 8.0.1
Create Prestaged Media
To create the Prestaged Media as the basis for the Winclone package, you need to have a version of Windows 10 to deploy, drivers to inject, and a Task Sequence to deploy Windows.
- If you do not already have Windows in SCCM to deploy, download Windows 10 from Microsoft. Import the install.wim from the Sources folder in the ISO to SCCM under Software Library->Overview->Operating Systems->Operating System Images:
- Import the drivers downloaded from Boot Camp Assistant in macOS to Software Library->Overview->Operating Systems->Drivers
Create a New Task Sequence under Software Library->Overview->Operating Systems->Task Sequences:
Create a custom task sequence and add in the following steps:
Note: there is no step for partitioning the disk. In the Apply Operating System step, select the Next Formatted Partition:
After the task sequence is complete, deploy the task sequence and distribute the resources.
Next, create the Task Sequence Media:
Select Prestaged Media and do not select the “Allow unattended operating system deployment” checkbox:
Select Dynamic media:
Provide the media properties and share to save the WIM:
Specify Security Settings as appropriate:
Select the task sequence you imported:
Select a distribution point for the boot image:
Select the version of Windows and the distribution point:
Add in any applications:
Add in the Configuration Manager Client Package:
Add in the Boot Camp drivers:
Select a Distribution Point for the media:
Add in any variables:
Confirm the settings:
Create the Media:
Creating a Winclone Package
Once the Prestaged media has been created, copy the WIM to a Mac with Winclone Pro 8.0.1 or later installed. In Winclone, select the option from the Tools menu to “Create Winclone Image from WIM…”:
Select the WIM Prestaged media that was exported from SCCM. Make sure to click the “Make WinPE Bootable on Restore” checkbox:
Save the Winclone Image on the Mac:
In Winclone Pro, create a Winclone Package to deploy the Prestaged Media Winclone Image. Only the options on the first tab (“Partitioning Options”) apply.
Select the Prestaged Winclone image you created and select the size of the Boot Camp partition you want to create (or use an existing partition if a Boot Camp partition already exists):
Click Create Package, give the package a name, and Save:
Once the package has been created, it can now be deployed.
Deploying
Copy the package to a Mac that needs Windows 10 installed via SCCM and install the package. The package will create the Boot Camp partition and install WinPE. Boot into Windows by rebooting while holding the option key and selecting Windows; you may also select Windows as the Startup Disk from System Preferences.
The Mac will boot into the WinPE environment and allow you to select the Boot Camp task sequence. Once the Task Sequence is run, Windows 10 and the other steps specified in the Task Sequence will be installed on the single Boot Camp partition, overwriting the WinPE environment.
If a new Windows image needs to be installed, the same package can be installed; any changes to the Task Sequence or media in SCCM will be used instead of the resources on the Prestaged media. If resources change significantly, a new Prestaged media can be created to speed deployment, since the resources will be precached for quick deployment.