What version of Office do I have?

Prior to Microsoft Office 2007, finding out what version you were running was very straightforward. You clicked on the “Help” menu bar item and then on “About”. Generally you would do this to find out not just what version you were running (i.e. Office 2003) but what Service Packs had been installed (e.g. Service Pack 1).

Recently I needed to quickly find out whether a customer’s Office 2007 installation had been upgraded with Service Pack 1. I was stumped for a short while! Where on earth was one to find the equivalent?

To save you the hassle, here’s the answer…

Click on the new “Office Button”, choose the relevant “Options” button at the very bottom of the menu, e.g. if you’re in Excel it will be “Excel Options”. Then click “Resources”, and finally “About” – in fact you can probably see all you need to know at the bottom of the “Resources” screen without having to click “About”.

I’m sure they could have buried it a little more if they really put their minds to it!

Comments

Michael said…

Thank you so much! Saved me a lot of searching.

23 March 2011 at 22:28

Chuck said…

Thank you! I can't believe the designers buried this 4 levels deep.

24 March 2011 at 12:57

Bingo Rose said…

Thank you for this post. Some things are just buried too deep.

16 November 2012 at 22:35

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted. Very often the fix is to run SCANPST.EXE on the offending PST/OST file. However, every time I go to do this I forget where the two executable files are. Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more... but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box: \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in: UPDATE tbSingletonData SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition. However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition. This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell: reagentc /disable If you get the error message "REAGENTC.EXE: Operati...

Artifact Weblog

Search This Blog