Having detailed the problems on here a week or so ago that I was having with GSS 2.0 and having had no relief, I ended up regressing my vmware host to a snapshot where I had GSS 1.1 . I then installed GSS 1.1 on an entirely different server and migrated the data over. I am using this new server as my production GSS (we intended to move to it anyway) while I put back 2.01 on the original server for testing with Tier 2 or higher support.
At any rate, I have been troubleshooting my migrated tasks because the post clone, configuration step is always failing. The task contains 2 steps, 1 to clone from an imaged stored on the local hard drive and the second is to set the configuration after cloneing.
Prior to GSS 2.0 the configuration setting was accomplished by a command line argument for ghost:
-replace:gvpcg.bin=\ghregupd.reg
the ghregupd.reg file mentioned is present, however upon inspection of the args.txt file for ghost that the console transfers to the client I note the -replace line is not in the file as it used to be when I ran tasks from the old server. So I added the argument myself to the clone task under the "Advanced" button option "Additional options for Ghost command line" And now all is working fine. I even created new tasks and deleted the machine object and let it be re-inserted in to the database and had no luck. The only cure is for me to manually add a command line argument to the task that should have already been given to the client by the console in the first place.
So, here is a WTF for you all to think about.