In this post I will be discussing on how to fix the issue “no task sequence found” for new devices. This is a very common error we see while trying to initiate the SCCM task sequence. Sometimes we see this error for old devices and sometimes for new devices. Let’s looking into it why it is caused.(more…)
SCCM client log files located under c:\windows\ccm\logs have a huge list of log files. This can be daunting for beginners to think about which logs should they be checking in various scenarios such as application deployment, package deployment, task sequence, hardware/ software inventory, software metering etc.
If we know the correct set of log files required for specific component, this will help us analyse and troubleshoot the issue.
I will also be sharing few SCCM tips and tricks to read the log files efficiently. Using below mentioned techniques will help you analysing the logs more easily with least efforts.(more…)
To create msix package, you need MSIX Packaging Tool. While installing this tool, you might stumble upon installing one of the pre-req ie. MSIX Packaging Tool Driver. While installing packaging tool, driver gets installed automatically. In few instance you might see the error code 0x80131500 with message:
We encountered an error when trying to install your driver. More information is available in your logs.(more…)
In this post I will be discussing on how to track SCCM application deployment through client log flow. There are several components involved with application model which is more complex than packaging model. I will run through all the important log files which plays vital role and also very much helpful while troubleshooting application deployment issues.(more…)
This is a short post where I am sharing an issue which I phased after upgrading to SQL Server 2019 for my Configuration Manager Database. After upgrade, I wasn’t able to open any report because of the following error:(more…)
During Operating system deployment using SCCM task sequence, one of the most important log file is smsts.log whose location used to get changed during multiple phases of deployment.
During SCCM OSD, we can press F8 to open Command prompt and can navigate to any folder to look out for the logs.(more…)