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

Need help with incorporating Symantec Packager with Altiris pcAnywhere Plug-in

Created: 23 Jul 2012 • Updated: 31 Jul 2012 | 7 comments
This issue has been solved. See solution.

 

 

Before explanation, we are running Symantec Management Platform 7.1 SP2 with pcAnywhere 12.5.5

We are going to be converting over from VNC to pcAnywhere and I’m attempting to set it up in the same fashion except I’m running into an issue.

I found the Symantec packager, which is great, I can import my reg keys to change central server logging, setup the host files the way I want them to initially be, but I need to be able to change the caller files globally throughout the company when we need to add more users to the authentication.

I see I can use the pcAnywhere plug-in to deploy it, then I can add the ADS groups into pcAnywhere Settings -> Authentication to update the users, but deploying from the plug-in, as far as I been able to find, I can't modify the package that gets deployed.  Which means the packager which so nicely brought everything I need, isn't able to be used since I have to deploy from the console.

And I don’t only have one package, I have several packages depending on if it’s host only, remote and host only, which central server I want it logging to or which firewall settings I need.

So I am wondering how I can deploy a custom built package but still have the ability to edit the authentication from the console to update the active user/groups on all my clients that have pcAnywhere installed.

Thanks,

Tom

Comments 7 CommentsJump to latest comment

andykn101's picture

So, as long as the base Symantec Management Agent reports to the Notification Server you set up the pcAnywhere policies on I don't think it matters where the pcAnywhere pug-in has been installed from.

Try it.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

tasmith1987's picture

This was my plan.  I was going to create policies for each installer I had, then use the plug-in policy to update the credential changes when I needed to change them.

First issue I ran into was that my host file, lets say the one I made was called "My Host <date>" would be imported into my installer via symantec packager, and this install gets deployed.  First I installed the plug-in with pcAClientInstallManager.exe /iall command, which create another host file, don't want that.  The one it created was named "pcaNSHost".

So I got the idea to just name mine the same, so I created a new package with all the same settings, deployed that, but this time just install only the plug-in.  I Send and Update the Altiris agent, I see it updates, I can check the xml in c:\program files\altiris\altiris agent\client policies and see it updated, but the caller files never update with the change I made in the console.

andykn101's picture

using policy with the file you want.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

tasmith1987's picture

I've probably waited a few hours before uninstalling pcAnywhere and trying something else.  I think i'll redo it this morning and wait till tomorrow and see if it updates.

Thanks

tasmith1987's picture

pcAnywhere caller files never updated with the AD groups I added into the pcAnywhere plug-in in the console. I wonder if a better way to do this is to add X groups into my symantec packager, and as new users are hired/fired, I can just modified those groups, so the client's caller files never change.

I'll probably try this later today or tomorrow (to see when I change the group in AD that it retroactivity affects pcAnywhere)

Tom

andykn101's picture

So you could have a pcAnwhere caller Domain Local AD Group and put your Role groups (ServiceDesk operators, Deskside techs etc.) into that.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

SOLUTION
tasmith1987's picture

I tested it and this works, just created a master pcA group and added that as a caller file.  From there we can put other groups/users into that AD group. I tested it and it updates immediately when adding another user and trying to use their credentials to log into a PC.

Thanks,

Tom