Category Archives: SCCM
SCCM reporting functions provides you to track your deployment status and this give you ability to measure how successful in your deployments.
In an enterprise environment you may want to share this functionality to be used by your first level support within limited rights. I will explain how to provide this functionality as limited as access rights.
First I advide you to create a security group in Active Directory with a name “1st level support”. First level operators should be a member of this group and you will set the sccm reporting rights for this group.
Than you should open SCCM Reporting tab and you will see some options like to give the access rights.
The group should be add in Reporting Class (instead of Instance) with Read Rights.
SCCM has may reporting functionalities therefore you may want to set rights for spesific report also like “status of an advertisement of an spesific computer” that’s on of the most popular that used by the helpdesk tead to track the deployment status of an computer.
In the following articles I will try to explain custom repoting by SQL scripts if I need time 🙂
SCCM Agent Installation Parameters
While you are deploying the agent you will use some parameters fits with your enviroments needs. I will explain the parameters below.
Windows Management Instrumentation
This is the main component that SCCM Agent based on to work with Operating System. In this Article we will what tha WMI is and its subcomponents and how can you troubleshoot the WMI problems.
User interactive series has been started. You will not let the end users to make any mistakes. 🙂
Here is the screen lock command line parameter that you can use during deployment.
Your deployment success is directly dependent how your Task Sequence was designed. Sending an installation documentation to end users is a good idea but they will never like to read the instructions. In this phase you may want to notify the users during deployment.
Here is the powershell command below that you can use ;
How to Deploy .NET Framework 4.0 via SCCM ?
One of the most common problem when deploying .NET Framework 4.o is handling unexpected restart during a Task Sequence. If you would like to deploy .NET Framework 4.0 in a Task Sequence you would see some kind of logs that the command completed successfully and your Task Sequence will restart unexpectedly. This issue is directly regarding with handling success codes. 3010 is the code that was genereted by the installation progress and you will see as a success record when you check the report.
You have two options to handle this situation.
1. Deploying via command line
2. Wrapping the installation in a VBScript.
For the first option you may deploy with Command line with the parameters below.
“dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT”
If you would Return the success code into 0, than you may use the script below ;
—————- script begins —————
Set WSHShell = WScript.CreateObject(“WScript.Shell”)
WSHShell.Run “dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT”, 1, True
Set WSHShell = Nothing
Retval = 0
—————— script ends —————