SCCM Tips, Scripts and Tools

  In the last day or so CVE-2022-29072  was released. This is a vulnerability that allows an attacker to use a malformed 7zip archive to gain local administrator rights to a computer. Until an official patch is released one of the recommended ways to resolve this is to remove the 7-zip.chm file as it is the Windows help system. We have put together a script to do just that.   $Vols = Get-Volume | Where-Object -Property DriveType -NE "CD-ROM" | Where-Object -Property DriveLetter -ne $null foreach ( $V in $Vols ) { $Files = ( Get-ChildItem -Path $( $V.DriveLetter + ":\" ) -Recurse -Filter "7-zip.chm" ).FullName foreach ( $F in $Files ) { Remove-Item $F -Force } } You can plug this script into an SCCM package to deploy to all your systems. Since 7zip offers a portable version and some software uses 7zip as a built-in utility we made the script scan all volumes on the computer that are not CD-ROM drives and that have a

One common issue we face as SCCM Admins is trying to keep common software up to date. Things like Chrome, Firefox, and VSCode always have new updates and maintaining that across Application deployments and Task Sequences can be tricky. I have started to use some script wrappers to help with this. These scripts are able to be packaged up as an application and deployed however you need it to be used.  I have created 2 scripts for each application, First is the app.ps1 and the second is install.cmd. The app.ps1 script is what does all the heavy lifting, the script will download the latest version and install it as well as find the needed string to run an uninstall command so an uninstall action can be provided in Software Center. The install.cmd script is a simple batch script that executes the ps1 script. I have included this to make it easy to create an application for the script as well as provide a simple way for a technician to run the scripts independently of Software Center or SCCM

  A new version of the windows 10 setup script has been added to our PowerShell gallery repository. We have made a few changes that not only make the script easier to read and understand but also add more functionality to the script. One of these changes is adding the ability to disable SMBv1. By disabling SMBv1 you can add more security to your devices as many crypto viruses use this to encrypt all your data. Disabling the protocol helps to prevent these types of attacks on your data. We have also added a Parameter to the scrip that gives you the ability to disable location and tracking services on the OS. This will provide better privacy and further reduce resource consumption on the device. More information about the script can be found on our official Windows 10 Setup Script page along with links to download the new version. 

We have just updated out get-systeminfo Powershell module to 3.2.7. With this update we have fixed some bug that would throw false errors as well as fixed an issue when not using the -computername parameter the computer name property would not get filed.  To download the newer version head over to our product page at  https://www.mosaicmk.com/get-system-info

  Now that I have more resources at my disposal I have finally been able to get ISO2USB working. Over at MosaicMK we have renamed the application to ISOWriter and have gotten the application to work correctly. We have 2 options available for using ISOWriter, 1st is the standard windows install and the other is portable choose what best works for you and write away.  You can find ISOWriter and other apps HERE

 When a little after windows 10 build updates started coming out Microsoft released a new feature in SCCM called Windows 10 Serving. This feature is used to deploy windows 10 build to devices, However the deployment status and some of the reporting are not always the most accurate. So I will show you away that you can deploy the update using a standard application deployment. You will need to enable the windows 10 serving feature in your SCCM environment or have access to a SCCM setup that has windows 10 serving enabled.  If you dont have it enabled here is a good way to do so  Download the Windows 10 Serving Update, to do so find the update and right click Download  Once you have the update downloaded navigate to the path you downloaded the update to and copy the content of the GUID folder to a folder in your content library source. You should see a esd file and a WindowsUpdateBox.exe file in the folder. In the folder you copied the content to create a bat file with the following sta

Some times when you are create a script you need to store some credentials for a specific command to work like connection to Azure or Office 365 storing the password in a file or in the script has always been something you just dont do. That is where leveraging the windows credential manager can be handy though PowerShell dosnt have this ability nativly you can get the ability by installing our Credential Management Module from PowerShell Gallery by running  Install-Module -Name CredentialManagement once installed you can store a credential with the Add-StoredCredentials comment and call it with the Get-StoredCredentials command One thing to keep in mind the credentials are stored on a per user basis which means the PowerShell console needs to be running as the user that wrote the credentials to Windows Credential Manager. For more information about Credential Manamgment Please see https://www.mosaicmk.com/2019/07/credential-management-module.html