SCCM can be used to deploy packages and applications on multiple computers. But as with any other deployment tools, you can get errors or issues. This blog post will describe the SCCM Error 0X87D00324 which occurs on computers after application deployment. What Causes Error 0X87D00324 During SCCM Deployment? This error code means that the application was installed, but it couldn’t be detected by SCCM. Usually, a faulty or incorrect detection method is set in the application you are deploying. The detection method is SCCM ways to know that the application is installed on a computer. After the installation, SCCM validates the presence of the application using the detection method parameter. The SCCM Error 0X87D00324 tells you that the application is not present on the computer. however, this can be misleading, the application can be installed correctly but SCCM will report it as not installed if the detection method is not … Read More
How to use SCCM Dynamic Queries in your Deployment Collections
In this post, we will be looking at using SCCM dynamic queries to populate collections in our deployments. As an SCCM administrator, you most likely had to plan out mass deployments to all your servers or workstations or even both. How did you go ahead and populate your collections? Queries? Since the introduction of SCCM 2012, we now have a multitude of options, most notably: Direct membership Queries Include a collection Exclude a collection Chances are, if you are deploying new software to be part of a baseline for workstations (for example), you will also add it to your task sequence. In my past life, I must admit, I really did like queries. They can be such a powerful tool to populate your collections. I always was looking for ways to pimp the usual types of queries we use. For example, we developed a fabulous list of operational collections that we … Read More
SCCM Report Builder Error – The Certificate Chain was issued by an Authority that is not Trusted
If you’re like us and love to create and build awesome reports, you may get an error when running report builder on a remote computer. When editing an SCCM report in Report Builder you may receive the following error: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 – The certificate chain was issued by an authority that is not trusted.) SCCM Report Builder error – Cause This error occurs because you don’t have the required SCCM SQL certificate on the computer running Report Builder. Follow the following steps in order to resolve the issue. Export the certificate from your SQL server On the SQL Server Click the Start menu, click Run, and then type mmc. Click Enter. This starts the Microsoft Management Console (MMC) In the console, click the File menu and then click Add/Remove Snap-in On the … Read More
SCCM 1810 Client Notification error
We had an issue in one of our clients site where some SCCM Administrator were receiving SCCM 1810 Client Notification error in the console. They informed us that they just upgraded to SCCM 1810 recently. When we tried to initiated a client notification on SCCM 1810, the following error occured : Clearly a missing permission in the security role of the affected users… but which one ? We found our answer in the SCCM 1810 What’s new documentation : A new permission is now required to perform the Client Notification Actions. SCCM 1810 Client Notification error Resolution Here’s how to fix this error : Go to Administration\Security\Security Roles Select the security roles that applies to your affected user, right-click and select Properties In the Permission tab, go to Collection (not SMS_Collection) Set Notify Ressource to YES Repeat for any other security role That’s it, your user will be able to do again … Read More
Operating System Deployment SCCM 2012 0x80070570 Error
During an operating system deployment using SCCM 2012, you received the error code 0x80070570 at the beginning of the Task Sequence. Numerous errors and warnings are showing in SMSTS.log : ThreadToResolveAndExecuteTaskSequence failed. Code(0x80070570) Failed to create C:\_SMSTaskSequence (1392) The TSM directories could not be created at this time (80070570) uRet == ERROR_ALREADY_EXISTS, HRESULT=80070570 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,1903) Cause The SCCM 2012 0x80070570 error is translated to : The file or directory is corrupted and unreadable. This issue is completely external to SCCM 2012. If you try to launch the Windows installation from the CDROM, you will get the same error. It’s probable that your computer has been incorrectly shutdown and Windows wants to do a check disk at the next reboot. How to fix SCCM 2012 0x80070570 Error You have 2 options to fix this error Option #1 | Chkdsk Boot the machine and let Windows complete the checkdisk process Reboot the computer and restart the Task … Read More
Windows 10 Error Code 80240020
Windows 10 has just been released, Microsoft is calling it the biggest software update in history. With massive installations at the same time, many users has been reporting errors when upgrading. The most common error is Windows 10 error code 80240020. Microsoft explains this error in the following statement: This is an expected message indicating that when installation begins it may require user interaction. This is the largest software upgrade event ever and we’re managing it so everyone has a great experience. We recommend waiting until your PC receives a notification to upgrade, and then following the instructions provided. Please note that there is no problem with your reservation or upgrade download. The upgrade download is not corrupt as some have stated, and you will be notified in the coming days or weeks when your device is ready to upgrade. How to fix Windows 10 error code 80240020 Method 1 – Download folder Go … Read More
Failed to resolve selected task sequence dependencies 0x80040104
I had to troubleshoot a problem where a Task Sequence return the error Failed to Run Task Sequence. SMSTS.log shows : Failed to resolve selected task sequence dependencies 0x80040104 Not big of a deal, this error oftently occurs. It just means that some package referenced by a task sequence is not distributed to the distribution point. This should be an easy fix… well not in this case. Troubleshooting When reading SMSTS.log we can find the problematic package ID. In this case KR100048 was the bad guy. So I did the basic troubleshooting in those cases : Open the SCCM Console Navigate to Software Library\Operating Systems\Task Sequences Click Reference tab at the bottom Locate the problematic ID (KR100048) Note the package Name (Windows x64 – HP ProBook 650 G1) First problem : the Size column is 0.00MB ?!? I immediately thought that I’ve probably forgot to distribute this package on my distribution point. … Read More
SCCM Reporting Point Error after R2 Upgrade
This post explains how to fix SCCM Reporting Point Error after R2 Upgrade. SCCM Reporting Point Error after R2 Upgrade Problem : After upgrading from SCCM 2012 SP1 CU2 to SCCM 2012 R2. You get the following error when running reports : An error has occurred during report processing. (rsProcessingAborted) Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow) Conversion failed when converting the nvarchar value ‘S-1-5-21-1010946700-728571707-39459515-134623’ to data type int. Removing and adding the “Reporting Service Role” did not fix the issue. SRSRP.log has Invalid Class errors : Invalid class SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)Could not retrieve the reporting service name for instance ‘RPSERVER’ SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)Invalid class SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)Could not stop the reporting service ” SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0)Next security configuration at [07/7/2014 1:52:12 PM] SMS_SRS_REPORTING_POINT 07/7/2014 1:52:12 PM 6096 (0x17D0) Resolution:The problem is due to the … Read More
Endpoint Protection Policy is not Applied
This post explains what to do when Endpoint Protection policy not applied Symptom The policy was applied to a specific collection and all members of the collection were failing to apply the policy Monitoring / Endpoint Protection Status / System Center 2012 R2 Endpoint Protection Status / Operational State 12 clients are failing to apply the custom policy. Clicking on the “Antimalware policy application failed” brings us to the list of machine. On the bottom, clicking on the “Antimalware Policy” tab shows the error : 0x80004005 – Failed to generate Antimalware policy file Let’s look at the EndpointProtectionAgent.log on one of the affected client. Failed to generate AM policy XML with error code 0x80004005 State 2 and ErrorCode -2147467259 and ErrorMsg Failed to generate Antimalware policy file You can see that my policy “Endpoint Protection CTX 4.5, 6.0 & 6.5” is failing. Error 4005 would make me think about “Access Denied” error … Read More
SCCM 2012 Management Point Error 1603
We have recently experienced a SCCM 2012 management point error 1603. Scenario : Installing a new MP gives an error 1603 SCCM 2012 R2 Windows 2012 R2 The first thing to check is the MPSetup.log, you can see the error 1603 but you have not much information about what’s the problem really is. You have to dig deeper in the MPMsiLog.LastError to see the root cause. As you can see the error is cause by a previous version of the client being installed on the server. My environment had SCCM 2007 configured with the client push so my 2007 client was installed. I’ve removed the client using ccmsetup /uninstall and remove the MP role. Still the same error then re-adding … Read More