How To Check Version Level for Office X for Mac

K

kat

I did a get info to see if I had the most recent version update of
Office X for Mac: I do recall doing only one update since I bought the
software and wanted to see if I had inadvertantly *missed* any, since
I dont necessarily receive notification of updates. Would love to but
I don't seem to get them all.

Anyhoo, I highlighted Office X icon; did GET INFO and got *no* version
number, so I opened it up and did a GET INFO on WordX; got Version
10.1.1; am I correct in assuming this version number also indicates
overall, the version of Office X I have?

Second question: when I do the update, in the sequence I must, do I
need to remove anything of the old software first or last? Or does the
update activity take careof all that automatically?
Thanks so much!
Kat
 
J

JE McGimpsey

I did a get info to see if I had the most recent version update of
Office X for Mac: I do recall doing only one update since I bought the
software and wanted to see if I had inadvertantly *missed* any, since
I dont necessarily receive notification of updates. Would love to but
I don't seem to get them all.

Anyhoo, I highlighted Office X icon; did GET INFO and got *no* version
number, so I opened it up and did a GET INFO on WordX; got Version
10.1.1; am I correct in assuming this version number also indicates
overall, the version of Office X I have?

Second question: when I do the update, in the sequence I must, do I
need to remove anything of the old software first or last? Or does the
update activity take careof all that automatically?
Thanks so much!
Kat

Take a look here:

http://www.mcgimpsey.com/macoffice/office/vxversions.html
 
K

kat

JE McGimpsey said:

That looks good; I sure wish I had that last line in there about
"version" within *my* Office X get info box; but alas, I don't; which
is why I checked the individual part of the program; ie: Word, and did
a get info; now *that* did have a version number in it; so my question
still stands; is this version going to reflect the overall version
level of Office X? and if I do an update, does it automatically take
care of any extraneous files or do I have to trash anything?
-Kat
 
D

Dayo Mitchell

Hi Kat,

kat said:
That looks good; I sure wish I had that last line in there about
"version" within *my* Office X get info box; but alas, I don't; which
is why I checked the individual part of the program; ie: Word, and did
a get info; now *that* did have a version number in it; so my question
still stands; is this version going to reflect the overall version
level of Office X?

Did you read the entire page? It answers this question.
and if I do an update, does it automatically take
care of any extraneous files or do I have to trash anything?
-Kat
The page is very clear statement of everything you need to do to update.
You don't need to trash anything.

DM
 
J

JE McGimpsey

That looks good; I sure wish I had that last line in there about
"version" within *my* Office X get info box; but alas, I don't; which
is why I checked the individual part of the program; ie: Word, and did
a get info; now *that* did have a version number in it; so my question
still stands; is this version going to reflect the overall version
level of Office X? and if I do an update, does it automatically take
care of any extraneous files or do I have to trash anything?
-Kat

Read the page thoroughly - you have to choose the Microsoft Component
Plug-in, not the Office X folder (folders never have Version numbers).
If your Microsoft Component Plugin doesn't have the Version property,
then it's possible that something is wrong with OSX - IIRC, every
version of Office shipped has the MCP version listed (unfortunately, I
can't check it right now).
 
A

Adam Wuellner

JE said:

At the bottom of your page you recommend running repair permissions
before and after using the updaters. I was under the impression that
Apple's utility only checked and fixed permissions of system files and
apps that Apple distributes (e.g. the iApps). I believe that I have
verified this in past attempts at using the utility, but I cannot offer
any evidence... Am I suffering from a misunderstanding?
I have gone the route of using chmod to give all users write access to
the entire Office folder heirarchy, as suggested by a MS kb article, so
that non-admins may use the program. Still, some wierdness happens,
like temp files popping up on the Desktop during saves (they disappear
when the save is complete, but I never noticed this before I switched
all the users from local admin accounts to network-homed 'normal' users).
Is there a best way to install Office for non-admins using the machine?
 
C

Corentin Cras-Méneur [MVP]

Adam Wuellner said:
At the bottom of your page you recommend running repair permissions
before and after using the updaters. I was under the impression that
Apple's utility only checked and fixed permissions of system files and
apps that Apple distributes (e.g. the iApps).

DiskUtility checks permissions for everything installed through a .pkg.
Apps, files and folders. Repairing permissions might fix a permission
issue of the parent folder of the Office folder which could be
drastically important to the Office apps.
You might also haev probelms accessing files and preferneces which might
be controlled by the Bill Of Material (BOM) of MacOS X.


Fixing permissions before updating is usefull to make sure the updater
will not have a permission issue installing, and afterwards, it helps
making sure everything is in order since some installers mess up
permissions in the process.
I believe that I have
verified this in past attempts at using the utility, but I cannot offer
any evidence... Am I suffering from a misunderstanding?

Believe me: the process repairs permissions on many key folders as well
:))
I have gone the route of using chmod to give all users write access to
the entire Office folder heirarchy, as suggested by a MS kb article, so
that non-admins may use the program.

That is a workaround that's pretty usefull especially when the
application has been installed under the root account (BIG mistake).
Since the app is not installed through a .pkg and not registered in the
BOM, it never gets fixed by itself when you repair permissions.
Still, some wierdness happens,

Yeah. It usually helps, but it's not perfect. You'd probably be better
of uninstalling the whole thing through the uninstaller (backing up the
custom settings, templates and dictionaries first) and reinstalling
from scratch.

Corentin
 
A

Adam Wuellner

Corentin said:
DiskUtility checks permissions for everything installed through a .pkg. <snip>

Thanks for the info, Corentin. This all makes sense.

Oddly, the 'weiredness' I alluded to happened even with a fresh install
from a recent Office CD (using a local admin account, not Root). Things
are working ok at the moment, though if I experience problems in the
future I'll come back with more specific info for help.
 
C

Corentin Cras-Méneur [MVP]

Adam Wuellner said:
Thanks for the info, Corentin. This all makes sense.


I'm glad it clarified the situation for you Adam,
Oddly, the 'weiredness' I alluded to happened even with a fresh install
from a recent Office CD (using a local admin account, not Root).

Weird... As far as the temp files go, I don;t know who might be
responsible for that. It could as well be a problem in the Finder
showing up files that should be invisible - I really don't know,

Things
are working ok at the moment, though if I experience problems in the
future I'll come back with more specific info for help.


Sure. I'll do my best to help (or someone else will - I dont; doubt it
:))) ).


Corentin
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top