Forum Discussion
AlexanderM
Staff
14 years agoHello Shubhangi,
When you set the actionAfterRun parameter to saReboot, the slave computer will be rebooted after Task execution. At that, no user will be logged in automatically after the reboot. So, could you clarify your scenario:
Are you configuring the AutoLogon feature of Windows on the Slave computer from your Slave test (writing the needed Registry entries) before the Task is completed?
Or do you have one more Task (with the Automatic Logon option enabled) configured to run on the same Slave PC, and your Master test waits for the host to become available after reboot (doing verification in a loop), and then starts the next Task?
Of are you implementing some different approach?
Also, let me know what exactly happens when a test runs on the Slave computer after a reboot. If it is failing, could you post the exported Test Log here? Or can you send it to Support? This should help us better understand what is going on, and help you resolve it.
Thanks!