Jump to content


Sanchez

How Are Automatically and Manually Triggered Deployments Different?

Recommended Posts

Hi.

I have an application which has a "required" deployment. If I leave it to install by itself, it always fails. But if I log-on to one of the target computers, open Software Center, go into the deployment and click "Install", it always works.

So what I'm wondering is: when SCCM automatically triggers the deployment, how is that different to triggering it from Software Center? Why would one work, but not the other?

I suspect the problem is to do with the executable itslelf, but understanding the mechanics of how the two scenarios differ, could help me test and troubleshoot the issue.

I hope someone can shed some light!

Thanks.

Share this post


Link to post
Share on other sites

the difference (based on what you said) is that one of those two installations may have been in user context, as in the user clicked and ran the installer, so is your software dependent on a user being logged on ?

Share this post


Link to post
Share on other sites

Thanks for your reply.

There's nothing documented, to say that the application requires a user to be logged-on, but I thought SCCM always used the system account, anyway. In both scenarios, the installer's temporary files and logs appear in C:\Windows\Temp, as opposed to the user's %Temp% folder, which is the bahaviour of the system account. Either way, I always test my deployments using PSExec to run the installer in the system context, and that always works, with this application.

Also, the installation fails whether a user is logged-on or not, I'm afraid. So I don't know where that leaves us.

 

Thanks.

Share this post


Link to post
Share on other sites

ok well if you can zip up all logs starting with app*.log in your c:\windows\ccm\logs folder and attach them here i can take a look

Share this post


Link to post
Share on other sites

Thank you.

Personally, I can't see anything of note in those logs. The only relevant clue is in Windows application logs, which record the installer's executable crashing:

image.png.5997132d2554a73d9f870fd04d9dc3db.png

Exception code 0xc0000005 is a memory violation, and the exit code in AppEnforce (3221225477) seems to mean the same thing. I'll speak to the developers, but it's just strange how this only happens when triggered automatically.

All these logs are from a VM with Windows 10 1909, and no software installed. The only antivirus is Windows Defender, which I disabled by local Group Policy.

AppLogs.zip

Share this post


Link to post
Share on other sites
On 9/18/2020 at 8:50 PM, anyweb said:

the difference (based on what you said) is that one of those two installations may have been in user context, as in the user clicked and ran the installer, so is your software dependent on a user being logged on ?

Agree with this view, system computer account installation and user installation of some software will cause installation errors

Share this post


Link to post
Share on other sites

Thanks, radish.

I am pretty sure that both methods (automatically-triggered and via Software Center) use the system account, but if anybody knows different, I'd like to hear it.

Understanding the exact difference between the two will help troubleshoot and explain it to the developer.

 

Thanks.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...