You can either create a share for the files or create a SCCM package. If you have more images you should add them with an “OR” to line 144:ĥ. In this example “WIN7alm” for Windows 7 and “WIN10alm” for Windows 10. I’m using a computer variable called “ODSImage” where I write witch OS the task sequence should apply. Edit the “PreFlight.hta” line 154 and add the IP address of the servers that you would like to ping. The values here should be the same as the value in WMI in the Win32_ComputerSystemProduct Class in either Name or Version Property depending on you Manufacturer.ģ. “ComputerModels_w7.txt” and “ComputerModels_w10.txt” These files are used for your supported computer models. “logo.png” You can add your company logeĬ. “background.png” You can add your own backgroundī. Download OSD Pre-Flight Checks.zip and extract the files to a folder called “OSD Pre-Flight Check”Ī. SCCM have updated your distribution points and your boot image have HTA support.ġ.
Click “Yes” to update the distribution points Select “HTML (WinPE-HTA)” and click “OK”ħ. Right click on your boot image and choose “Properties”ĥ. Open your SCCM console and go to: Software Library –> Operation Systems –> Boot ImagesĢ. You have to have HTA-Support enabled in the boot image.
The user cannot continue if ALL the check are not a success. Otherwise the user have to correct the problems and click on the ‘Refresh’ bottom to continue. If all the checks are Success, then the HTA will automatic countdown from 15 seconds and continue. – WiFi check (To make sure that a laptop is not running the OSD on Wi-Fi) – Drive Encryption Check (To make sure that the HDD is not encrypted)
– UEFI Check (To force UEFI if task sequence is Windows 10) – For laptops, AC power connected (So it is not running on battery) – No USB drives attached (To make sure that there is no USB drives attached) – Network connection (To make sure that we can access the SCCM environment)
– Only supported hardware models (To make sure that there is driver for the model) Here is the things that I would like to check for: This solution is using this hta with some customization that I have made. This Pre-Flight check have to be at the beginning of your task sequence, because then you don’t break break anything on the existing installation if the requirement is not meet. To make sure that a Pc is ready for your task sequence deployment and to minimize the risk of an error during OSD, you can do some checks before you start your OS deployment with a Pre-Flight check.
I have extended that check with this Pre-Flight Check. Last week I created this post on how you can do a UEFI check if you are installing Windows 10. Because this happens before initialization of the new version, you can continue to use your existing version while you investigate the issue, then rerun the upgrade-tsm script.UPDATE: I have updated the hta script, because there was an issue with the Wi-Fi and UEFI detection.
Port conflicts stop the upgrade process before initialization starts, allowing you to correct the problem. Any permissions issues are logged to the app-upgrade.log but do not block the upgrade.