AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() In the portal, find Windows 11 (business editions).To get the ISO file, you can either download it from MSDN or VLSC. In order to deploy Windows 11 using SCCM to a new device, we need to download the. If you need to identify which machines are ready in your organization, you can use our free Windows 11 Readiness report :įree Readiness MEMCM / SCCM Windows 11 Report () Download Windows 11 ISO High definition (720p) display that is greater than 9” diagonally, 8 bits per color channel Trusted Platform Module (TPM) version 2.0Ĭompatible with DirectX 12 or later with WDDM 2.0 driver Processor:ġ gigahertz (GHz) or faster with 2 or more cores on a compatible 64-bit processor or System on a Chip (SoC) This would be the major reason if you’ll upgrade your devices or not. Here are Microsoft official requirements needed for Windows 11. If you’re already running an ADK version on your SCCM server, see our post on how to install a new version. Windows recommends using the Windows ADK that matches the version of Windows you’re deploying. Windows ADKīefore capturing and deploying a Windows 11 image, make sure that you’re running a supported version of the Windows ADK. See the following support matrix if you’re running an outdated SCCM version and make sure to update your site. You need at least SCCM 2107 in order to support it as a Windows 11 client. Launch the Process on a new Windows 11 computerīefore the SCCM Windows 11 Deployment, we’ll make sure that all our tools are updated : SCCM Version.Launch the Upgrade Process on a Windows 10 computer.Deploy the SCCM Windows 11 Upgrade Task Sequence.Create a Windows 11 Task Sequence for new Windows 11 computers.Create a Windows 11 Upgrade Task Sequence for existing Windows 10 computers.Check if you have an SCCM Supported version.Let’s get started to Deploy Windows 11 using SCCM / MEMCM ! Table of Content You need to run at least SCCM 2107 and your device needs specific requirements. You can read the whole post but here’s the important part: SCCM is ready to support Windows 11 starting with SCCM version 2107. In a previous blog post, we listed everything you need to know about SCCM and Windows 11. Like any other Windows version, you need to do a couple of tasks before you can do an SCCM Windows 11 Deployment. If you are planning to deploy and manage Windows 11 using SCCM or Configuration Manager, this post has you covered. Even though the name says “Windows 10 Classroom Software” it will run on Windows 7.Windows 11 has been released by Microsoft on October 5th, 2021. I could install them on a template computer, and remove their unique components, but it is just as easy to install them during deployment. The main reason why I do not build these into the image is that their values need to be unique on every installed instance. For example, my bundle is called “Windows 10 Classroom Software.” It contains Symantec Endpoint Protection (SEP), the BigFix client (IEM), and the Sassafras K2 client. To get around the prompt and have MDT install the necessary applications, I create an app bundle, add my desired apps to the bundle and have the Install Applications step just run that. This is good for versatility, but can get a bit repetitive if done many times. In the “State Restore” section, one step we really don’t have to touch is “Install Applications.” In its default state, the MDT wizard will prompt the end user to install any or all applications listed on the deployment server. However, additional steps can be added to sweeten the task sequence. This is a quick way to get up and running with a basic Windows install. MDT will install Windows 7 and only use drivers detected by WMI for the installed hardware. Selection Profile = Nothing / Choose all drivers… The name and description should be concise and meaningful as it is shown to the one doing the imaging on the image selection screen, from Windows PE. Whatever works is fine just as long as each ID is unique. Example: DEPW7EX64 for deploying an image of Windows 7 Enterprise 圆4, or CAPW7EX64 for capturing an image. I like to use a truncated version of what the task sequence does for the ID. The ID becomes the name of the folder for the task sequence in the deployment share’s file system hierarchy. Each task needs a unique ID for starters, and a name which can or can not be unique. The process of creating a new task sequence is wizard driven like many things in MDT. Creating folders is just as easy as starting to create a task sequence, right-click the node above and choose “New Folder.” Also, if one was to create an offline MDT deployment share, separated tasks and operating systems can make your selection profile much slimmer. I haven’t run across the need to use the same image with multiple different task sequences. Generally, one operating system image goes along with a single task sequence. MDT’s operating system and task sequence folders are the same.
0 Comments
Read More
Leave a Reply. |