Hello all,
I'm using NIS 2011. For 2 of my PCs, I run my LiveUpdates at night when nobody is trying to use them (these 2 PCS are a little short on resources so are too slow to use during LiveUpdates). I schedule the LiveUpdates using the WIndows Scheduler (to run uistub.exe /lu). This works fine for 1 PC, but not for the other. The problem is that the main user on one of my PCs does NOT have a password (it is blank per her request). This appears to cause a problem I have been unable to solve.
Specifically, I can't shedule the Liveupdate to run using her credentials because blank passwords aren't allowed by the scheduler. Consequenlty I scheduled it to run using the Administrator credentials. This works fine as long as the Administrator is logged in at the time when the scheduled task runs. However, the Administrator is almost never logged in, and this presents a problem. Specifically, the sheduled LiveUpdate does not run unless the administrator is logged in.
Since the scheduler isn't seeing any error, I believe it is LiveUpdate that is failing, and not the scheduler. I also believe the problem is that the scheduler is trying to run LiveUpdate "non-interactively." I believe this is the designed behavior of the Scheduler. Specifically, if the user associated with the scheduled task is logged on, then the task is run interactively (visible in the foreground). Conversely, if the user associated with the task is not logged in, then the scheduler attempts to run the task in the background. I'm guessing that the scheduler requests that LiveUpdate (uistub.exe /lu) run in the background and LiveUpdate doesn't support running in the background. I'm not sure why this would NOT be logged as an error by the scheduler, but it appears that the scheduler sees nothing wrong. The task just doesn't run.
So I'm hoping maybe someone knows how to get LiveUpdate to run in the background. If it is possible to run LiveUpdate in the background, then I can use the Windows scheduler.
If not, maybe someone who knows more about the Windows scheduler can tell me how to work around this issue.
I'm not sure where to go from here, so any help at all would be greatly appreciated.
Thanks in advance for any help with this.