What exactly do you need help with? Are you new to using patch manager in general and what version of LDMS?
PM can be a little bit to get your arms around but in general the process is:
1) make sure the update/definitions are downloading
2) make sure the definitions for Google Chrome are viewable under Patch and Compliance->All Types->All Items
3) Consider creating a custom group like "Google Chrome Test" under Groups folder in PaC and drag and drop the latest Google Chrome definition in there
4) Right-click the "Google Chrome Test" folder and click "Repair". Check the box "Repair as Scheduled Task" and choose a Repair setting (how it will interact with the user and client PC, including rebooting). Click on the Patches Tab in the Repair Task and make sure the patch file for the definition is actually download and click the "Ok" button.
That should create a scheduled task in your "Scheduled Tasks" tab in the LDMS console. Then just drag and drop a test client with Chrome into it, right-click and run the task. If it fails, right-click the test client and select "view log file".
In many parts of Landesk Mgmt Suite there are more than one way to do something and each environment is different and that adds more variables.
Search on the topic and you'll find things Landesk terms "Best Known Methods" which is just what it sounds like- a knowledge base type doc on what some say is the best way to do something. Some of it is version specific so note that. There's also plenty to search through on discussions.
My 2c is patching is a complex topic but this is one of my favorites re patching: https://petermassa.com/?p=486
In addition to the (very good) comments above - and not directly related to your problem - please be aware that LANDesk Management Suite 9.5 has gone EOL (End Of Life) as of December 2015. We would strongly advise to upgrade to a current & supported version if possible.
Just to make you aware of the situation.
The advice above is perfectly accurate, and I tend to say that there's usually AT LEAST 3 different ways of doing 'the same thing' with LANDesk - a lot of it comes down to personal preference.
As a side note though (probably less for you and more for your boss(-es) ) - patching isn't something that should be a part time activity by and large. There's a heck of a lot to it (irrespective of how / via which tool & method things get patched). We're happy to help out with triage as needed - just to hopefully help you along that patching the corporate app stack shouldn't be something that gets 2 hours / week allocated to it as it were .
Hope that helps.
Well said Phoffman.
It's a very good point that patching and security in firms large enough to need a client management suite like LDMS really needs to more than just a box to check and 2 hrs a week assigned to it.
Happy to be of service .
I've had to have the above conversation with several companies over the years. Patching is more than just "installing stuff". There's the whole thing around resiliency / acceptance testing.
Installing stuff is actually pretty easy. You "could" (it'd be very dangerous, but one COULD do it) simply patch an environment with an approach of "automatically install every patch ever published" without bothering to test anything for instance (I've had to talk a few companies out of that). Yes, pretty much every company under the sun will (or should) test their updates - but they can only do so in a limited fashion.
And certain "big hitters" such as Java, .NET Framework updates can cause rather massive problems & take down those business critical / in-house applications that have been written 10+ years ago often enough and not really maintained much (/at all) since then.
So yeah - if you want / need someone to understand why patching is a serious business (and "detecting & installing" is only half the story) and why there's much more to it when you want/need to do it in a way that keeps a company running smoothly, feel free to make them read this.
Let us know if there's anything else you need help with.