5 Days later, 100 views but no reply... Guess the question is too delicious.. We have not really solved the issue. so If anyone feels like he has a suggestion.. Please write :-D
Ask support if Bomgar has a VDI mode, a few products such as McAfee have this, where at install time you specify an argument to the installer "/VDI". Then if the machine already exists in the application DB it won't create a new entry but just use the existing instead.
If Bomgar doesn't have that feature then an alternative: You could enable the ability to view the linked clone console in vSphere via the Horizon GPO's.
Thanks for your answer. Unfortunately this is the solution form Bomgar Support. the Bomgar Client is registring himself at the installation and there is no way to install and wait with the registration (somehow a Security reason)..
Total respect on trying to tackle this difficult issue. I love Bomgar as well.
Here are a few thoughts as this is a very unique challenge.
1. Use a flag file that gets created after the postsyncscript that will skip over the install if it exists on refresh. Cons: Can't think of one at the moment but its been a LOOOONNGGG Day .
2. Set pool to delete on logoff and configure pool to not re-use computer names (Note that this is explained well in pool config, the computer account must be present in the target OU for it to skip. Which means you may have to setup a post logoff script that adds said computer account to ensure it is not reused.) Cons: Fairly convoluted, eventual Computer Account cleanup, and extra I/O for recompose vs refresh.