О LENOVO
+
О LENOVO
-
Наша компания
-
Новости
-
Контакт
-
Соответствие продукта
-
Работа в Lenovo
-
Lenovo Открытый Код
КУПИТЬ
+
КУПИТЬ
-
Где купить
-
Рекомендованные магазины
-
Стать партнером
Поддержка
+
Поддержка
-
Драйверы и Программное обеспечение
-
Инструкция
-
Инструкция
-
Поиск гарантии
-
Свяжитесь с нами
-
Поддержка хранилища
РЕСУРСЫ
+
РЕСУРСЫ
-
Тренинги
-
Спецификации продуктов ((PSREF)
-
Доступность продукта
-
Информация об окружающей среде
©
Lenovo.
|
|
|
|
To upgrade Windows 10 1903 to version 1909, you can deploy Windows 10 1909 enablement package using SCCM.
According to Microsoft Windows 10 versions 1903 and 1909 share a common core operating system with an identical set of system files.
The Windows 10 1909 enablement package allows you to update from version 1903 to version 1909 with a single restart. In other words, you get a reduced update downtime.
If you are using SCCM (Configuration Manager) you can deploy Windows 10 1909 enablement package easily. When you push this update, you can upgrade all your machines running Windows 10 1903 to 1909.
For version 1903 devices that receive updates directly from Windows Update, the devices will automatically get the enablement package. This will install the feature update to Windows 10, version 1909.
But what about devices running Windows 10 1809 and earlier builds ?. In this case the feature update enablement package cannot be manually installed. That’s because it is bundled and automatically included with the feature update to Windows 10, version 1909. Most of all the installation time is not reduced in this scenario.
You may either download 1909 feature update or use Windows 10 servicing plans to upgrade 1809 or earlier builds to Windows 10 1909.
Prerequisites
You must have the following prerequisites installed before deploying 1909 enablement package.
- Servicing stack update for Windows 10 version 1903 that is dated September 24, 2019 or a later servicing stack update.
- Cumulative Update for Windows 10 version 1903 that is dated October 8, 2019 or a later cumulative update.
- Finally configure software updates to deploy Windows 10 feature updates if you haven’t done that.
Download Windows 10 1909 Enablement Package
So now lets look at downloading Windows 10 1909 enablement package using SCCM. First of all ensure you have synchronized the updates in Configuration Manager.
You can either download the feature first and deploy or directly deploy the feature update. I prefer to download it first, let the content get distributed to distribution points and then deploy it.
Go to Software Library > Overview > Windows 10 Servicing > All Windows 10 Updates. Look for the update “Feature Update to Windows 10 Version 1909 2019-11 via Enablement Package“. You can also search the updates with article ID 4517245.
Since my lab VM’s are running 64 bit OS, I will select the 64 bit package. Right click the 1909 Enablement Package and click Download.
On the Deployment Package page, select Create a new deployment package. Specify name and package source. Click Next.
On the Distribution Points window, click Add button and select Distribution Points or distribution point groups. Click Next.
No changes required on distribution settings window, so click Next.
Specify the software updates source location. In our case we will download the software updates from the internet. Click Next.
Click Next.
On the Completion page, click Close.
Go to Software Updates > Deployment Packages. Select the 1909 feature update and at the bottom, check the distribution point status.
Deploy Windows 10 1909 Enablement Package using SCCM
Navigate to Software Library > Overview > Windows 10 Servicing > All Windows 10 Updates. Look for the update “Feature Update to Windows 10 Version 1909 2019-11 via Enablement Package“.
Right click the Windows 10 1909 Enablement Package and click Deploy.
On the General window, specify the deployment name. Next, select the device collection to which you want to target the update deployment. Click Next.
On the Deployment Settings window, select the type of deployment as Available.
First select the schedule evaluation to client local time. Specify the software available time. In this example I have selected software available time as As soon as possible. Click Next.
Select the desired user notifications and click Next.
Specify the download settings and click Next.
Click Close.
Alright so now if you open the software center on the client machine, you will find the 1909 update. The users can install it based on their convenience. In my next post I will show you how to schedule this update and set a proper deadline to install it.
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.
In this article, we will explain how the System Center Configuration Manager Console tool is installed on your Windows 10 PC. In some cases, you can easily operate on the SCCM Console screen from your Windows 10 operating system computer without the need to connect to the SCCM server. Now we can start the installation process. We need to go to our client computer and copy the SCCM Console Setup file. For this, we right-click on the ”Windows” button of our Windows 10 computer and click on the ”Run“ option.
We need to connect to the “c$” of our server. We can connect as ”\\SCCM\c$”. Continue by clicking the “OK” button.
When we connect to the c$ screen of our SCCM Server, we can go to the Path we have specified below and copy the “SCCM Console Setup” file to our desktop.
When we open the folder that we have moved to the desktop, we right-click the “ConsoleSetup” program and click the “Run as Administrator” option.
On the “Microsoft Endpoint Configuration Manager” page, click the “Next” button.
On the “Site Server” page, we write the “FQDN” of the server in the box to which “Site Console” screen you want to connect to. Then we click the “Next” button. Since there is only one site in our lab environment, we continue by typing the name of our server.
On the “Installation Folder” page, we select where the program will be installed. We leave it the same. Then we click the “Next” button.
On the “Ready to Install” page, we start the installation process by clicking the “Install” button.
On the “Please Wait” page, we wait a bit until the installation is finished.
On the last page, we will complete the installation process by clicking the “Finish” button.
When you click on the start menu, you will see that the SCCM Console tool is installed.
When you type the name of your server by selecting the “Connect to site” option, the automatic name filling process will be performed. After the name filling process; By selecting the “Connect” option, the connection to the Console screen will be successfully established. In addition, the warning on the screen shows that the user we have become “Logon” does not have SCCM Console login authority.
For this; In order to give SCCM Console login authorization to the relevant user, we can authorize the relevant user or our own user by clicking the “Security” folder in the “Administration” section of our SCCM server and selecting the “Administrative Users” option. After the authorization is completed, we see that we have successfully accessed the SCCM Console screen.
We have successfully accessed the SCCM Console screen.
