Install problem non priv users admins fine

L

Linda P

I am trying to install Office 2003 standard on a Windows XP SP2 pc to be
ghosted for multiple users.
Using a volume licensing original CD with volume licensing key. I install
using the custom install advanced options to install all options from
computer (for word, excel, powerpoint, outlook)

Installs and works fine for admin users, WORD & EXCEL open immediately for
these users NO delay whatsoever.

Each and every time a power user tries to run, takes 1 minute to configure,
but opens, takes a while to configure to save as well for both WORD & EXCEL.

Tried installing many ways from setup with and without /allusers options.

Questions..... is the MSOCACHE folder supposed to have rights to all users
(read at least?) mine only has admins and system, altho changing this to
everyone didnt appear to change anything. Should I be using the
LISTOOL.exe? and if so, I thought this was what the MSO Cache was for.

Please help... my frustration is clouding my debugging skills...
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
G

Gerry Hickman

Hi,

Does this only happen the FIRST EVER time the user tries to use Office?
If so, I have also noticed this issue with Office 2003. The first user
who runs it (Admin or not) gets a progress bar followed by being
prompted for their full name and initials.

I found that once it's been done once, it's not been an issue since.

In general, Office has been designed to run perfectly with User rights
since Office 2000.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 
L

LindaP

It ran every time, that was the problem. At this point tho I have assumed
tho that something got corrupted in my image build and I rebuilt from
scratch... Windows xp & O2K3 & all updates and then networking and other
software components, checking all along the way, but thankfully the problem
did not reappear. Thank you anyway for your time and response.
 

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