I have not done this before, but in theory it should works. Kind of off topic but maybe using File search instead of Registry. If the registry path houses "Microsoft\Windows\CurrentVersion" the Office Version matches the "Host" Architecture which is also displaying on this report. If the registry path houses "WOW6432Node", it's running a 32-bit version of Office on a 64-bit machine. I then ran these filters against the registry on the machines. I started by creating my columns as such: You can run a report to find what Office application versions and architecture are running on your machines. I created a Report for someone else in another thread to assist in removal of Office applications but if your registry is jacked up, you may have a really rough time with the repair. You are telling me that after a successful scan in PDQ Inventory, that under "Applications" for "ProblemMachine" you are still seeing both Office 2010 and Office 2016? Something has gone terribly wrong during your uninstall/install process. It's not a digression as those registry values "must" be present to have a successful install of Office. I'm assuming I'm an idiot, its a good bet. I don't know how to access the data that the scan is returning or even if the scan is returning anything. Registry>Value>Starts With>Word.Application.16 I have created a custom report with the following value filters:
I have run the scan against the "All Computers" group. The scan checks the Registry for "Keys in HKEY_CLASSES_ROOT\Word.Application\CurVer" So I amended the Applications scan profile to include a registry scan ( I would upload a pic here but the site tells me I can only upload jpeg, gif or png and size limit is 2MB - my pic is somewhere between 124KB and 215KB and I have tried as gif, jpg or jpeg with no success, although it appears fleetingly and is then removed). HKEY_CLASSES_ROOT\Word.Application\CurVerįor an office 2016 application the value would be Word.Application.16
I found a key that might help, although because its specifically for Word maybe isn't perfect (there are equivalents for other Office apps): Stephen, that key doesn't have a value set on my 圆4 win7 office 2016 machine. Thanks Sam & Colby for the heads up on those tools
0 kommentar(er)
