It isn't the case that the user needs to be logged in for a provisioning task to run. However, the machine must be powered on (see comments associated with this article).
Try following test: create a template that installs package 1, reboots, installs package 2. Have the target machine machine sitting there, powered on but not logged in. The template will run to completion as intended, i.e. install package 1, reboot, install package 2.
What may come as a surprise, however, is that a provisioning task always behaves like a push. No matter what the delivery method, when you "start now" the task will run now on all machines that are available now. If a machine is off-line now, you've missed it and the only way you're going to catch it is to start the task again.
There is of course the delivery method to take into account. The delivery method may require user interaction.
Ok here is the testing I have done.
Booted up a machine and completed an inventory scan. Checked in landesk console to make sure data had been sent to the server.
Rebooted computer and left at login prompt.
Deployed a Software Provisioning task, that contains 5 software applications, to the above machine after the machine had been at the login prompt for a good 5 minutes (to allow services to start up).
Left it for 2 hours and the provisioning task had not started.
Logged into machine and the provisioning task still did not start.
Re-Deployed Software Provisioning task to machine with user logged in and it installed without any issues.
So from this I have gathered that not only does a machine have to be started up for a Software Provisioning task to run, but also a user needs to be logged into the machine.
Anyone found different results? We are still only using 8.8 SP2.
Jan is exactly right in that the user does not need to be logged in for a provisioning task to work. I would suggest you open a support incident with LANDesk to see why the task isn't kicking off, but it has been tested (and used) in many environments with no user logged in.
This is a common issue of the task remaining delayed until you log in to the machine.
I am on LDMS 9.0 SP2, but figured I would add some input from what I have been seeing.
We are experiencing this when we have at least one machine in the task that is not powered on. The provision_schedule.exe.log shows that machines powered off are treated as Linux boxes, the task tries to create a directory and ends up delaying all machines in the task. There is some sort of bug with this in my opinins, my TAM is working with Engineering on this.
As for whether a user is logged on or not, that is flakey too. It waits 10 minutes to see if someone is logged on before either starting or continuing and sometimes doenst continue until another reboot and a user logs on.
Am also on LD9, SP2. A user must be logged in for provisioning to kick off.
Haven't had it work without a user being logged in.
Same here, LD 9.0 SP2. We use provisioning templates to push applications when we have more then 3 that we need to install. I am unable to get the provisioning template to run unless I login to the machine. It doesn't seem to matter what delivery method I use either. It would be nice to have it run without having to login.
At the present, with LDMS 9 SP2, if a user isn't logged in, Provisioning will wait for 10 mintues before starting the task. If someone logs in, the task will start immediately. Part of this is due to the increased isolation of session 0. If LDProvision starts before a user logs on, it (and the UI) will be isolated/stuck in session 0, so someone could log on while Provisioning is still running and not know it. This could be a real problem if someone started doing work on the machine and it suddenly rebooted on them . Also, someone trying to see if it was done could be confused by the lack of the UI. That is why the 10 minute wait is in there.
There are probably some other ways to handle this and we continue to look at ways we can handle this such that all our customers can work with the behavior and we can properly handle and operate in the new versions of Windows that have the greater session 0 isolation
What if a reboot is in the middle of the provisioning action list? Will the computer wait 10 minutes before it continues?
If you use software distribution through provisioning, you will have to wait 5 minutes (and not 10) for provisioning to begin.
You can see that in \\%computername%\c$\ldprovisioning\provision_schedule.exe.log
To avoid this problem, put a autologon_ON before software provisioning, and an autologon_OFF after.
And with a open session, the user will not try to open his own session during the process because provisioning windows is opened