Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

PCAnywhere Auth

Created: 04 Jun 2013 • Updated: 19 Oct 2013 | 5 comments
This issue has been solved. See solution.

Hi all,

We are in a process of configuring our PCAnywhere settings.

What we have is two PCAnywhere accounts - one superuser, one standard.

In the same time we have configured local administrators to be super users as well.

So I assume that we should be able to login using any local admin account as well as the two PCAnywhwre logins.

In reality the PCAnywhere accounts work fine, but the local admin ones don't.

Any ideas?!

Operating Systems:

Comments 5 CommentsJump to latest comment

W007's picture

Does this help
Connection works only with local admin account

Article:TECH133354  |  Created: 2010-06-24  |  Updated: 2010-10-28  |  Article URL http://www.symantec.com/docs/TECH133354

 

Process for pcAnywhere Agent registration and application of the pcAnywhere Settings - Windows policy

 

Article:TECH164883  |  Created: 2011-07-18  |  Updated: 2011-08-29  |  Article URL http://www.symantec.com/docs/TECH164883

 

 

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

technical_specialist's picture

You can only able to access with that account which has approved and having access on pcanywhere.

Check if help

https://www-secure.symantec.com/connect/forums/role-based-access-symantec-altiris-71-sp2#comment-8220071

Klim_Belchev's picture

thanks guys - it took a while for me to go through all suggested articles but none is the issue we have...

anyways we just started using PCA auth only and dropped local admins

PeeGee's picture

The UI indicates that you can configure and use different authentication methods, as any defined accounts are remembered, when you switch the authentication type in the drop-down box.

Anyway only the CURRENTLY SELECTED authentication type in the drop-down box is being configured on the clients for valid authentication. So if you have "Local account" selected and hit save, this configuration is set as valid authentication method on clients (after next client request). If you select "AD authentication" and hit save, then clients will accept (only) AD auhentication after their next policy update.

SOLUTION
Klim_Belchev's picture

Thanks PeeGee - that's what we see as well.

I reckon the configuration interface in NS is a bit misleading (could be improved), moreover I did not come across helpfull information in the user guide...