How do you handle outdated Google Chrome on servers?

The report that showed you that you have Chrome on 70 boxes should show you the install path. If it doesn't, talk to your security team to get it added to the report. It is important to tailor the reports and build rapport with your security team. They drive a lot work. The tool has to have the directory, because if the user isn't logged in, and Chrome is active, how would they detect it. Anyway, you need the install path. Get it from the report, script it, or grind it out. But if you are going to have to login to each box and grind it out, may as well handjam it all. Once you have the install path, read on. The scalpel. * Use the setup.exe in the user profile usually under `\Users\<UserName>\AppData\Local`with the --force-uninstall switch. * Delete the \\Users\\<UserName>\\AppData\\Local\\Google\\Chrome chrome profile directories. The chainsaw * You could delete the user profile from the server. You then need to check the registry HKLM\\Software\\Google and purge the chrome entries if your OCD requires it. It will probably be fine long term depending on your lifecycle management program. Personally If the report had the install directory listed, I would identify the username by the path, then script out delprof.exe to delete the profile. But if it was a vendor / installer that did this, you may lose you install media or license keys in their download folder. We use PDQ Deploy and Inventory for this. When I had to do this, after I was talked out of the chainsaw approach, we purged the user installs using the scalpel approach, Then if the application owner/vendor/application required it, we deployed it to the server using a machine wide installer via PDQ Deploy package library. PDQ package library is updated monthly, so we run it on a schedule. We do this with some other small accessory programs as well so it adds to the business case for PDQ deploy and inventory.