Hi, Here is the situation. It has come down from 'the powers that be' that we are to implement GPO's to manage software, particularly MS Office 2000. To do this we will need to install 2000 server with AD. Currently we have setup a test domain,using the existing SAM to produce an equivilent environment. Our test workstations are Win2k Pro. We have copied the Office 2000 cd to a network share and then created a GPO, using the data1.mis file. When this is assigned to the workstation, the application is installed perfectly and office runs with no problems.
Here is the 'rub'. Because of licensing, we do not want to install from the data1.msi file. We need to create a custom MSI file. Therefore we are using Wininstall to create the custom MSI package. This proceds fine and the new package is created in the MS Office network share. (NOTE: we have tested by placing in a different network share) When the GPO is created with this new package, it is assigned to the computer and it installs with no problems, (event viewer says package installs) Now, when we attempt to run Winword.exe or Excel.exe, we get this message.....
"This application must be installed to run. Please run setup from thelocation where youoriginally installed the application."
We have tried multiple ways to install, multiple office configurations, and different computer / server settings. This problems happens every time. In our research I have checked the Knowledge Base and found articles 224095, 233529, 238387. But these articles refer to Win9x and we are using Win2k Pro.
Has anyone encountered this and found a solution? Thanks.
Michael R.
This conversation is currently closed to new comments.
We have found creating MSI's to be somewhat of a "black art". We didn't have much luck with WinInstall LE (comes with 2000). We purchased Wise installer and found it ran better in our situation. There is a switch somewhere which tells the install torun on the machine, then run for each user who logs in. Unfortunately I am at home so can't pull it out. Post a comment if you still need it and I'll look it up on Monday for you. hopefully somebody else will know it and tell you here first. Have a good think before you commit to this. We have found it difficult when you need a patch or SP. The other way is a central install using the administartion kit of Office. Then updates look much easier (haven't tried it though).
I know this is not what you asked, but I'd like to share my experience with you as an option. I also had a problem deploying office via group policy and .msi Finally, I decided to just include the full install of office on all staff PC's with ghost. On the box I set up the image on. I do a full install through custom setup selecting all options, because I have found problems with things like trying to add clipart etc. later. By installing office on the ghost PC using a shared network drivewith data1.msi and data2.msi, adding service packs and patches I have been vitually trouble free. Since it was installed on the imaged PC with the shared drive, users are never prompted to insert a CD or product ID#. Users click right through the initial preparing to install screens on each module - no problem
TrackHappy, You are right, when you say that it is somewhat of a "black art". We have one test box which the Office install will only apply to the currently logged on user. Then on a different box, it will apply to all users. Something else we noted, when using WinInstall, it does NOT copy the 'All Users' profile. This makes me wonder what else it is not copying.
About that Switch for telling the install to run on the machine for All users, please let me know where this is located.To ANY ONE else who is reading this question. Please post any helpful hints, suggestions, problems encountered, or other useful comments. We are having all kinds of issues and problems to get this to work on our network. We still have some time, but there is a push to get the project moving. Any help would be greatly appreciated.
ewgny@hotmail.com Thanks for your comment. What you suggested will not apply to our situation. We have to use existing boxes and new ones are very few. Therefore, doing a Ghost would not be practical. Thanks very much for the info, as we will need to be considering patches and service packs in our 'roll out'
Any One else with input will be greatly appreciated.
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Office 2000 Install via GPO
Here is the situation. It has come down from 'the powers that be' that we
are to implement GPO's to manage software, particularly MS Office 2000. To
do this we will need to install 2000 server with AD. Currently we have
setup a test domain,using the existing SAM to produce an equivilent
environment. Our test workstations are Win2k Pro. We have copied the
Office 2000 cd to a network share and then created a GPO, using the
data1.mis file. When this is assigned to the workstation, the application
is installed perfectly and office runs with no problems.
Here is the 'rub'. Because of licensing, we do not want to install from the
data1.msi file. We need to create a custom MSI file. Therefore we are
using Wininstall to create the custom MSI package. This proceds fine and
the new package is created in the MS Office network share. (NOTE: we have
tested by placing in a different network share) When the GPO is created
with this new package, it is assigned to the computer and it installs with
no problems, (event viewer says package installs) Now, when we attempt to
run Winword.exe or Excel.exe, we get this message.....
"This application must be installed to run. Please run setup from
thelocation where youoriginally installed the application."
We have tried multiple ways to install, multiple office configurations, and
different computer / server settings. This problems happens every time. In
our research I have checked the Knowledge Base and found articles 224095,
233529, 238387. But these articles refer to Win9x and we are using Win2k
Pro.
Has anyone encountered this and found a solution? Thanks.
Michael R.