04-28-2009 09:03 AM
Hello... I've seen answer ID 14245 and wonder if any progress has been made on this issue.
We've been using ACT Premium 2008 (10.0.3HF1) for quite some time now, without having this problem. However, as we are moving our laptop users to new hardware we have encountered this issue. We move their databases from their old laptop to their new, register ACT successfully on the new laptop, and send them on their way.
Then, one or more weeks later, we find that they are getting prompted to register ACT. Since this requires Windows local admin rights, which they do not have, they are unable to run ACT.
They are VPN users, and we have found that indeed launching ACT before initializing the VPN works as a workaround.
But we also have non-VPN users that experience this problem (prompted to register ACT) when they change from a hard wired network connection to a wireless network connection.
Are there any fixes that address this behavior? Let me know if you need additional information.
05-01-2009 10:32 AM
Unfortunately this is an ongoing issue with the environments you've described. At this time there are no workarounds.
05-03-2009 08:17 AM
Thanks for the confirmation, David. Does this problem exist in ACT 2009 also?
Because they don't have Windows local admin rights, and because they do not work from our office where they would have someone available to re-register ACT, when this occurs they are without ACT.
Can you think of any tricks we can do to minimize the impact of this? If the information that triggers the re-registration is stored in the registry, perhaps we could set them up with a .reg file that would overwrite whatever conditions resulted in the registration prompt. We'd probably need to open up permissions on the necessary part of the registry, but at least they would have a way to fix this themselves.