Discovery and Inventory Group

Expand all | Collapse all

Unable to block google chrome using application metering policy

  • 1.  Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 09-21-2015 12:34 PM

    Hi

    I am trying to block google chrome using application metering policy but not getting success.

    I have tried chrome_exe, chrome.exe, chrome_installer.exe, to add in policy.

    There are two opiton while creating policy either you can add rule or software, i tried both way but no luck

    Also i want to block google chrome update.exe.



  • 2.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 11-02-2015 11:51 AM

    Try new version of google chrome apk this might helps you



  • 3.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 12-09-2015 01:55 PM
      |   view attached

    Hi TeleFragger

    No luck.

     

    Find attach screenshot

     

     

     

     

     

     

    Attachment(s)

    docx
    GoogleUpdateBlock_0.docx   110 KB 1 version


  • 4.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 11-24-2015 06:29 AM
      |   view attached

    Followed same pattern for Chrome Updater but no luck.

    There are number of update.exe dont know exactly which update.exe is responsible to update chrome from one version to another.

     

    180px_GoogleUpdate_0.JPG



  • 5.  RE: Unable to block google chrome using application metering policy

    Trusted Advisor
    Posted 09-23-2015 05:34 AM
    Try another executable to make sure App Metering deny is working OK.


  • 6.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 12-03-2015 03:18 PM

    Hello TeleFragger

    Thanks for detail reply, but we want to bloack GoogleUpdate.exe



  • 7.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 09-23-2015 05:51 AM

     

    Yes all other executable are working fine like Adobe Reader.



  • 8.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 11-03-2015 09:29 AM

    Hi Roman

    Operating system affected is Windows 7 and Windows 8. All the attributes are match metered file but still issue same.

    Anyway way have got solution to block update through registry and we got success.

    Thanks for all.



  • 9.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 11-18-2015 01:48 PM
      |   view attached

    Hi Fernando

    Thanks for your detail reply.

    If we see in application metering policy there are two options to add policy 1) add rule and 2) add software.

    both the ways we can create application metering policy. If we select add rule, in this case we have to provide all the required information like Definition name, file name, internal name, File version, company name etc.

    and if you select by add software bydefault it takes all the information. I think to avoid misconfiguration we have to choose add software option so that it takes all the required information of that software.

    Find attach screenshot for more understanding

    Or Is there any way after installing chrome version which we want we will delete update folder

     

    Attachment(s)

    docx
    GoogleUpdateBlock.docx   110 KB 1 version


  • 10.  RE: Unable to block google chrome using application metering policy

    Broadcom Employee
    Posted 11-03-2015 06:43 AM

    Hello vikas1101,

    Could you please clarify what Operating System is affected? I noticed that Windows Server (2003/2008) is marked as affected OS, but Application Metering Plug-in is not supported on server clients.

    Please be also aware that rule defined in Application Metering policy will block/meter executable file only in case if all rule attributes match metered file. If at least one attribute (i.e. FileVerison) does not equal FileVerison of executed file, it will not be metered or denied from running. Could you please check all attributes defined in rule really match executable file you want to block?

    Have you tried to block file only by its File name? If not, just try to create simple rule where only FileName is defined, where filename is exact name of started process..

    Thanks,
    Roman

     



  • 11.  RE: Unable to block google chrome using application metering policy

    Posted 12-15-2015 11:31 AM

    Think I know your problem...

     

    too many settings. Unfortunately you want to set the LEAST... since you filled in many of the fields App meter doesnt sit here and go This OR this OR this..

     

    it takes ALL of those and ALL must match.


    Try it as a test as how I pictured it with bare minimal... That should do it!

     

    let me know



  • 12.  RE: Unable to block google chrome using application metering policy

    Posted 12-04-2015 07:47 AM

    so then follow what I put up but for product name choose Google Update as seen here...

    GoogleUpdate.png



  • 13.  RE: Unable to block google chrome using application metering policy

    Posted 12-03-2015 10:28 AM

    Works like a charm for me...

    here...hope this helps...

    Sorry if I really went basic but it worked for me without any issue so figured I would walk through very detailed steps so maybe if it helps others too...

     

    Create a new policy and choose Rule

    Product name: Google Chrome

    1. Rule.png

     

    1. verify policy shows correct information

    2. verify your target test machine shows in list

    3. verify policy is enabled

    2. Policy_0.png

     

    Test machine

    1. Click update
    2. verify requested and changed update (as this will represent new policy came down)
    3. Verify you do have the app metering agent installed

    3. Altiris Client_0.png

     

    should be good to go and block.... I also added a message to the users... back on the options tab in the policy

    5. Policy.png

     

     

    also you can go into the altiris queue directory and find your metering information that goes to Altiris.

    Goto your policy, right click and choose properties

    Take the guid number

    go into the altiris agent\queue directory and look for the guid number

    open with a text editor 

    Policy is there and good to go....

     

    should be working

    4. File.png

     



  • 14.  RE: Unable to block google chrome using application metering policy

    Posted 11-03-2015 04:05 PM

    Hi Vikas1101

     

    First of all. how is configured your google chrome denying rule?

    You should try to block using the Google's Chrome Internal Name. I don't know what is the Google Chrome Internal name, but should be "Chrome" or "GoogleChrome". Find out this info before configure the rule.

     

    Second point is the number of items you are defining in your rule.

    Sample: A rule to block the game called "Counter-Strike".

    - Executable name = cstrike.exe

    -Version = 1.6

    If tou create a rule to block and set the executable name with "cstrike.exe" and version with "1.6", both values MUST be TRUE to the rule work and Application Metering block the game. If the user run the executable "cstrike.exe" but the version be "1.5", the game will be open without problems.

    Other good example is when your user change the executable name from "cstrike.exe" to "abc.exe" or anything different from the original name. In this case your rule will also fail.

     

    I've told you to find out the Internal Name of Google Chrome because you can block Google Chrome from different version using only this value. This value is generated when the software is compilated.

     

    Best Regards!

    Fernando Romano



  • 15.  RE: Unable to block google chrome using application metering policy

    Posted 11-23-2015 12:32 PM

    I block the Chrome installation by using the following rule:

    File Name: *_chrome_installer*.exe

    This takes care of the online installer.  No other attributes need to be named (version, manufacturer, etc.).  For the offline installer, I use this:

    File Name: ChromeStandalone*.exe

    You should be able to follow a similar patten for the Chrome updater (I have not attempted to block it with a metering policy yet).  I'd try only configuring the filename for it and then you can see how that goes.

    Hope this helps.