| || |
We are using Powerquest Drive Image Pro for getting clean images.
What we do is from one PC (Server) steer the tests, on the client machine
and let it reboot, restore an image, test, reboot, restore,... OK everything
Now are problem, we purchased Silk Realizer and want to steer everything
from Realizer, but we need 2 machines to test on 1.
Because we have the Realizer server which controls the activator/agents but
if we want to reboot that machine, the activator/agent goes down and
Releaser thinks that it failed.
So the intermediate solution would be to have 1 Realizer server and then per
client computer have a computer where the activator/agent is on so that the
real test computer can be rebooted...RIGHT?
How can we create a client that can reboot with the agent on it without
having to have a 'supervisor pc' that maintains a connection with Releaser?
I use the remoterebootwait function and I have read a few articles already
on the forum that are interesting.
Can this be done:
Run SilkTest on a machine, run the script and let it reboot, and then
resume where the script last stopped all on 1 machine?
Howabout the following setup:
Realizer Controls a SilkTest agent(controller) That controller runs another Agent which is rebooted at will (when you do the image)
That way Realizer is always connected to the SilkTest controller, and does not care about the other agent...
Search the QADownloads.com directory for a RemoteReboot inc file that explains how to do this successfully!
I'm very interested in your use of Drive Image Pro. I tried using it in the same way but I couldn't get around needing a boot floppy and program floppy in order to load down a clean image. I gave up on it even though I think it works great. I'm currently trying to find some time to play around with an Altiris product.