Office 2003 should not require users to have admin rights to load

[firstco_m]

Surely "the tail is wagging the dog" here! Why does every basic user require
admin rights to run a basic application such as an office program? You need
to change the software so that it is fit for purpose - we write software
applications for very sophisticated control systems that don't require the
control room operators to have to be given admin rights for them to use.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...15cef2bb8ad3&dg=microsoft.public.office.setup

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[neo [mvp outlook]]

huh? I run Microsoft Office 2003 with "User" rights every day. Working
with a standard desktop, terminal server offering user sessions... please be
descriptive about the problem. Makes it easier to give ideas on how to
correct.

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[firstco_m]

thanks for the reply. If you run an Office 2003 application as a basic user
(we have both Win2K and XP machines on our network) Windows Installer always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access to?

 

[neo [mvp outlook]]

Roaming or mandatory profiles in use?

thanks for the reply. If you run an Office 2003 application as a basic
user
(we have both Win2K and XP machines on our network) Windows Installer
always
tries to run each time. Then a dialogue box saying "Please wait while
Windows configures
Microsoft Office Professional Edition 2003" appears. This happens with
every Office application in the same session. As soon as the user is
given
local admin rights, the applications load straight away. I have searched
widely, but cannot get an answer. Perhaps there is a clue in that
Microsoft
itself says that all users must be given elevated admin rights to setup
Office 2003, and I suspect that this is because certain files are written
during load to system folders that basic users do not have write access
to?