Biggest Blunder in SCCM







Please go through the link and check out the biggest blunder made during use of SCCM. This link will give to idea about what not to do during the use of SCCM and lesson learnt.


https://www.reddit.com/r/SCCM/comments/6not6x/what_was_your_biggest_blunder/


" One stupid mistake can change everything."


- Aarif

Comments

Post a Comment

Popular posts from this blog

Error code 26352 while installing application

I was trying to install prerequisite of a web-based application, and getting error 26352. Verbose logging were showing it a certificate issue. I have imported required certificate but still installation was aborted with error code 26352. As a workaround when I looked into the certificate store. I found several certificates were present in the store with same name. Once I removed all, again imported the required ones it works fine. Please comment for other ideas or this blog helped. - Aarif 
Read more

Step by Step SCCM Client Remediation

Image
    This is most useful blog for SCCM client remediation. I will try to explain all possible point to be looked. These are steps we can use while remediating client on any machine manually. Check to ensure WMI connectivity Use Windows Management Instrumentation Tester: The Windows Management Instrumentation Tester dialog box is displayed when you click Start, click Run, and then type wbemtest.exe in the Open: field. This dialog box provides access to all WBEMTest functions. You should get screenshot below: Try to connect to the namespace like show in the below screenshot.   In the Namespace field, enter the path. On newer versions of Windows this defaults to root\cimv2 which is where all of the Win32 classes reside and what most people use. But if you know the path to another namespace, like root\SecurityCenter2 go ahead and use it. The default is the local computer which if that is the case all you need to do is click
Read more

Symantec Endpoint Protection Agent upgrade using SCCM

I have worked on a upgrade of Symantec Endpoint Protection Agent on 60000 devices including server and workstations. The upgrade was having several challenges and issues but here are some scripts that will help in upgrading with ease. -------------------------------------------------------------------------------------------------------------------- Installation Script ( Verbose Logging Enabled) : This script can be use to install SEP agent (if SEP is provided by the SEPMC) silently. '-------------------------------Start of Script----------------------------------------- '------------Install 32 bit Symantec Endpoint Protection12.1.5337.5000 ------------------ On error resume next dim fso, wshll, Dir, Path, key, installdir, uname, ttime, loc, sloc, Exepath, cmdline, cm, SCPath Set fso = createobject("Scripting.Filesystemobject") Set wshll = createobject("wscript.shell") PRODATA = wshll.expandenvironmentstrings("%ProgramData%"
Read more