gigkerop.blogg.se

1. #LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC HOW TO#
2. #LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC UPDATE#
3. #LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC PROFESSIONAL#
4. #LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC WINDOWS#

It works well, but I am not certain if it was updated to detect Office 2010.

In addition, there is an Office inventory tool that can be downloaded. You can take that approach if you do not have Configuration Manager installed. The WMI classes work very well, and retrieve their information from the registry. Microsoft Configuration Manager creates custom WMI classes that can be used to query for Office version information. Frequently such a broad stroke is sufficient. You can also query file versions but that will require you to check for every possible combination of service pack and hotfix as the file versions change at service pack levels.įrom a most basic stance, you can decide that if a computer has Microsoft Excel version 12 installed, it is running Office 12. However, you have to allow for all different variations of the configuration. You can query the registry for Office keys. Come back later, and retrieve the results.

#LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC WINDOWS#

However, the ability to run it as a background job in Windows PowerShell reduces this really well.

#LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC UPDATE#

For example, are you trying a software inventory, trying to detect update status, seeking information to determine upgrade costs, searching for machines that were possibly missed during an upgrade cycle, or for computers that do not have enough horsepower to stand an upgrade to the most recent edition of Office.Īs you mentioned, using the WMI class, Win32_Product can be a bit slow. One way to do this is to determine why the information is to be collected. Ultimately, one must describe what is meant by “what version of Office” is installed.

#LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC PROFESSIONAL#

In addition, problems can occur as to what version of Office is installed because of Professional version, Ultimate edition, Student edition or one of the other editions of Office that consist of different suites of applications. So a mix and match situation could very well exist that would make extrapolating what version of Office is actually installed on the machine problematic. In addition, as you pointed out, it may be that one has Office 2010 installed, has Word 2003 installed as well, and maybe even Outlook 2007. You can detect the “version of Office” by querying the product version of Word / Excel / PowerPoint / Outlook, and so on Unfortunately, I cannot find a global GUID to represent the version of office that is installed. I wrote a blog in 2009 that is on the same theme using Windows PowerShell. The blog post you mentioned was written in 2005 using VBScript. I do not really want to loop through all the available Office products. Nevertheless, how do I use this same technique to query the version of Office? In our organization, we have a mix of different versions of Office, some of which even have different versions of Word on the same machine (for backward testing of some old macros). Hey, Scripting Guy! With reference to one of your previous blog posts, “How Can I Determine Which Version of Word is Installed on a Computer?” I liked how your approach to determine the version of Word is much faster than querying Win32_Product.

#LANGUAGE ACCESSORY PACK FOR MS WORD 2011 FOR MAC HOW TO#

Summary: Learn how to use Windows PowerShell to detect your version of Microsoft Office.