Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Reply
New Member
klong
Posts: 2
Country: United States
Message 1 of 3 (1,553 Views)

Must re-register ACT when using a different network interface (wireless or VPN)

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.

 

Thanks... Ken

 

Ken Long
ACT 2008
Please use plain text.
Moderator
dlunceford
Posts: 4,373
Country: USA
Message 2 of 3 (1,527 Views)

Re: Must re-register ACT when using a different network interface (wireless or VPN)

Hello Ken,

 

Unfortunately this is an ongoing issue with the environments you've described.  At this time there are no workarounds.

Please use plain text.
New Member
klong
Posts: 2
Country: United States
Message 3 of 3 (1,517 Views)

Re: Must re-register ACT when using a different network interface (wireless or VPN)

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.

 

Thanks... Ken

Ken Long
ACT 2008
Please use plain text.