SCCM Tips, Scripts and Tools

I just released a new update to my ISOtoUSB tool. The tool now has some better notifications and some bug fixes. you can get more info and download the update from the ISOtoUSB page http://www.sccmtst.com/2018/01/isotousb.html  

Some of you may have had the issue where the ISS Application pool for WSUS keeps stopping. In most cases the stop is do the the Application Pool needs to use more memory then it is configured to use. 1. The way to resolve this is to open IIS expand the node and click on application pools in the list find the Application Pool called WsusPool and right click on it choosing Advanced settings. 2. In the Advanced Settings window scroll to the bottom, You are looking for "Private Memory Limit (KB)" 3. Once you find the settings change it to a larger amount be sure you do not set it higher then the memory you have installed on the server. Settings the amount to 0 will get it to unlimited. That's it once you click ok you should stop having this issue.

SCCM is able to do a lot but sometimes you need to sometimes you need to Install software uninstall the old version move some config files then remove a old shortcut and this all needs to be done as an application deployment. By default SCCM isn't able to handle all of that as an application deployment so you will need a scrip to do it. A while ago I was given a scrip that dose all of that and more the script was old and not all parts of it functioned  so I doctored it up and made it a little more user friendly. The scrip is called Install-Wrapper.ps1 is very easy to use.  You can get all the scripts from HERE To start enter the appropriate information under Software Information and uncommnet the actions you want to run. Then in SCCM create an Application for the script and for the install parameter enter. powershell.exe -ExecutionPolicy Bypass -NoProfile -File Install-Wrapper.ps1 The msi file should also be in the same folder as the script. If yo...

Build a custom Windows PE disk with a easy to use GUI interface. PEBuilder is an application that allows you to build a PE image the way you want it. You can enable PowerShell and other components with a simple click of a check box. You can also add your own compatible application right to the image. The tool is simply a GUI over top of my PEBuilder PowerShell script. That way if you still would prefer to use the PowerShell script you can do so. Below is a list of applications that will by default be added to the Windows PE image. You can remove these from the GUI or add your own. Just click add app and point to the containing folder.   What Application are included PowerShell - Microsoft PowerShell Cmtrace - Log view application Defraggler - A defragging tool Explorer++ - File explorer Notepad++ - Advanced text editor ntpwedit - Windows password reset tool PENetwork - Ntwork configuration tool Produkey - Product key finder SearchMyFiles ...

I have updated my ISOtoUSB to version 2.3.1.4 tool you can get the tool from HERE 

ISOtoUSB is a simple PowerShell script that burns a ISO files to a drive. The script formats the drive then makes the drive bootable and writes the ISO file to the drive. Change Log 3-28-18 Fixed a issue that would stop the ISO file from being dismounted if the file path had a space Fixed a issue that caused the progress description to be obscured by the burn button  Added error logging to the GUI progress description 1-31-18 Added NTFS and FAT32 file system support  Recompiled to exe to a better format  Updated the icon file to be in the script  8-2-17 Removed CD/DVD drives from the Available Drives List Add the File System Label to the Available Drives List Added scroll bars to the Available Drives List  Added the ability to name the new volume label  Removed the Cancel button  Removed the window resizing handle  Script now uses Robocopy to write the ISO files to the drive (Better handles the file copy process) reorgan...

For some addons and features you will sometimes need to add additional components to your SCCM boot image, things like PowerShell and HTML support. I will show you how you can do this for your x64 boot images. To do this for x86 images just replace x64 in the file paths with x86. 1. Create a folder where you keep your content called BootImages 2. Create a folder called Custom-x64 or something that will tell you what boot image is held in this folder. 3. Navigate to \\<SiteServer\SMS_<sitecode>\osd\boot\x64\ .  In this location you should see a boot.wim file, this is the built in boot image file. Copy this file to the folder you created in step 2 4. Open your SCCM Management console and navigate to Software Library > Boot Images. Create a folder called Custom 5. Click on the folder you just created then from the top ribbon click add Boot Image  6. Navigate to the Boot.wim file you put in the BootImages\Custom-x64 folder 7. Give the Image a good d...