PENDINGTask Sequence to install application at Log Off

[macquazi]

Hi,

I have created a task sequence to install an application at log off which seems to works fine. However for some devices I've noticed:

- It takes a couple of reboots before the task sequence runs
- The TS does not run at log off but instead at Log on for some devices
- When monitoring the deployment status in MECM, several devices are stuck in "Progress" although they have actually completed the task sequence and installed successfully.

Are the above behaviours normal? The main one which causes a problem is the Deployment status, where it is not reporting back correctly. Is there anything I need to do to refresh. I have ran an App deployment evaluation cycle on all devices in "Progress" using RCT, hoping the status would refresh but it hasn't made a difference.

Thanks,

Mac

[supriyo91]

Hi,

I have created a task sequence to install an application at log off which seems to works fine. However for some devices I've noticed:

- It takes a couple of reboots before the task sequence runs
- The TS does not run at log off but instead at Log on for some devices
- When monitoring the deployment status in MECM, several devices are stuck in "Progress" although they have actually completed the task sequence and installed successfully.

Are the above behaviours normal? The main one which causes a problem is the Deployment status, where it is not reporting back correctly. Is there anything I need to do to refresh. I have ran an App deployment evaluation cycle on all devices in "Progress" using RCT, hoping the status would refresh but it hasn't made a difference.

Thanks,

Mac

Just implement it through GPO.

[Garth]

Running anything at logoff is problematic at best. Why because if you reboot, you are logging off then a reboot or shutdown happens. Why not use the install when there is no users, instead?

[macquazi]

Running anything at logoff is problematic at best. Why because if you reboot, you are logging off then a reboot or shutdown happens. Why not use the install when there is no users, instead?

Thanks Garth, yes I was thinking to run when no users are logged on - but the SCCM package runs a powershell script which has a portion of it that looks for the logged on user and creates a folder in %appdata% as a post installation task.

Can you suggest any other method to run at log off, other than a task sequence please?

[Garth]

Thanks Garth, yes I was thinking to run when no users are logged on - but the SCCM package runs a powershell script which has a portion of it that looks for the logged on user and creates a folder in %appdata% as a post installation task.

Can you suggest any other method to run at log off, other than a task sequence please?

Create two different installed and make the user one dependent on the other one.