Universal Task Sequence Import - SCCM Task Sequence with a GUI

By -
Previously I put together a how to on building a SCCM Task Sequence that allows you to choose what image file and software is applied to a computer and perform a few other tasks. Its good to know how to do the process from scratch but with how long the process of building your own Universal Task Sequence is I decided to export the TS to that you can import it into your own environment and customize it as you need to. You can download the TS from HERE, it can take some time to download its about 8gb. So start it off and go get some coffee.

Once the file is downloaded unzip the file and copy the content to the where you keep your SCCM content files (Should be a UniversalTaskSequence_x64_files folder and a UniversalTaskSequence_x64.zip file) .

Open your SCCM Console and navigate to Software Library > Operating Systems > Task Sequence and along the top ribbon you will see Import Task Sequence from there browse to where you put UniversalTaskSequence_x64.zip.



Once the TS is imported it should look like this. Note the Driver task, they may not work correctly since only the driver package gets exported but I wanted to include them as examples of how you can configure your own driver packs.



The TS is setup to give options for Windows 10 and Windows 7. You can configure it to user whatever images you want as long as they are all 64 bit image files, if you need a 32 bit image you need to create the TS from the 32 bit example files in the TS setup post.

If you modify any of the Packages you need to update the content on the DP before you will see the changes in the TS

Comments

  1. AnonymousNovember 1, 2023 at 8:54 PM

    Link to download Task sequence not working can you share?

    ReplyDelete

Post a Comment

Popular posts from this blog

SCCM Task Sequence GUI - How to set up the TS to work with a GUI

By -
Image
Before I have posted how you can create a TS for windows 10 , add a GUI to your TS and run a script to configure your windows 10 install . However all of this has become out dated and so I wanted to update all of that. This how to will walk you through how to create a TS that will allow you to choose a windows 10 or windows 7 image, name the computer, add the computer description to AD, Choose form a list what applications you want to install, Choose to enable BitLocker and set the PIN as well as create a local account. Prerequisites: MDT integrated to SCCM A boot image with the following components added Windows Powershell(WinPE-DismCmdlest) HTML(WinPE-HTA) Microsoft .NET (WinPE-NetFx) Windows Powershell (WinPE-Powershell) A windows 10 and windows 7 image  1. Download the package I have put together containing the scripts you will need https://github.com/sccmtst/SCCM-Management-Scripts/tree/master/TSGUI 2. If you have not already done so download and in...
Read more

SCCM Applications vs. SCCM Packages: Understanding the Key Differences

By -
Microsoft System Center Configuration Manager (SCCM) is a versatile and powerful tool for managing devices, applications, and updates in an organization's IT environment. Among its many features, SCCM allows you to deploy software to your end-users in two primary ways: Applications and Packages. Although both methods have a similar goal, they have some key differences that IT administrators should understand when choosing the appropriate deployment method. In this blog post, we will explore these differences and help you decide which option is best for your organization. Definition and Deployment Scenarios SCCM Applications: An SCCM Application is a high-level, user-centric deployment method that focuses on providing the desired user experience. Applications are designed to be state-based, meaning they can detect if the application is already installed and only perform the necessary actions if the application is not present or if a newer version is available. Applications are suita...
Read more

Faster PXE boot times in SCCM 1606 and later

By -
Image
A new feature introduced with SCCM 1606 was being able to modify the boot times for PXE. This is done by modifying the TFTP block and window size of the boot image RamDisk. This was originally implemented to help a admin over come network requirement. This allows us to make the PXE boot times much faster for my self this meant taking a 10 minute boot time all the way down to 30 second boot time. In order to make this change you need to create 2 registry keys on your PXE enabled DP. Location : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP Name: RamDiskTFTPWindowSize Type : REG_DWORD Value : <customized window size> The default value is 1 (1 data block fills the window)  Location : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP Name: RamDiskTFTPBlockSize Type : REG_DWORD Value : <customized block size> The default value is 4096 (4k).  once you have added the registry keys you will need to restart  the Windows Deployment Service for the ch...
Read more