System Center

How to move the SMS_[SITESERVER-FQDN] folder and/or smssqlbkup.log file of the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component and how to fix the latter when it’s broken (SCCM 2012 R2)?

Posted on Updated on

Attention: this blog post has been written based on SCCM 2012 R2, more precisely with SP1. There is a small chance that this article is not completely true for SCCM 2012 R2 without SP1 or even that the content lies quite far from reality in SCCM 2012 non-R2. What is certainly true is this post doesn’t apply for older SCCM versions (2007 and older) for at least a decent amount.

This blog post’s goal is twofold:

  • Describing how to change the location of the SMS_[SITESERVER-FQDN] folder and/or smssqlbkup.log file of the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component. Please read the paragraph “How to change the location of the SMS_[SITESERVER-FQDN] folder and/or the smssqlbkup.log file?” to deep-dive into this one.
  • Describing how the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component may be broken, what happens then and how to fix it, even if you didn’t try to change the SMS_[SITESERVER-FQDN] folder and/or the smssqlbkup.log file. See the paragraph “What if the SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component is broken?” hereunder for that part.

In both cases it may be useful to start with the introduction paragraph “First some background information on SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] component…” below. In the case of fixing a broken component (the 2nd goal of this post) I also think it’s worth reading the part about changing the location of the SMS_[SITESERVER-FQDN] folder and the smssqlbkup.log file, because it contains some in-depth details which may be useful to understand how to fix a broken SMS_SITE_SQL_BACKUP_[SITESERVER-FQDN] SCCM component.
Read the rest of this entry »

Advertisements

Yet another DCOM error related to SCCM

Posted on Updated on

(or a few things you need to know about DCOM, DCM and SCCM)

On some systems the following error appears in the System event log:

Event ID: 10016

Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

{B07C1D3E-637B-4C71-BC2F-06665F376A59}

and APPID

{AD65A69D-3831-40D7-9629-9B0B50A93843}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Source: DistributedCOM

Level: Error

User: SYSTEM

Computer: YOUR_SYSTEM

Logged: DATE_AND_TIME

Task Category: None

Keywords: Classic

OpCode: Info Read the rest of this entry »

Another DCOM error related to SCCM

Posted on Updated on

(or learn some connections between DCOM, SENS and SCCM)

On some systems the following error appears in the System event log:

Event ID: 10016

Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

{1CCB96F4-B8AD-4B43-9688-B273F58E0910}

and APPID

{AD65A69D-3831-40D7-9629-9B0B50A93843}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Source: DistributedCOM

Level: Error

User: SYSTEM

Computer: YOUR_SYSTEM

Logged: DATE_AND_TIME

Task Category: None

Keywords: Classic

OpCode: Info Read the rest of this entry »

DCOM error related to SCCM

Posted on Updated on

(or what you need to know about DCOM and SCCM)

On some systems the following error appears in the System event log:

Event ID: 10016

Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

{05D1D5D8-18D1-4B83-85ED-A0F99D53C885}

and APPID

{AD65A69D-3831-40D7-9629-9B0B50A93843}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Source: DistributedCOM

Level: Error

User: SYSTEM

Computer: YOUR_SYSTEM

Logged: DATE_AND_TIME

Task Category: None

Keywords: Classic

OpCode: Info Read the rest of this entry »

DCOM error related to NAP

Posted on Updated on

(or what you need to know about DCOM, NAP and SCCM)

On some systems the following error appears in the System event log at boot time:

Event ID: 10016

Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

{24FF4FDC-1D9F-4195-8C79-0DA39248FF48}

and APPID

{B292921D-AF50-400C-9B75-0C57A7F29BA1}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Source: DistributedCOM

Level: Error

User: SYSTEM

Computer: YOUR_SYSTEM

Logged: DATE_AND_TIME

Task Category: None

Keywords: Classic

OpCode: Info Read the rest of this entry »

Download of an update via SCCM fails with "invalid certificate signature"

Posted on Updated on

When you use the Software Updates features of System Center Configuration Manager (SCCM) and you download one or more updates to a deployment package, it’s possible one or more of those updates failed to download with the error message “Invalid certificate signature”. This means the signature (which is based on a certificate, hence the name “certificate signature”) of the download is invalid.

This is possible because the signature itself is incorrect because the creator or publisher of the update has signed the update incorrectly. This way the source of the update (the creator/publisher) cannot be verified for sure.
Another possibility is the fact that something has changed to the actual content of the update without adapting the signature. This means the integrity of the update is broken, because perhaps some malicious user has changed something to the update!
A third possibility is perhaps the least technical one and perhaps the most forgotten one: something went wrong when downloading the file or storing the file. Perhaps the file stored at MS got just corrupt, or could not be downloaded completely, or got corrupt when stored locally. Causes of these are multiple: bugs in software, hardware problems,… So getting this error message (“”) doesn’t per se means the presence of a virus or a hacker. Read the rest of this entry »