Process Explorer now shows the total CPU utilization for multiprocess apps like Google Chrome. A pair of new monitoring tools have been added, and allow tracking of hard disk and network activity. By default, they're all crammed into Process Explorer's main toolbar, but a quick drag-and-drop gives you a full-window timeline.
Sadly, my desktop system won't be able to take advantage of one big addition to Process Explorer 14: support for more than 64 CPUs. One day...
Now, Google has made policy templates available for download which provide a measure of lockdown functionality. As you can see, after importing the .ADM files into the Windows Group Policy Editor you'll be able to manage a handful of Chrome settings via a local machine policy.
A default home page and proxy settings can be configured and Chrome Sync can be blocked, but the bulk of the options are related to background communications with Google (alternate error pages, DNS prefetch, crash reporting, suggestions, etc.). There are a few things missing right now. For example, while I can choose to disable certain plug-ins, there's no switch to disallow extension installs. I'd also like to disable Chrome's autofill feature, but it, too, is missing.
Providing this type of application control was a key step if Google had any hopes of wresting away enterprise market share from Internet Explorer. Now that it's here, it will be interesting to see if Chrome can make inroads in the workplace.