GoToAssist Express problem with cloned drives

UPDATE: 11-28-11 - We found another occurrence of this problem that was not fully resolved by this solution, but running SysPrep did solve the problem.
-----

We had an ongoing problem with GoToAssist Express on two systems, an original and a clone of the original, where we couldn't get both of them back into a functional state with GoToAssist Express Customer on both systems.  These are Windows XP systems, and we didn't initially realize the cloning process had anything to do with the problem.  GoToAssist was on the original system before the cloning process, and after the cloning process, only the cloned system was recognized by GTA Express support console.

CAUTION: The following discusses modifying the registry.  Do not attempt unless you have a backup and/or know what you are doing.  Incorrectly modifying the registry can cause irreparable damage to the OS to the point where it may no longer be able to start.

We tried uninstalling GTA from both systems and re-installing, but that didn't work.  Whichever system was the last system to have GTA installed was the only one that would be recognized as a GTA client.  Even after uninstalling the app and removing all registry entries with GoToAssist, still no joy.

After several calls to Citrix tech support for GoToAssist, with no one seeming to know how to resolve it, we finally ran into one technician that said "It can't be done.  This is a known issue and many people have complained, so we are considering a way to fix this."  This sounded fishy, especially because I did it once before, but I didn't think much about documenting what I did at the time because my resolution at the time was quick and worked.  I moved on.

Now it came up again, but it had been too long to remember exactly what I did, and we finally found the resolution.  We were two-thirds of the way there.  Uninstall GTA, remove all registry entries with "GoToAssist" *AND* "g2ax" (where it obviously related to GoToAssist, being careful not remove anything that didn't also have some reference to GTA.)

Voila!  Success!

Image Magick error "missing an image filename" SOLVED

If you've ever experienced the error in Image Magick that states "missing an image filename", it may or may not state also that it can't find a file.  In my case, I found the solution.  There are many people online that tried various things, including running the Image Magick configure command, modifying the delegates.xml file, etc., but none of those worked for me.  I have two different systems I could compare.  One worked and the other did not.  After retracing my installation steps, I realized the one thing I did differently was on the system that did not work.  I installed GhostScript, but then realized I didn't have it in the path I wanted it, so I renamed the path and changed the GS_PROG environment variable, but I didn't realize that there were registry entries that did matter to Image Magick to identify the location of GhostScript.  This would also apply in situations where the GhostScript files are manually copied to the system.  The environment variable GS_PROG is not sufficient to be correctly pointed at the GhostScript folder.   (I haven't investigated when these registry entries get created yet, but they are apparently necessary for Image Magick to properly find GhostScript.)

In my case, I originally installed GS in the folder "C:\Program Files\gs\gs9", but I wanted it in the folder "C:\Program Files\GhostScript\gs9", which is how I discovered this solution.  I've verified that this solution works by copying the installed GhostScript folder to another computer, set the GS_PROG environment variable, and applied these registry entries.  The registry entries that resolved this are:

[HKEY_LOCAL_MACHINE\SOFTWARE\Artifex\GPL Ghostscript\9.02]
@="C:\\Program Files\\GhostScript\\gs9"

[HKEY_LOCAL_MACHINE\SOFTWARE\GPL Ghostscript\9.02]
"GS_DLL"="C:\\Program Files\\GhostScript\\gs9\\bin\\gsdll32.dll"
"GS_LIB"="C:\\Program Files\\GhostScript\\gs9\\bin;C:\\Program Files\\GhostScript\\gs9\\lib;C:\\Program Files\\GhostScript\\gs9\\fonts"


There is a registry section for uninstalling GhostScript as well that had a reference to the GS folder:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\GPL Ghostscript 9.02]

...includes a line that needed to be modified.  The entire section is:


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\GPL Ghostscript 9.02]
"DisplayName"="GPL Ghostscript"
"UninstallString"="\"C:\\Program Files\\GhostScript\\gs9\\uninstgs.exe\""
"Publisher"="Artifex Software Inc."
"HelpLink"="http://www.ghostscript.com/"
"URLInfoAbout"="http://www.ghostscript.com/"
"DisplayVersion"="9.02"
"NoModify"=dword:00000001
"NoRepair"=dword:00000001