Client Management Suite

There are 2 upgrade policies now.  I get that 'Host only' should be fine for my clients.  Do our technicians need the other more general "pcAnywhere Plug-in for Windows - Install" even if they don't want to use the Quick Connect app and instead will only connect through the CMS console?  If technican has host only they seem to get caught in an needing an install loop when they try to connect.

If I'm correct and techs and non techs need separate installs (and upgrades moving forward), anyone have smart ideas for scoping this and upgrades down the line?  

I found these filters which will be helpful post install
https://www-secure.symantec.com/connect/forums/filter-pcanywhere-host-only-and-quickconnect

Fot the pcanywhere connection both side computer is required the pca. However you can install the full package or host only. From the admin system you need to install the full package.

I guess the question is moving forward how to best keep client and technician agents upgraded.  It seems like the default policies are scoped to anyone who has either installed so if you enable either host only or full upgrade, all clients would get that.

Guess we'll have to manually create a static filter of technicians, scope the 'full' upgrade to them, and a dynamic filter of everyone else, who gets the host only install?

We have found that if our technicians PCs also have the SMP Agent installed on them, they cannot use PCA unless their PCs are configured to used the "pcAnywhere Plug-in for Windows - Install" (full install) policy.  If they have the "Host Only" policy, they cannot connect.  I seem to recall it throws up a lot of errors relating to missing PCA packages.  So we now use the "Host Only" policy for non technical staff and the "full install" policy for staff that may need to use PCA from the SMP console.

@Chrismcevoy72 - yes that's what we ended up doing too.  I had to do an uninstall of host only, then full install for techs. Then I scoped the upgrade policies individually.