Community
Showing results for 
Search instead for 
Do you mean 
Reply

ACT and terminal services

New Member
Posts: 2
Country: United States

ACT and terminal services

How well does ACT Premium 2009 work in a terminal services environment?
Bronze Elite Contributor
Posts: 2,548
Country: New_Zealand

Re: ACT and terminal services

As ACT! Consultants we have had somewhat of a patchy experience with installing on Terminal Server. ACT! has got better with later versions but it isn't the best fit but don't let that desuade you from installing, it certainly works. For an application to be a good fit with Terminal Server it should be designed with consideration to the environment, for instance careful attention to limit unecessary resources and services running on the Terminal Server. Attention to rights and permissions under Terminal Server is another important area. The impact of problems of an application that are not a good fit for Terminal Server are felt across the organisation, not only for those who are running the application, so well designed applications with low resource consumption are important.

 

When applications are built and tested by software companies the testing and design budget is going to focus on the intended popular install environment and in the case of ACT! that is desktop not Terminal Server, having said that, my advice is go ahead and install but closely monitor event logs and event viewer.

 

 

Graeme Leo
Xact Software - consultants and developers
Follow us on Twitter and check out our Blog


Nickel Elite Contributor
Posts: 508
Country: USA

Re: ACT and terminal services

I have installed ACT! in a terminal services environment, and it works fine, just follow the KB articles, and pay attention to the specific settings regarding this environment.

 

However, what I think Graeme is referring to is some of the "side" services, such as Network Sync, Scheduler, and the Outlook service will start for *every* TS user, regardless if they are actual ACT! users.  20 TS users = 20 Outlook.Service.exe instances running + 20 Scheduler + ..., and so on.

 

What we ended up doing is creating a startup sequence for the ACT! users where they start ACT!, start the Outlook service via an icon, which is a step or two more than most people, but they don't really know any different.  This has solved the multiple instance issues.

Richard Brust
ACT! Certified Consultant
richard@rbrDataSolutions.com
Bronze Elite Contributor
Posts: 2,548
Country: New_Zealand

Re: ACT and terminal services

Correct Richard. We find also that across a number of installation there is inconsistency in folder creation and an upgrade will be different than a new install. We have found permissions both registry and folder can affect an install which in turn can result in odd errors with MS Word and Outlook integration. Overall it is acceptable but needs to be monitored after install. Interesting idea to limit number of act.outlook.service.exe instances which to me is an example of where the appication is not a good fit for the Terminal Server environment. As other commentators have said in the past this area of email integration with Outlook needs some attention to make it more efficient.

Graeme Leo
Xact Software - consultants and developers
Follow us on Twitter and check out our Blog