B
BJM
I have a series of 2K clients on a Win 2K domain that I
have locally installed O2K Pro on. I have tried "Run All
From My computer" installations from a network server
location, CD-ROM installations locally, as well as
installations from a C: drive folder containing a copy of
the installation CD files.
Each time the results are that whenever a user logs on to
the machine under a network account and then launches an
Office app, they are asked to install additional
componants before the app launches. Sometimes cancelling
the installation request will bring up the app, sometimes
not. And since sometimes the installation path is not
available for an end user, the installation attempt fails.
On occasion, (especially with Access) the additional
componant installation is looking for files from Disk 2!
It fails (even when the original set up files are on the
local C: drive) and the application will not launch.
This, I presume, is a permissions issue. Is there a group
policy or some permission setting I can tweak (preferably
on the server since I have about 30 clients involved) that
can stop this from happening?
Thanks,
BJM
have locally installed O2K Pro on. I have tried "Run All
From My computer" installations from a network server
location, CD-ROM installations locally, as well as
installations from a C: drive folder containing a copy of
the installation CD files.
Each time the results are that whenever a user logs on to
the machine under a network account and then launches an
Office app, they are asked to install additional
componants before the app launches. Sometimes cancelling
the installation request will bring up the app, sometimes
not. And since sometimes the installation path is not
available for an end user, the installation attempt fails.
On occasion, (especially with Access) the additional
componant installation is looking for files from Disk 2!
It fails (even when the original set up files are on the
local C: drive) and the application will not launch.
This, I presume, is a permissions issue. Is there a group
policy or some permission setting I can tweak (preferably
on the server since I have about 30 clients involved) that
can stop this from happening?
Thanks,
BJM