Why is the target computer in a locked state? I can't help you with the alternate process, but perhaps the root cause could be addressed. Are you rebuilding live systems that people are leaving in a locked state? Are your techs leaving them in this state, or is the screensaver causing this? If you can remove the cause of the locked state either through policy or changing the user behaviour, then a work-around in the scripting may not be necessary.
Verismic Software - http://www.verismic.com
Precision Engineering for Systems Management
Check Our New Power Manager Solution
Sorry, I should have clarified, we are using Provisioning to "Chain Software" applications and reboots on existing systems as described in http://community.landesk.com/support/docs/DOC-4648
These are not new build, etc and we are not using Provisioning for any other use. It offers much for flexibility over Software Distribution.
Thanks for the reply though.
I finally got a few minutes to think about this, what happens if you use the provisioning reboot command instead of an external one?
The Provisioning reboot command does not do anything if the system is locked.
Turns out that I had a couple issues, the first about the system being locked and not being able to get it to reboot was solved by calling a batch file that contained:
Shutdown.exe /f /r
I then discovered that provisioning would not pickup again after the reboots. At first we thought the /f was killing it, but more testing showed otherwise.
In short, I built a system from an XP CD, and everything worked great.
Joined it to AD, all ok still.
Applied our custom XP Security template and that broke it.
I have not had time to narrow down what setting it is.