SCCM Tips, Scripts and Tools

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

We have just released iso2usb 2.3.8, However you may have noticed the name has changed. Due to some bad people out there we found our application had the same name as malware leading to our application being flagged by some anti-virus applications. So we desided to change then name to ISOBurn. A few changes you will notice is the layout of the application, ISOBurn is no longer a single exe. We did this to make future changes easier and allow for more robust feature. Once such feature is the ability to stop the application for checking for updates. You can do this by going to the app folder and opening the settings.ini file with note pad. Edit the line CheckForUpdates=True and change True to False. You will also notice the AllowBurnToSystem this setting allows the application to burn an iso to a system volume erasing the current os. We did fix one major bug and that with an issue not properly notifying the user of an update. As always you can get the latest version from the ISOB

PowerShell Module to create, delete and mount a Volume Shadow Copy. Not only can you manage shadow copies on a device but it also tells you the status of the shadow copy and where the shadow copy is mounted to. Installation  ShadowCopyHandling can be installed by either running Install-Module -Name ShadowCopyHandling or by downloading the package directly from https://www.powershellgallery.com/packages/ShadowCopyHandling Commands Get-ShadowCopy  Shows information about all shadow copies on the system New-ShadowCopy Create a Shadow Copy for a volume Mount-ShadowCopy Mounts a specified shadow copy to a symbolic link Dismount-ShadowCopy  Dismounts a specified shadow copy from a symbolic link Remove-ShadowCopy  deletes a specified shadow copy from the system

 Message Handling is PowerShell Module designed to write a message to a log file, Event log or PowerShell host window and provide the ability to perform a task based on the message type. The Module can be imported and will provide a Write-Message function. The Write-Message function can also be used as a standalone PowerShell script. The idea of the Write-Message command is to write an Error, Warning, Information or Success message to a desired forum and perform an action based on the message type. The module is designed to be flexible to fit most needs. To perform an action based on the message type there are 4 internal functions Invoke-Error, Invoke-Warning, Invoke-information and Invoke-SuccessAudit. Code can be added to each function to additions task will be performed when a message of that type is written. The command requires that at least one of the write parameters (WriteLog, WriteEvent, WriteToHost) is specified for the script to actually do anything. Each will wr