Posts

Showing posts from November, 2017

SCCM Client Install Error Codes

Image
When installing the client you can look at the ccmsetup.log to tell when the setup is done. However there are a few different return codes that can be shown below is a table of what the codes mean.


SCCM Client Health Check

Image
This script will check components used by the SCCM client and if an issue is found it will attempt to fix the issue.

1. Looks to see if the the client is installed, if not it
will install the client from the specified location.

2. Next the script will check the startup type and status
of services needed for SCCM

3. Runs specific client actions to verify they are working

4. Checks to see if basic WMI queries are working and that
the SCCM name space is working.

5. If an issue is found that can be resolved by reinstalling
the SCCM client this will happen last. The scrip will also
look for any reaming client files and remove them to be sure
there are no corrupted files left behind.

This script is best used in a Scheduled task deployed via a GPO




<#.SYNOPSISSCCM client health check and repair.DESCRIPTIONThis script will check components used by the SCCM client and if an issue is found it will attempt to fix the issue.1. Looks to see if the the client is installed, if not it…

Multi-Software Install Wrapper

Image
Yesterday, I released a script, Install-Wrapper.ps1, that allows you to do more with a SCCM Application Deployment then just a single task. The Install-Wrapper script will only run a single application install and yes you could modify the scrip to do more but I found it much easier to use another script. The Multi-Software Install Wrapper script allows you to plug the Install-Wrapper script into it and install software in an order or stop the process if an install fails.

The only part of the script  you need to modify to use it is under the variables to set section of the script. The $Installs variable is where you will enter the name of the Install-Wrapper scripts that are to be part of this application deployment. Again the Install-Wrapper script should be in the same content folder as the Multi-Software Install Wrapper script. The other variable, $ExitOnFail will determine if the script should stop if the other install scripts fail. If you want the script to stop on an error change…

Advanced software install wrapper script

Image
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 part 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 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-ExecutionPolicyBypass-NoProfile -File Install-Wrapper.ps1
The msi file should also be in the same folder as the script.

If you need to deploy multiple applications with the script you can use the Multi-Install scr…