Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SCCM installing when no user is logged on

  • Thread starter Thread starter sysad74
  • Start date Start date
  • Replies Replies 8
  • Views Views 7K

sysad74

Member
Messages
9
Reaction score
0
Points
1
Can someone explain to me how this part of User Experience is supposed to work? I just deployed an application to my test device (that I've been logged into for a few hours), with System as the installation behavior and "Only when no user is logged on" for the Logon requirement.
A few minutes later, I see the application come up on my test device and immediately starts installing.
Apparently, I don't understand exactly what "Only when no user is logged on" means in terms of SCCM. Can someone please explain it to me? Are there other settings that must be checked in order for it to only install when no one is logged on?
 
It does exactly what it say it does. It will only install if no use is detected to be logon. Did you review the logs to see exactly what is happening?
 
It does exactly what it say it does. It will only install if no use is detected to be logon. Did you review the logs to see exactly what is happening?
Looks like installing task sequence as an application does not have the same behavior. If I install one application by itself, it works fine. When I put them together in a task sequence and deploy as an application, it does not.

Logs were not helpful as there were no errors.
 
Looks like installing task sequence as an application does not have the same behavior. If I install one application by itself, it works fine. When I put them together in a task sequence and deploy as an application, it does not.

Logs were not helpful as there were no errors.
Reading the log is more than just looking for errors. Did it show a logs was logon when the install was triggered? Did the install get triggered then you logon and the install completed?
 
Reading the log is more than just looking for errors. Did it show a logs was logon when the install was triggered? Did the install get triggered then you logon and the install completed?
No, I was already logged on and had been logged in for a few hours before the deployment was created. The task sequence as an application ignores the install only when no user is logged on.
Just to test, I took another application, made it into a program and deployed it as a task sequence application and it had the same behavior. Maybe it's because it uses a silent switch in the install, I don't know. I ended up just deploying two separate applications as actual applications and not in a task sequence application.
I'm sure there's documentation somewhere on deploying task sequence as application but I couldn't find it because searches turned up everything but.
 
Well now I have another one I need to deploy and it needs to be done sequentially so I'm guessing I'll need to figure out how to get this Task Sequence as an application to properly work.

The current one I am trying to do shows an error in AppDiscovery.log-
"The Install action on AppDT "redacted" will not use managed content. The content location is not specified and is assumed to be locally available."
This happens regardless of whether or not I add the applications as "applications" "programs" or just command line into the TS. The content was all distributed but I can't add Distribution points within the TS application itself.

I see a few others have had this issue but there's no resolution been posted that I can find.
 
What is the command line of the app? Are you seeing the content download?
 
It doesn't matter what the command line of the apps are. It's all the same behavior.
Some are setup.exe, some just install.bat (where it silently installs an MSI), some just msi.
The issue seems to be that no matter what, Task Sequences deployed as applications all end up with the same error in the logs:
"will not use managed content. The content location is not specified and is assumed to be locally available."
I'm still having the same issue today. No matter what applications I'm trying to deploy, they all give me that error when trying to deploy TS as an application.
 
See this post, it's the same issue and there's no resolution on this anywhere, going on 3 years.
 

Forum statistics

Threads
7,211
Messages
28,130
Members
18,399
Latest member
dimasyandr

Trending content

Back
Top