In this post I will show you have to create 3 steps in your task sequence that checks if the computer is running UEFI. This is useful if you are installing Windows 10 and want to make sure the UEFI is enabled. The check is running at the start of the task sequence, so it doesn’t format the disk if the BIOS setting is not UEFI. This means that you can boot the Pc with the old installation if the check fails. If you want to semi automate the switch from BIOS to UEFI, see this post. 1E have a fully automated process and you can get more information here. Nickolai Andersen have a blog post where he automate the switch on Dell computers. Thanks to the blog post on Garytown for the inspiration.
Microsoft have released a Windows 7 convenience rollup that contains security updates from SP1 up to April 2016. This is nice because creating a reference image with all the patches is time consuming, because there is so many patches to be installed. In this guide I will show you how to patch the Windows 7 Sp1 wim file. This will make the reference image creating a lot faster.
1. Download the Windows 7 convenience Rollup here. Save it to C:\Update
2. Download the KB3020369 here.
3. Open a CMD in Admin mode
Recommended settings for Windows 10 is UEFI with secure boot enabled. But you can’t change the Bios boot to UEFI boot with the build in steps in SCCM. But here is a quick and dirty way to do it semi automatic. You should have an Task sequence Available and not required for your Windows 10 deployment. Thanks to Mike Terrill blog post for the inspiration.
In the guide you are going to use the bios configuration that you have created in this blog post. Remember to configure the Bios for UEFI and secure boot
If you don’t want all the default Windows Store Apps that comes with Windows 10, then you can follow this guide. Removing Windows Store Apps will also make the first logon faster.
1. Download RemoveApps.ps1
2. Run it on your reference machine
3. The first time you run the script it will generate a xml file in the same folder where the script is. It contains all the apps that have been removed. If you don’t want to remove all the windows store apps, then you can remove the apps that you want to keep in the xml file. Then put it in the same folder as RemoveApps.ps1. The script will then look for the xml file and only remove the apps that is defined in the xml file. Example of the xml file:
In this blog post I will show you how you can update the bios on HP computers in OSD.
1. Down the bios update from HP’s website
4. Commandline: HPBIOSUPDREC64.exe -s -pBios_Password.bin -fHP840G1/L71_0136.bin
5. WMI query: Select * From Win32_BIOS WHERE SMBIOSBIOSVersion LIKE “%01.36%”
Microsoft Edge is the default browser in Windows 10. You can change that and apply the setting during OSD. Here is how.
1. Login to a reference machine.
2. Go to All Settings –> System –> Default Apps
Note: You can also make settings for other default apps, as we will export default settings for all apps.
4. Create a folder called “DefaultApps” on the C drive.
4. Open a CMD as Administrator
Follow this guide to manage windows 10 taskbar via OSD. Thanks to Jörgen Nilsson for the inspiration.
1. Download ManageTaskbar-1.0.zip and extract it on your reference machine.
2. Modify the taskbar as you would like to have it
4. Copy the folder “C:\Users\%username%\appdata\roaming\Microsoft\Internet Explorer\Quick Launch” folder to the “ManageTaskBar” folder.
5. Rename “Quick Launch” to “QuickLaunch” (Remove the space)
You can do the following to get rid of the “Disable apps to help improve performance” message.
1. Create a “Run Command Line” step with the following command:
You can install application dynamically with AD groups and create role based installations. Thanks to Jörgen Nilsson for the inspiration.
1. Download Get-AppGroups.ps1 and put in a SCCM package.
3. Add the application name from SCCM in the description of the AD group that you created in step 2.
There is a very easy way to test task sequence variables without doing a full OS deployment. You can use “ServiceUI.exe” witch is located in the MDT toolkit package under “Tools\x64\” and then run it on a Windows machine.
2. Deploy it to a collection that contains you Windows Test PC and run it from “Software Center”.