→ Having trouble accessing our new support portal or creating a ticket? Please notify our team here

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
DSKIM
Engaged Sweeper
I need to build a report that will scan for computers that have the 32-bit (x86) version of Microsoft Office (any version) installed. I checked around and it seems like even the x64 version of Office creates folders and installs software in both Program Files and Program Files (x86), so that can't be used as a way to narrow it down.

Does anyone know of another way?
1 ACCEPTED SOLUTION
Susan_A
Lansweeper Alumni
This online thread points to a registry value that stores Office "bitness" information. You could try scanning this registry value with custom registry scanning to retrieve the information that way. (The thread refers to Office 2010 and 2013, but there's likely similar keys for other Office versions as well.)

View solution in original post

3 REPLIES 3
Argon0
Champion Sweeper
So how to build this into a report?
fjca
Champion Sweeper II
Argon0 wrote:
So how to build this into a report?


You can use mine, it's a simplified version of the "official" registry template report.
I do have some idea that if gives false positives on those cases where we have applications like Lync Basic or some runtimes installed, that create Office keys, but are not "real" Office apps.
So, handle with care...


Select Top 1000000 tsysOS.Image As icon,
tblAssets.AssetID,
tblAssets.AssetName,
tblAssets.Domain,
tblAssets.Username,
tblAssets.IPAddress,
TsysLastscan.Lasttime As LastRegistryScan,
Case
When TsysLastscan.Lasttime < GetDate() - 1 Then
'Last registry scan more than 24 hours ago.'
End As Comment,
Case
When SubQuery1.Valuename Is Not Null And SubQuery1.Valuename <> ''
Then 'Yes'
Else 'No'
End As ValuenameFound,
SubQuery1.Regkey,
SubQuery1.Valuename,
SubQuery1.Value,
tblAssets.Lastseen
From tblAssets
Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
Inner Join tsysOS On tsysOS.OScode = tblAssets.OScode
Inner Join TsysLastscan On tblAssets.AssetID = TsysLastscan.AssetID
Inner Join TsysWaittime On TsysWaittime.CFGCode = TsysLastscan.CFGcode
Left Join (Select Top 1000000 tblRegistry.AssetID,
tblRegistry.Regkey,
tblRegistry.Valuename,
tblRegistry.Value,
tblRegistry.Lastchanged
From tblRegistry
Where tblRegistry.Regkey Like '%SOFTWARE\Microsoft\Office\%') SubQuery1 On
SubQuery1.AssetID = tblAssets.AssetID
Where tblAssetCustom.State = 1 And TsysWaittime.CFGname = 'registry'
Order By tblAssets.AssetName
Susan_A
Lansweeper Alumni
This online thread points to a registry value that stores Office "bitness" information. You could try scanning this registry value with custom registry scanning to retrieve the information that way. (The thread refers to Office 2010 and 2013, but there's likely similar keys for other Office versions as well.)