Client Management Suite

 View Only

  • 1.  Custom Filter Based on File Name for PC Anywhere

    Posted Feb 01, 2012 01:52 PM

    While rolling out 7.1 to our new computers we have noticed that the quick Connect shortcut and executable get installed by default on any machine receiveing PC Anywhere, which is a bit overkill for 4000 client machines. I have seen people making custom tasks or jobs to handle this and have it run every day against all machines with PC Anywhere but this proves problematic as computers start to have long history of a simple task to delete shortcuts. How would I go about creating a custom filter for machines with just this shortcut. I assume I have to use the inventory manager and start looking for it first.



  • 2.  RE: Custom Filter Based on File Name for PC Anywhere

    Trusted Advisor
    Posted Feb 01, 2012 02:32 PM

    I asked support same thing recently and didn't get a good solution other than create a managed policy to remove it without a good way to scope it to just machines that have it.  They really should build a checkbox into the console to install or not install quick connect for clients.



  • 3.  RE: Custom Filter Based on File Name for PC Anywhere

    Posted Feb 01, 2012 03:10 PM

    Create a Managed Software Delivery that uninstalls QuickConnect, and base the detection rule on a file existing at C:\Program Files\Syymantec\pcAnywhere\PCAQuickConnectDll.dll or PCAQuickConnect.exe.

    Alternatively create a script with a simple IF EXIST statement that then proceeds to perform the uninstall.



  • 4.  RE: Custom Filter Based on File Name for PC Anywhere

    Posted Feb 01, 2012 05:46 PM

    this is what I was looking into, but pretty new to 7.1 so looking how to go about this. Dumb question but I cant see where detection rules are created. I have the tast and the Managed Software but I dont see how I would go about adding this into the Managed Delivery dependencies.



  • 5.  RE: Custom Filter Based on File Name for PC Anywhere

    Trusted Advisor
    Posted Feb 03, 2012 03:36 PM

    I'm no expert - this is what I have so far 

    This is the script I have under jobs/tasks called "delete pcAQuickConnect"

     

    if exist "C:\Program Files\Symantec\pcAnywhere\PCAQuickConnect.exe" del "C:\Program Files\Symantec\pcAnywhere\PCAQuickConnect.exe"
    if exist "C:\Program Files (x86)\Symantec\pcAnywhere\PCAQuickConnect.exe" del "C:\Program Files (x86)\Symantec\pcAnywhere\PCAQuickConnect.exe"
    if exist "C:\Documents and Settings\All Users\Start Menu\Programs\Symantec pcAnywhere\.." rd /s /q "C:\Documents and Settings\All Users\Start Menu\Programs\Symantec pcAnywhere"
    if exist "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Symantec\Symantec pcAnywhere\.." rd /s /q "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Symantec\Symantec pcAnywhere"
     
    go to manage, policies, then right click on managed software delivery folder and select new managed software delivery.
     
    Click add, task, top right of that box you can search for your task name - i typed pca.  Highlight it, click ok. Then go to schedule and scope below and fill those out.  You could scope to all machines with PCAnywhere installed and run it 1x a week or something.  
     
    I'm still working on figuring out detection rules, etc but it would be good to figure out the detection rules so you don't have to scope to all machines I guess.


  • 6.  RE: Custom Filter Based on File Name for PC Anywhere

    Posted Feb 10, 2012 12:11 AM

    Detection rules can be found when editing the Software Resource.  They're located under the Rules tab, where you'll see Detection and Applicability rules.  Choose to create a new Detection rule.  Then choose Add (blue + sign) and choose the appropriate type, such as a registry or a file path detection rule.  You could use file version if pcaquickconnect.exe has a Version.  Or you could just use an exists rule -- if the file is at the folder specified, then it is detected.

    For a Command Line of type Install, it will run when the detection rule evaluates to False.

    For a Command Line of type Uninstall, it will run when the detection rule evaluates to True.

    Does this help?  I know I don't have exact clicks since I'm away from an environment at the moment.